Backenly

Features

• Agent builds the backend over MCP. Your coding agent creates tables, auth, row-level security, integrations and realtime through Backenly's MCP tools, with a key scoped to one project and revocable from the dashboard. Official source 1 ↗
• Postgres schema per project. Each project gets its own PostgreSQL schema with relations, indexes, constraints and pgvector, plus direct connection strings and pg_dump exports. Official source 1 ↗
• Instant REST APIs. PostgREST serves every table as soon as it exists, with filters, ordering, pagination, embedded resources and OpenAPI. Official source 1 ↗
• Auth, storage, realtime and functions. Built-in sign-up, OAuth and magic links; buckets with expiring signed URLs; realtime changes over SSE; and functions on row events, sign-ups or a cron schedule. Official source 1 ↗
• Row-level security from a description. Describe who can read and write what, and Backenly writes and enforces the Postgres policies. Official source 1 ↗
• Approval for destructive changes. Dropping tables or columns, deleting files and revoking keys never run directly; they wait in a review queue for a person, and each schema change can be restored. Official source 1 ↗ · Official source 2 ↗
• Self-healing every minute. Backenly checks every project every minute, fixes safe issues such as a missing index on its own, and holds risky fixes for your approval. Healing is never metered. Official source 1 ↗ · Official source 2 ↗
• Natural-language backend generation. Describe what you need and Backenly extracts entities, relationships and access rules into a plan before writing SQL, then applies later changes incrementally. Official source 1 ↗ · Official source 2 ↗
• Branches. Clone the backend for your agent to experiment on, review the diff and merge what works. Official source 1 ↗

Pricing & free limits

Billing details

One AI credit is 1,000 tokens of Backenly's own model use, spent only by the natural-language tools; the typed MCP tools and self-healing never use credits. Official source 1 ↗

Past Pro's quotas nothing is billed unless you set a prepaid spend limit ($50, $100, $250 or your own); usage then continues at the listed rates up to that limit. Official source 1 ↗

You can cancel anytime; paid access lasts to the end of the billing period, then the account returns to Free. Official source 1 ↗

Free access & limits

Free includes 1 live project, 50,000 monthly active users, 512 MB Postgres, 1 GB storage and 200 AI credits a month. Official source 1 ↗

Free has 10,000 function runs a month, 25 concurrent realtime connections, 2 team seats and 7-day logs, with no event triggers, outbound webhooks or custom domains. Official source 1 ↗

Best for & limitations

Let Claude Code or Cursor build a production backend for an app, such as tables, auth, Stripe checkout and realtime order updates, without writing server code. Official source 1 ↗

Keep an agent-built backend running safely, with destructive changes held for review and safe fixes applied automatically. Official source 1 ↗

Run an open-source, Supabase-style backend on your own servers. Official source 1 ↗

• Natural-language tools use credits. The natural-language build tools run Backenly's own model and spend AI credits; self-hosters need their own Claude or OpenAI key for them. Official source 1 ↗ · Official source 2 ↗
• Agent SQL is translated, not run as written. Migrations are translated into Backenly's own fixed set of actions, anything it cannot translate is refused, and there is no rpc() endpoint for SQL functions. Official source 1 ↗
• Protected tables return empty without a user token. A request without a signed-in user's token reads zero rows from a protected table instead of failing. Official source 1 ↗
• Hosting region and project deletion. The privacy policy says the platform runs on AWS in Mumbai, India, and deleting a project starts deletion with no recovery window. Messages to the AI assistant are stored. Official source 1 ↗