Skip to contentNewLaunching soon on Product Hunt (opens in a new tab)

The complete backend, operated for you

Postgres, APIs, auth, storage, realtime and functions, built by your coding agent over MCP and kept healthy by Backenly after launch.

Build with your agent

Your coding agent is the builder. It reaches the backend over MCP, with a key scoped to one project.

  • MCP server

    Typed tools for schema, data, auth, storage and functions, local over stdio or remote over HTTP.

  • Scoped, revocable keys

    One key per project, revocable from the dashboard, and mintable as read-only.

  • Requests, never approvals

    An agent key can ask for a destructive change. Only a person can approve one.

  • CLI

    Schema, generated types, CI drift checks, logs and read-only SQL, with zero dependencies.

  • Agent skill

    A canonical skill at backenly.com/skill.md, so an agent learns the platform first.

  • llms.txt and fetch_docs

    The complete reference in one file, also fetchable by an agent at run time.

How agent-built backends work
terminal
# Project id and key: dashboard, Connect, Agents
claude mcp add backenly -- \
  npx -y @backenly/mcp-server --project <project-id> --key <mcp-key>

# Then, in a new session:
# > add comments to posts. Only the author can delete theirs.

Hosts load MCP servers when a session starts, so the tools appear in the next one.

Database

Standard PostgreSQL in a schema of your own. Isolation is a Postgres grant, not a WHERE clause.

  • Tables and relations

    Columns, foreign keys with their delete behaviour, indexes and CHECK constraints.

  • pgvector

    Store embeddings beside the rows they describe, and query both in SQL.

  • Direct connections

    Read-only on demand, read-write when you arm it. psql, ORMs, any BI tool.

  • Read-only SQL

    Joins, aggregates, CTEs and EXPLAIN, run as a SELECT-only role from the CLI or MCP.

  • Daily backups

    Taken every day and kept for seven days, on every plan.

  • pg_dump exports

    A full export that restores on any Postgres, Free plan included.

The database in depth

REST APIs

PostgREST serves every table from the catalog. A table created a second ago is queryable now.

  • Filters and pagination

    The full PostgREST grammar: operators, or-groups, ordering, ranges and full-text search.

  • Embedded resources

    ?select=*,author(*) returns a row and its relations in one round trip.

  • Two surfaces, one engine

    /api/v1 is the stable contract; /api/v2 passes PostgREST through untouched.

  • OpenAPI and typed clients

    Generated from the live schema by the CLI, never written by hand.

  • A drift gate for CI

    backenly diff fails the build when committed types drift from the schema.

  • JavaScript SDK

    CRUD, auth, storage and realtime from one typed client.

The REST API in depth

Auth

Sign-up and sign-in for your users, isolated per project and signed with the project's own secret.

  • Email and password

    Sign-up, sign-in, sessions and refresh, from two SDK calls.

  • Google sign-in

    OAuth for your users, alongside email and password.

  • Magic links and verification

    Passwordless sign-in and verified emails, with hosted pages and branded mail.

  • A secret per project

    Tokens from one project are never accepted by another.

  • Row-level security by description

    Say who can read and write what. Backenly writes and enforces the policies.

  • Teams for your product

    Organizations, members and invitations for your own customers, scoped by policy.

Authentication in depth

Storage

Buckets and files with their metadata, served publicly or through URLs that expire.

  • Public and private buckets

    Public files load anywhere; private ones need a session or a signed URL.

  • Uploads and metadata

    Upload from the SDK, and every file keeps its metadata beside it.

  • Expiring signed URLs

    Share a private file for a limited time, then never again.

  • Local disk or S3

    Self-hosted installs choose local storage or any S3-compatible provider.

Realtime

Inserts, updates and deletes as they land, over server-sent events. No socket server to run.

  • Database changes

    Subscribe to a table and receive every committed change as it lands.

  • Presence

    Who is online right now, with a sixty-second activity window.

  • Broadcast

    Ephemeral messages between clients, up to 6 KB each.

  • Automatic reconnect

    The SDK reconnects by itself after a dropped connection.

Functions and events

Run TypeScript when rows change, when a user signs up, on a schedule, or at a public HTTPS endpoint.

  • Serverless TypeScript

    Your code, run by the platform, with no server to deploy.

  • Event triggers

    Insert, update, delete and signup events call your function. Pro and Enterprise.

  • Cron schedules

    Run a function on a schedule you write as a cron expression.

  • Outbound webhooks

    Tell other systems when your data changes. Pro and Enterprise.

  • Rate limits

    Built in, so one noisy caller cannot exhaust the rest.

  • Public endpoints

    Expose a function at an HTTPS endpoint of its own.

Governed change

Every change, from you, your agent or the autonomy loop, goes through one path that plans it, gates it, applies it, verifies it and records it.

  • Typed actions

    Ordinary SQL becomes named actions that say exactly what each one touches.

  • Review Queue

    Destructive work waits for a person, with the live row count beside it.

  • Restore points

    Captured before the first write, then the plan commits atomically.

  • Behavioural verification

    Real requests as a stranger and as a signed-in user, with the evidence kept.

  • Change ledger

    Every change with its actor, its diff and a way back.

  • Branches

    Clone the backend, let your agent experiment, review the diff, merge what works.

Autonomy and operations

A resident loop checks every project every minute, fixes what is safe to fix, verifies the fix, and leaves you a receipt.

  • Every minute, every plan

    The same loop on Free as on Enterprise, never metered.

  • No model calls

    Repairs are deterministic, so healing never spends AI credits.

  • Snapshot first

    Only reversible fixes apply on their own. The rest become proposals.

  • Your autonomy level

    Review-only, or apply safe fixes and read about them afterwards.

  • Traffic watched

    Requests, latency and error rates, checked for anomalies.

  • Receipts

    What was detected, what changed, and how the fix was verified.

Operations and autonomy in depth

Teams, security and hosting

The questions a company asks before it trusts a backend with production.

  • Organizations and roles

    Invite teammates with roles. Free includes two seats and Pro five.

  • Custom domains

    Serve your backend from your own domain on Pro and Enterprise.

  • Logs

    Kept for 7 days on Free, 30 on Pro and 90 on Enterprise.

  • Single sign-on

    OIDC sign-on for your team, on Enterprise.

  • Open source

    The platform is Apache-2.0; the SDK, CLI, MCP server and skill are MIT.

  • Self-host or Cloud

    One codebase either way, with pg_dump to move between them.

The whole backend, free to start

One live project, no card. Connect your agent in one command and judge Backenly by the evidence it gives back.