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.
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.
4 things you can do with it.
Forms that save for real
Orders, bookings and messages land in a table in your own account.
Your provider
Supabase or PocketBase, proven end to end. Firebase, Neon, Nhost and Upstash are in beta.
Security rules
Tables come with access rules, not left open.
Keys kept away from agents
The agents work without your API keys in reach. A secret in the code stops the release.
Plain words in the one chat.
You never pick the module. Neo reads the request, picks Backend and database, and says why.
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.