Hi, I build Scribase. It is for developers and small teams shipping an app, and for anyone who now lets a coding agent do most of the setup work.

The painful bit: every new app still starts in a dashboard, and then in five more dashboards. Create the project, copy the URL and keys, paste them into the env file, wire up auth, then sign up somewhere else for push, somewhere else for subscriptions, somewhere else for over-the-air updates. A coding agent cannot click through that for you, and per-user or metered pricing makes the fifth project an awkward conversation.

What Scribase does:

npx scribase init detects the framework, creates the project, writes the env file and a small client module, and sets the keys on a linked Vercel project. With --temp it needs no account.
The MCP server (97 tools) lets Claude Code, Cursor or any MCP client run reads immediately; destructive and control-plane changes wait for an explicit confirm.
Works with supabase-js: the /auth, /rest, /realtime, /storage and /functions paths are contract-tested, so existing client code moves by changing the URL and keys.
Beyond database and sign-in: push notifications, store subscriptions (who paid, from the app stores), over-the-air JS updates and deep links, in the same account with the same key.
Instant copy-on-write branches, scale-to-zero, daily backups, and scribase export writes a bundle that boots elsewhere.

Free vs paid: one project per account is free with no time limit: 0.5 GB database, 1 GB files, scales to zero when idle and wakes on the next request, never deleted for inactivity, no card. Every new account also starts with 14 days of Hobby (up to 3 projects); when that ends, your first project stays on the Free plan and any others pause with their data kept until you add a card. A temporary project is also free for 72 hours with no account; claim it to keep it. Paid: Hobby at $5 per project per month, Pro at $25 per project, or Studio at $199 a month for up to 25 projects.

One honest limitation: the Free plan is one project per account (a second one needs a card), and the hosted platform is not open source. It is also early and runs on our own infrastructure, so at busy moments a new project may wait in line (we email you the moment there is room) rather than be created instantly.

I would like to hear what would stop you from moving a side project over, and which feature you would miss first. I will answer every comment.

Hi, I build Scribase. It is for developers and small teams shipping an app, and for anyone who now lets a coding agent do most of the setup work.

What Scribase does:

npx scribase init detects the framework, creates the project, writes the env file and a small client module, and sets the keys on a linked Vercel project. With --temp it needs no account.
The MCP server (97 tools) lets Claude Code, Cursor or any MCP client run reads immediately; destructive and control-plane changes wait for an explicit confirm.
Works with supabase-js: the /auth, /rest, /realtime, /storage and /functions paths are contract-tested, so existing client code moves by changing the URL and keys.
Beyond database and sign-in: push notifications, store subscriptions (who paid, from the app stores), over-the-air JS updates and deep links, in the same account with the same key.
Instant copy-on-write branches, scale-to-zero, daily backups, and scribase export writes a bundle that boots elsewhere.

I would like to hear what would stop you from moving a side project over, and which feature you would miss first. I will answer every comment.

Scribase

Postgres, Auth, Storage and Realtime, live in one command

Postgres, Auth, Storage and Realtime, live in one command