
Your coding agent builds it. Backenly keeps it running.
Backenly is an open-source, autonomous backend platform for coding agents. Your coding agent builds the backend over MCP (tables, auth, policies, realtime), while Backenly maintains it: it checks the backend every minute, fixes what it can verify and undo on its own, and holds destructive or risky changes for human approval. It provides real PostgreSQL schemas, REST APIs, auth, file storage, functions/triggers and realtime, and is available as Backenly Cloud or self-hosted.
Your coding agent (Claude Code, Cursor, Codex, Cline, GitHub Copilot, Zed, etc.) builds tables, auth, policies and realtime via typed MCP tools that never consume AI credits.
Backenly checks 26 guarantees every minute, detects broken guarantees, proposes fixes, applies safe ones automatically, and verifies each fix. Autonomy mode is configurable; the safety floor (auth, destructive, irreversible changes) always requires approval.
Dropping or emptying tables, dropping columns, deleting files and revoking keys park as approval requests with impact laid out (live rows, recoverability). Agent keys can request and poll but never approve.
Tables, relations, indexes, constraints and pgvector in an isolated PostgreSQL schema per project (isolation via Postgres grants). Includes direct connection strings, pg_dump exports and standard PostgreSQL.
Sign-up, OAuth, magic links and verification emails, with per-project JWT signing secrets never shared across projects.
PostgREST serves every table from the catalog with filters, ordering, pagination, embedded resources and OpenAPI.
Inserts, updates, deletes plus presence and broadcast, delivered over SSE with no socket server to run.
Buckets, uploads, metadata and expiring signed URLs on local disk or any S3-compatible provider.
One command installs the Backenly MCP server for Claude Code, Cursor, Codex, Cline, or any MCP host; the key is scoped and revocable from the project dashboard. A CLI (npx @backenly/cli) provides schema, generated types, CI diffs, logs and read-only SQL.
The agent applies migrations, enables auth, sets RLS policies, connects integrations (e.g. Stripe) and turns on realtime over MCP; every schema change is read back from the live database before it counts as done.
The autonomy loop observes every minute, fixes safe issues (e.g. adding missing indexes) and re-verifies them; destructive or auth-related changes wait in a 'Waiting on you' queue for human approval, and every fix keeps an Undo.
Free plan at $0/month with 1 live project, 50,000 MAU, 512 MB Postgres and 200 AI credits; Pro at $25/month (or $240/year) with unlimited projects, 100,000 MAU, 8 GB Postgres and 3,000 AI credits; Enterprise at custom annual pricing. Usage beyond included quotas is hard-capped on Free and prepaid up to a spend limit on Pro. A 50% off Pro launch offer (code PRODUCTHUNT50) was tied to the October 31
$0/month
Free forever, no credit card. For prototypes and first experiments. 1 live project, 50,000 MAU, 512 MB Postgres, 1 GB file storage, 200 AI credits/month, unlimited API requests, 7-day backups and restore points, 25 realtime connections, 10,
$25/month (or $240/year)
For products with real users, agencies and small teams. Everything in Free plus unlimited projects, 100,000 MAU (then $0.003/MAU), 8 GB Postgres (then $0.125/GB-month), 100 GB storage (then $0.0213/GB-month), 3,000 AI credits/month, 2M func
Custom (annual, invoiced)
Everything in Pro plus custom limits and AI credit pool, SSO (OIDC), custom guardrail policies for compliance, 90-day logs and 90-day restore points, dedicated support with 12-hour SLA, onboarding and migration help, invoiced billing for pr
One command installs the Backenly MCP server for Claude Code, Cursor, Codex, Cline, or any MCP host. The key is scoped and revocable from your project dashboard. There is also a CLI (npx @backenly/cli) for schema, generated types, CI diffs, logs and read-only SQL, and a canonical agent skill at backenly.com/skill.md.
Dropping or emptying a table, dropping a column, deleting files and revoking keys do not run. Each parks as an approval request under 'Waiting on you' with the impact laid out (how many live rows, whether data is recoverable) and waits for a person on the project to decide. The agent's key can request and poll but never approve. Ordinary row inserts, updates and deletes run as normal.
Real infrastructure: an isolated PostgreSQL schema per project, live REST endpoints, auth with per-project secrets, file storage, and realtime streams. Schema changes are read back from the live database before they count as done, and the autonomy loop keeps monitoring and repairing the backend after you ship.
Yes. The entire platform is open source under Apache-2.0, including the autonomy engine; the SDK, CLI, MCP server and agent skill are MIT. You can self-host everything on your own infrastructure with your own Postgres, or use Backenly Cloud. It is the same codebase either way, so you can move between the two.
Like Supabase, Backenly is open source, built on real PostgreSQL and self-hostable. The difference is who operates it: Supabase and Firebase hand you the parts and leave assembly, configuration and upkeep to you, while Backenly manages backend change safely — changes are planned, destructive ones wait for approval, schema changes are verified against the live database, and a resident autonomy loop keeps fixing the running backend with receipts.
No. The typed MCP tools never use credits. AI credits (1 credit = 1,000 tokens of Backenly's own model usage) cover Backenly's own model usage, included at 200/month on Free, 3,000/month on Pro and a custom pool on Enterprise.
Yes. Every plan includes direct Postgres access and pg_dump export, plus daily backups (7 days kept on all plans) and schema change restore points kept 7 days (Free), 30 days (Pro) or 90 days (Enterprise).