The best backend for vibe coding is hosted Postgres that comes with auth, an auto-generated API, and Row Level Security, plus a scoped MCP connection your AI tool can use without your database password. If you build entirely inside Lovable or Bolt, their built-in backends are the fastest start. If you code in Cursor, Claude, or VS Code, or want a backend you can take with you, Supabase and WoWSQL both fit. WoWSQL gives you managed Postgres, auth, storage, realtime, REST, and a hosted MCP server at https://mcp.wowsql.com/mcp that you can pin to one project in read-only mode, on flat $0 / $25 / $99 plans. Facts were checked on 21 November 2026.
Key facts
- What WoWSQL includes on every plan: Postgres, authentication, realtime, file storage, and REST and MCP APIs (pricing).
- Hosted MCP:
https://mcp.wowsql.com/mcpuses OAuth, so you don't paste a long-lived key into a JSON file. Addproject_ref=<slug>to pin it to one project,read_only=trueto block INSERT, UPDATE, DELETE, and DDL inexecute_sql, andfeatures=to choose tool groups (MCP overview). Setup pages cover Cursor, Claude, VS Code, and other HTTP MCP clients.- MCP tools:
list_projects,get_project,list_tables,execute_sql,search_docs, andget_doc. There are no storage tools yet (MCP reference). Pro allows 100 MCP requests a minute and Scale 250.- SDK:
@wowsql/sdk3.10.0 (WowSQLClient,ProjectAuthClient,WowSQLStorage), andwowsql gen typescriptwrites types from your schema.- Plans (USD): Free $0 (256 MB database, 10,000 MAU, no platform backups), Pro $25/month (daily backups kept 7 days), Scale $99/month.
- Regions: Mumbai (
ap-south-1), US East (us-east-1), and Frankfurt (eu-central-1). The self-hosted edition is Apache-2.0.
What an AI coding tool needs from a backend
Vibe-coded apps need the same backend as hand-written ones: sign-in, a database, file uploads, and an API. The difference is that a model writes most of the code, and it moves fast. That puts a few extra requirements on the backend:
- A schema the model already understands. Coding models have seen a huge amount of SQL. Postgres tables, joins, and policies are where they make the fewest mistakes.
- Auth, data, storage, and API in one place. Every extra vendor is another set of docs the model can get wrong. One SDK with a small, consistent surface is easier for an agent to use correctly.
- Rules that live in the database. The browser code an AI writes is public. Anyone can open dev tools, read your anon key, and call your API directly. Row Level Security keeps "users can only read their own rows" inside Postgres, where a prompt can't delete it.
- A safe way for the agent in. The agent will want to look at tables and run SQL. Give it a scoped, revocable OAuth connection through MCP, pinned to one project and read-only by default. Don't give it the owner password or the service key.
- Types and migrations. Generated types stop the model from inventing column names. Migration files let you review what it changed.
- A way back. Agents make confident mistakes. Know what backups your plan has before you let anything write to production.
Option 1: Stay on the builder's built-in backend
Both big app builders ship their own backend, and for a prototype that is usually the right call.
Lovable. Lovable's built-in backend (called Cloud in parts of the product) includes a database, auth, storage, realtime, and edge functions, and "utilizes Supabase's open-source foundation" (Lovable docs, as of Nov 2026). Things to know before you rely on it:
- The default agent permissions are permissive. Modify database, Change data, and Configure auth are all set to Always allow by default. Only backward-incompatible migrations default to Never allow. You can change each one to Ask each time.
- The region (Americas, Europe, or Asia Pacific) is locked once the backend is enabled, and you can't move a project between regions.
- Lovable says migrating from Supabase to the built-in backend is not supported, and moving out to your own Supabase is a manual export, restore, and reconfigure.
- Usage is paid from Lovable credits. Free and paid plans include a monthly grant of 20 Cloud credits; Pro is $25/month (Lovable pricing, as of Nov 2026).
Bolt. Bolt Database is included on every Bolt plan and is created automatically when your project needs one (Bolt docs, as of Nov 2026). It has auth settings, file storage, server functions, logs, and a Security Audit that checks for problems such as a missing RLS policy. Low-usage databases can be paused after six days unless the project is published on Bolt hosting. Bolt Pro is $25/month (Bolt pricing, as of Nov 2026). Bolt's docs also show how to opt out: tell it "Don't use Bolt Database. This app uses my existing API at …".
When to leave the built-in: when you need direct SQL access, a specific region, predictable costs, or to use the same backend from a mobile app or a second tool. Then you bring your own backend.
Option 2: Bring your own backend (Supabase or WoWSQL)
A backend you own outlives the builder. Lovable and Bolt both document Supabase connections, which is why Supabase is the default in most vibe-coding guides. Its hosted MCP server is at https://mcp.supabase.com/mcp, with project_ref, read_only, and features parameters, and its docs warn you not to give the MCP connection to end users and to scope it before using production data (Supabase MCP docs, as of Nov 2026).
WoWSQL works the same way from Cursor, Claude, or VS Code, but it has no one-click integration inside Lovable or Bolt. There you add it as an external API: put the project URL and anon key in the app's environment and ask the builder to use @wowsql/sdk (or plain fetch against /rest/v1).
Set up WoWSQL for an AI coding tool, step by step
Step 1: Create the project and turn on auth
Sign up at app.wowsql.com/signup, create a project in Mumbai, US East, or Frankfurt, then open Authentication and enable it (it asks for a JWT secret of at least 32 characters). From the Connect menu, copy the project URL and the anon key (wowsql_anon_…). The service key (wowsql_service_…) bypasses RLS. Never put it in a prompt, a frontend file, or a builder's environment that ships to the browser.
Step 2: Connect the MCP server, scoped
In Cursor, add this to .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally), then restart Cursor and complete OAuth in the browser (Cursor setup):
{
"mcpServers": {
"wowsql": {
"type": "http",
"url": "https://mcp.wowsql.com/mcp?project_ref=YOUR_PROJECT_SLUG&read_only=true&features=database,docs"
}
}
}
That URL gives the agent list_tables, read-only execute_sql, and docs search for one project, and hides the account tools. Claude Desktop connects through npx mcp-remote <url>, and any client that supports Streamable HTTP MCP can use the same URL. When you want the agent to write schema changes, use a separate connection without read_only=true on a development project, and keep tool-call approval switched on in your client. The Cursor database setup guide and Postgres MCP server comparison go deeper.
Step 3: Give the agent rules it can follow
Agents follow project rules files well. Put something like this in AGENTS.md, .cursor/rules, or Lovable/Bolt project knowledge:
Backend: WoWSQL (Postgres). SDK: @wowsql/sdk 3.10.0.
- Data: new WowSQLClient({ projectUrl, apiKey }).table('<name>')
.select('*').eq(col, val).order(col, 'desc').limit(n).get()
.create({...}) / .update(id, {...}) / .delete(id)
- Auth: new ProjectAuthClient({ projectUrl, apiKey }) with
signUp, signIn, getUser, refreshSession, logout, sendMagicLink,
sendOtp/verifyOtp, getOAuthAuthorizationUrl(provider, redirectUri)
- Files: new WowSQLStorage({ projectUrl, apiKey }) with upload, getPublicUrl,
download, listFiles. There are no signed/presigned URLs.
- Only the anon key (wowsql_anon_...) may appear in client code.
- Every new table in public: enable RLS and add policies using auth.uid().
- Take user IDs from the verified session, never from request bodies.
- Schema changes go in migration files; do not edit production directly.
Every method named there exists in the 3.10.0 docs and type definitions. Rules like this stop the most common failure: the model "remembering" a different SDK's API and writing calls that don't exist.
Step 4: Let the app talk to the backend
import WowSQLClient, { ProjectAuthClient } from '@wowsql/sdk'
const projectUrl = import.meta.env.VITE_WOWSQL_PROJECT // e.g. 'myproject'
const apiKey = import.meta.env.VITE_WOWSQL_ANON_KEY // wowsql_anon_...
export const auth = new ProjectAuthClient({ projectUrl, apiKey })
export const db = new WowSQLClient({ projectUrl, apiKey })
const login = await auth.signIn({ email: 'user@example.com', password: 'SecurePassword123' })
For queries that must run as the signed-in user, so that RLS sees auth.uid(), send the anon key in apikey and the user's access token in Authorization:
const res = await fetch(`https://${projectUrl}.wowsqlconnect.com/rest/v1/notes?select=*`, {
headers: {
apikey: apiKey,
Authorization: `Bearer ${login.session?.accessToken}`,
},
})
The login guide covers magic links, OTP, and OAuth. The React backend-as-a-service guide shows the same calls inside components. To keep the model honest about your schema, run wowsql gen typescript --output ./types/database.ts after each migration and commit the file (type generation).
Security pitfalls in vibe-coded backends
Most security problems in AI-built apps are small, boring mistakes that show up again and again. Check for these before launch:
- RLS off, or on with no policies. With RLS off, anyone holding the anon key can read the whole table. With RLS on and no policy,
anonandauthenticatedsee empty results, and the model may "fix" that by turning RLS off. Ask it to write the policy instead. This query lists tables inpublicwithout RLS:
select c.relname
from pg_class c
join pg_namespace n on n.oid = c.relnamespace
where n.nspname = 'public' and c.relkind = 'r' and not c.relrowsecurity;
- The service key in the bundle. Search your built JavaScript for
wowsql_service_. If you find it, rotate the key in API Keys → Regenerate; the old key stops working. - Trusting a client-supplied
user_id. Policies should compareauth.uid()with the row's owner column. Writewith check (auth.uid() = user_id)on inserts so users can't create rows for someone else. See what is Row Level Security. - Agent write access to production. Use
read_only=trueandproject_reffor anything that touches real data, and keep write sessions on a development project. - Prompt injection through data. Rows and docs can contain hostile text. WoWSQL's MCP server appends a reminder to treat tool output as untrusted, but your client's approval prompts are the real safeguard.
- Keys in Git. Put the project URL and anon key in environment variables, and keep
.envfiles out of the repo. - No backup plan. The Free plan has no platform backups. Pro and Scale keep daily backups for 7 days, restored by support. That isn't point-in-time recovery, so run your own
pg_dumpbefore risky agent sessions.
Comparison: built-in backends, Supabase, and WoWSQL
Competitor facts come from each vendor's own pages, checked 21 November 2026 (as of Nov 2026). Links are under the table.
| Lovable built-in (Cloud) | Bolt Database | Supabase | WoWSQL | |
|---|---|---|---|---|
| What it is | Backend inside Lovable, built on Supabase's open-source foundation | Database built into every Bolt project | Postgres development platform | Postgres backend-as-a-service |
| Best when | You build only in Lovable | You build only in Bolt | You want the biggest ecosystem and builder integrations | You want flat pricing, a scoped hosted MCP, and US/EU/India regions |
| Agent access | Through the Lovable agent; database permissions default to Always allow | Through the Bolt agent; Security Audit for missing RLS | Hosted MCP with project_ref, read_only, features |
Hosted MCP with project_ref, read_only, features (OAuth) |
| Use from Cursor or other tools | Managed through Lovable; moving out is a manual export and restore | Can be claimed into your own Supabase account | Yes | Yes |
| Price to start | Lovable Free includes 20 Cloud credits/month; Pro $25/month | Included on every plan; Pro $25/month | Free $0 (2 projects, 500 MB, paused after 1 week idle); Pro from $25/month plus compute | Free $0 (1 project, 256 MB, 10,000 MAU); Pro $25/month |
| Regions | Americas, Europe, Asia Pacific (locked after enable) | Not stated on the page checked | 17 specific AWS regions | Mumbai, US East, Frankfurt |
| Backups on entry paid tier | See Lovable docs | See Bolt docs | Daily, 7 days; PITR add-on $100/month per 7 days | Daily, 7 days; no PITR |
| Self-host | Not offered on the pages checked | Not offered on the pages checked | Yes (Docker) | Yes (Apache-2.0, Docker Compose) |
Sources: Lovable built-in backend, Lovable pricing, Bolt Database, Bolt pricing, Supabase pricing, Supabase regions, Supabase MCP, WoWSQL pricing, WoWSQL MCP reference.
Where others are better: Lovable and Bolt need zero setup and keep everything in one chat. Supabase has native integrations with both builders, a broader MCP toolset, PITR, branching, more regions, and the largest community. WoWSQL is the younger product with a smaller ecosystem. Its strengths are a single flat price per plan with a dedicated Postgres instance from Pro, a hosted MCP that is easy to lock down, three regions across the US, EU, and India, and an open-source self-hosted edition.
Which should you pick?
- Prototype inside one builder: stay on Lovable's or Bolt's built-in backend until real users arrive.
- Coding in Cursor or Claude with a real Postgres you control: Supabase or WoWSQL. Pin MCP to one project, read-only.
- Users in India, or flat-price billing matters: WoWSQL. Free to start, $25 when you need dedicated Postgres and backups.
- Need PITR, branching, or a region outside those three: Supabase.
- Already on Supabase and want to move: follow the Supabase to WoWSQL migration guide. To compare against a database-only option, see WoWSQL vs Neon.
FAQ
What is the best backend for vibe coding in 2026?
Hosted Postgres with auth, an auto-generated API, Row Level Security, and a scoped MCP connection. Use Lovable's or Bolt's built-in backend for a prototype that stays in the builder. Use Supabase or WoWSQL when you code in Cursor or Claude or want to own the backend. WoWSQL offers a hosted MCP at mcp.wowsql.com/mcp and flat $0 / $25 / $99 plans.
What database should I use for a Lovable app?
Lovable's built-in backend is the easiest start and runs on Supabase's open-source foundation. Lovable also documents connecting your own Supabase project. Any other backend, including WoWSQL, can be called as an external API with its URL and anon key, but there is no one-click integration.
What are Bolt.new's backend options?
Bolt Database is included on every plan and created automatically. Pro and Teams users can use their own Supabase instead, or claim the Bolt Database into Supabase. Bolt's docs also show how to tell it to use an existing external API instead of Bolt Database.
How do I connect Cursor to my database safely?
Add a hosted MCP server to .cursor/mcp.json and scope it. For WoWSQL, use https://mcp.wowsql.com/mcp?project_ref=YOUR_SLUG&read_only=true, complete OAuth in the browser, and keep tool approvals on. Never paste the service key or the database owner password into the chat.
Is vibe-coded app data secure?
Only if Row Level Security is on for every public table, with policies that use auth.uid(), and the service key never ships to the browser. Check for tables without RLS before launch, keep agents read-only on production, and make sure you have a backup.
Does WoWSQL work with Claude Code and VS Code?
WoWSQL's docs include MCP setup pages for Claude, VS Code, and Cursor, plus a generic HTTP config for any client that supports Streamable HTTP MCP. Clients that only support stdio can use npx mcp-remote with the same URL.
Related guides
- Cursor AI database setup
- Postgres MCP server: local vs hosted
- Best backend for AI apps
- What is Row Level Security?
- How to add login to your app
- Free backend for apps
- Auth as a service compared
- React backend as a service
- WoWSQL vs Neon
- Migrate from Supabase to WoWSQL
Give your AI tool a backend in a few minutes: create a free WoWSQL project · Pricing · MCP docs