Vibe Code Forum teamAdmin
Sharing your app with real people changes everything: their data, your bills and your reputation are now involved. Work through this list first. Ask your AI tool to help check each item. Members can copy the longer tick-box version, the go-live checklist template.
Secrets
- No API keys or passwords in the code or in Git history. Search for them.
- Secret keys only on the server, never in front-end code or browser-visible variables. See Environment variables and .env files.
- Live keys are different from the test keys you used while building.
Data and access
- Database security rules on for every table (Row Level Security or Security Rules).
- Tested with two accounts: neither can see or change the other's data.
- Admin pages and actions checked on the server, not just hidden.
- Backups switched on, and you know how to restore one.
Money
- Spending limits or alerts on every usage-billed service. See Keep costs under control.
- Anything that calls a paid API is rate-limited, so one user (or bot) can't run up your bill.
- If you take payments: tested end to end in test mode, including a failed payment and a refund.
It works
- Every main feature tested on a phone and a computer. See Test before you trust.
- Friendly error pages and messages (no raw error dumps).
- Forms check their input and show what's wrong.
- Sign-up, email verification and password reset all work with a real email address.
The basics
- Your own domain with https. See Domains, DNS and hosting.
- Page titles and a short description, so links look right when shared.
- A privacy policy if you collect any personal data, and terms if you charge money.
- A way for users to contact you.
- Basic error monitoring or at least someone checking the logs.
Last step
Ask your AI tool: "Review this project as if you were a security-minded senior developer about to launch it. List the top risks in order." Fix the serious ones, then share the link. Then read After launch.