Security
How your app is secured
Apps built here are secure by construction, not by configuration. Most AI-builder security incidents come from many customers sharing one database with per-row rules that someone gets wrong. We removed that class of mistake instead of asking you to avoid it.
Your own database — not a shared one
Every app gets its OWN Postgres project (Neon). There is no shared database, no shared tables, and no row-level-security rules to get wrong — the failure mode behind the best-known AI-builder data leaks structurally does not exist here. Your data lives alone.
Draft and live data are separated
Your database has a development branch and a production branch. Building and previewing touches only the development branch; your live customers' data is on the production branch and only changes when your app changes it. A build can never trample production data.
Nothing goes live until you publish
Every change builds as a private draft first. Your live site only updates when you press Publish — and each published version is pinned, so you can restore any previous version in one click.
Secrets never live in code
Database credentials, AI access, and upload tokens are injected as environment settings — encrypted at rest, never committed to your repository. The AI that builds your app is under standing instructions to never hardcode a secret, and every build is scanned for pasted keys before you publish. If we find one, we tell you.
Isolated build machines
Each project builds inside its own dedicated virtual machine — not a shared runtime. When you stop working, the machine is destroyed. Nothing about your project is reachable from anyone else's.
Checked in a real browser
After each build, we open your app in a real browser and look for errors before you publish — the kind of check a careful engineer does by hand, run automatically.
Sign-in that's built right
When your app needs user accounts, it uses a managed authentication provider with per-environment trusted origins — not hand-rolled login code. Passwords are never stored by your app.
A human engineer, one button away
Security questions, a review before a big launch, or something that doesn't look right — Ask an Engineer reaches a real person who can inspect your actual code and infrastructure. No other AI builder offers that.
Before you publish — a five-point check
- 1No secrets or API keys pasted into code — keep them in environment settings (we scan every build and warn you).
- 2Pages meant to be private sit behind sign-in — tell the builder which pages should require an account.
- 3Forms that collect personal data only collect what you need.
- 4You've clicked through your draft site — the browser check catches errors, you catch wrong content.
- 5You know how to restore: every published version can be brought back in one click from publish history.
It's your code, on your terms
Every project is a real repository with a real Postgres database from the first minute — no proprietary runtime, no export wall. If you ever leave, your app comes with you and keeps working. That's a security property too: you are never locked into trusting us forever.