Module 05 of 18 · Build

Backend and database

When something you build needs to keep data, Neo gives it a real database in your own account: tables, security rules, environment settings and webhooks. A booking form on a site saves to a table you can open next to the preview. The agents never hold your keys, and every site and app is scanned for secrets before it ships.

You say
“Save the bookings from the reservation form to a database.”
Neo · Backend and database

A real recording from the Neo app. A restaurant site with table bookings: the form is sent, and the row lands in the database shown next to the site.

What you can do with it

4 things you can do with it.

Form sent
Row saved
Shown next to the site

Forms that save for real

Orders, bookings and messages land in a table in your own account.

SupabasePocketBaseFirebase (beta)Neon (beta)Upstash (beta)

Your provider

Supabase or PocketBase, proven end to end. Firebase, Neon, Nhost and Upstash are in beta.

TableRulesApp

Security rules

Tables come with access rules, not left open.

Secret key found in the code
Waits for your yes
Stopped

Keys kept away from agents

The agents work without your API keys in reach. A secret in the code stops the release.

You say…

Plain words in the one chat.

“Save the bookings from the reservation form to a database.”
“Add a table for orders with name, phone and pickup time.”
“Show me the newest bookings.”

You never pick the module. Neo reads the request, picks Backend and database, and says why.

What you get at the end

What you hold when it is done.

  • Tables with security rules in your own account
  • Forms wired to them and tested
  • Environment settings and webhooks in place

Anything that spends money, publishes or deletes stops and asks you first, with the price on the button.