BATTERIES INCLUDED·BUILT FOR MCP·FREE DURING THE BETA
A database, functions, sign-in for your users, hosting, files and scheduled jobs — ready the moment you sign up. Point Claude, or any MCP client, at it and ask for what you want built.
GETTING STARTED
Sign in with Google. Your first workspace is free — and during the beta, so is every battery. No card, nothing to configure — the database, hosting and everything below already exist.
One URL. Your browser opens, you approve, done — no API key to copy or paste.
Settings → Connectors → Add custom connector https://app.simplebackend.dev/mcp Same steps on claude.ai.
claude mcp add --transport http \ simple-backend \ https://app.simplebackend.dev/mcp
Add a remote (HTTP) MCP server: https://app.simplebackend.dev/mcp Sign-in is OAuth — your browser opens to approve.
Your LLM reads the manual from the server itself, then builds, tests and ships into your workspace. You watch it happen, or open the console and see everything it made.
BATTERIES INCLUDED
Nothing to provision or wire together. Every workspace has all of it, and during the beta none of it costs extra.
HTTPS endpoints, cron jobs and queue workers. Clojure or JavaScript, in a sandbox, timed on every run.
No schema before your first write. Every version of every value kept, so you can ask what it said last Tuesday.
Emailed codes, sign-in links and passkeys, or your own Firebase. Drop in <sb-signin> and you have a login.
Your pages at you.simplebackend.app, beside your functions. Your own domain for $1 a month, certificate included.
A private and a public folder per workspace. Public files get a URL; private ones never leave your functions.
Credentials sealed at rest and never shown back. Plain settings your functions read with no setup.
Sessions, presence, cursors, feeds and transcripts — the fast-changing things that are not records.
Every call logged with its timings. Every deploy a release you can roll back. Export all your source with a button.
SAFE TO HAND TO AN LLM
The things that go wrong when a model writes a backend are decided by the platform, not left to the model.
Every endpoint says public, key, signed-in or none. Nothing is reachable by accident, and public endpoints are rate limited.
Opening your app to sign-ups is your decision, made out loud — in the console, or by your LLM when you ask.
A release that fails validation is refused with the reason, and the last good one stays live.
A function reaches the hosts its release lists, and nowhere else.
Wiping data or deleting a workspace happens in the console, never through MCP — a wipe even needs an emailed code.
Approve read-only, or one workspace instead of all of them, on a consent page you can read.
PREFER TO DRIVE?
Everything your LLM can do, you can do in the console: write a function, press Run, read the timings, browse your data as it was last Tuesday, roll back. And sb does it from a terminal or a pipeline.
sb test # on the platform sb deploy # go live sb sign-in enable # switch on sign-in sb rollback # the release before
THE FOUNDATION
Every version of every value is kept, because the database underneath is Datahike — an immutable Datalog store. No schema before your first write, and a past you can still query.
datahike.io — the memory model underneath →PRICING
Sign-in, files, the database, hosting and every other battery cost nothing while we are in beta. A second workspace is $5 a month, and your own domain on any workspace is $1 a month. Before any of that changes, we will tell you.