Back office

Pick where the data lives

The screens below work with any backend. Copy the setup prompt for yours and paste it after the screens: it creates the tables, the sign-in, and the rules for who may see what, which is the part AI tools most often get wrong. Ordered by how many people use each.

1. 1Your AI builder's own backend

   builders

   Use the database and sign-in built into the tool you're already in: Lovable Cloud, Bolt's database, Replit's database and auth, or v0 with a Vercel-connected database.

   Best for: People building in Lovable, Bolt, Replit or v0 who don't want another account.

   Cost: Included in the builder's plan, usually with a small monthly allowance.

   Copy setup promptLovable Cloud

2. 2Supabase

   everyone

   Postgres database, sign-in and row-level security in one hosted service. The default for Lovable, Bolt and v0 projects, and what Lovable Cloud runs on.

   Best for: Most sites: bookings, orders, enquiries and an editable menu, with a generous free tier.

   Cost: Free tier for small sites; paid from about $25 a month per project.

   Tested end to end

   Copy setup promptSupabase Auth

3. 3Firebase

   everyone

   Google's hosted Firestore database and Firebase Authentication, protected with Firestore security rules.

   Best for: Teams already on Google Cloud, or sites that also have a mobile app.

   Cost: Free Spark plan for small sites; pay as you go on Blaze.

   Tested end to end

   Copy setup promptFirebase Authentication

4. 4Convex

   developers

   A TypeScript-first backend with live queries: tables, server functions and auth in one place, with every check written in code.

   Best for: All-TypeScript projects that want screens to update live (orders and bookings appearing without refresh).

   Cost: Free tier for small projects; paid plans per team.

   Copy setup promptConvex Auth

5. 5Postgres + Better Auth or Clerk

   developers

   Your own stack: any Postgres (Neon, Vercel Postgres, Railway, your own) with Drizzle, and Better Auth or Clerk for sign-in. Access is checked in server code.

   Best for: Developers who want to own the database and choose each piece, or who already run Next.js with Neon.

   Cost: Neon has a free tier; Better Auth is free and open source; Clerk is free for small user counts.

   Copy setup promptDrizzle with Neon

6. 6PocketBase

   developers

   One small open-source file that is the database, sign-in and admin API. Self-host it on a cheap server and keep everything in one place.

   Best for: Low running costs and full control: one business, one small server, simple backups.

   Cost: Free and open source; a small VPS from a few pounds a month.

   Copy setup promptPocketBase API rules

7. 7Cloudflare D1 + Access

   developers

   Cloudflare's D1 database for the data, and Cloudflare Access in front of /admin so staff sign in with an emailed code — no sign-in code to write.

   Best for: Sites already hosted on Cloudflare that want the simplest secure admin for a small team.

   Cost: Access is free for up to 50 people; D1 has a free tier.

   Copy setup promptCloudflare Access applications

8. 8Google Sheets (content only)

   content only

   No back office at all: the owner edits the menu, prices, hours and closures in a Google Sheet, and the website reads it.

   Best for: Owners who only need to change the menu, prices and opening hours, and take bookings through a booking service.

   Cost: Free.

   Copy setup promptPublish a sheet to the web

Using the MCP? Ask your editor to build a back office and it calls list_recipes and get_recipe for you. Recipes follow each provider's docs; check the linked docs, as providers change their APIs.