Simple BackendBetaStart

BUILT FOR MCP·CLAUDE AND ANY CLIENT

The backend with batteries.

Database, sign-in, hosting, files and functions. Your AI builds it over MCP; the platform keeps it safe.

Start → How to connectConnect and vibe.

Encrypted and secure by default.Daily backups and instant rollbacks.How we keep it safe →

HOW IT WORKS

Ask. Build. Live.

One conversation, one URL. Your AI reads the manual from the server, then writes, tests and ships into your workspace. You can watch every step in the console.

01 · YOU

Ask

› Make me a waitlist page that saves emails, and a page only I can open that shows the count.

in Claude, or any MCP client

02 · YOUR AI

Build

● Simple Backend · add_function ⎿ waitlist/join · public ● Simple Backend · test_function ⎿ 200 in 31ms

written, then tested in the sandbox

03 · THE WEB

Live

● Simple Backend · call_function ⎿ live yourapp.simplebackend.app /waitlist /api/join

called live to prove it answers

Start → How to connect

EVERY WORKSPACE INCLUDES

Everything a backend needs, already running.

Nothing to provision or wire together. The free workspace has all of it, and none of it costs extra.

Database

Every version of every value kept, so you can ask what it said last Tuesday. No schema before your first write.

Sign-in for your users

Emailed codes, sign-in links and passkeys. Off until you switch it on.

Functions

HTTPS endpoints, schedules and queue workers, each run in an isolated sandbox with a time limit.

Hosting

Your pages beside your functions, on your own domain with a paid plan.

Files

A public folder with URLs, and a private one only your functions can read.

Secrets and settings

Sealed with AES-256-GCM and never shown back, through the API or to your AI.

Cache, state and streams

Sessions, presence and feeds: the fast-changing things that are not records.

Releases, preview and rollback

Every deploy is an immutable release. Stage changes privately, roll back in one step.

See the platform in detail →

SAFE TO HAND TO AN AI

Your AI builds. The platform holds the line.

The mistakes that matter when a model writes a backend — who can call an endpoint, where code can reach, what can be deleted — are settled by the platform, not left to the model's judgement.

Who may call it is one word

Every endpoint says public, key, signed-in or none. Nothing is reachable by accident.

Code gets only what it declares

A function that never asked for the database, secrets or the network does not have them.

No tool deletes your work

Wiping or deleting happens in the console with an emailed code, never through MCP.

PREFER TO DRIVE?

The console and the CLI do it all too

Everything your AI can do, you can do by hand: write a function, press Run, read the timings, browse your data as it was last Tuesday, roll back. Export all your source with a button.

sb test             # on the platform
sb deploy           # go live
sb preview promote  # make it live
sb rollback         # the release before

PRICING

Try it with 1 free workspace.

Every feature in every plan. Your own domain from $6 a month; point-in-time restore with Pro at $18.

Start → See pricing