Your app works. Now get it in front of people
Level 1 was about making something run on your own computer. Level 2 is the step where strangers start to use it, which means the audit has to keep up with your changes and search engines have to find you. Then people start writing in, and somebody has to answer them. The free path stays open the whole way. Cloud is there for when you want help running it, and you never need it to launch.
What the Playground does for you at Level 2
Everything below is in the app today, unless it says coming soon. Each part answers a question you only start asking once other people can see your work: is it still safe, and can anyone find it?
Re-audit only what you changed
After a fix, the re-audit reads the code you edited and nothing else, so you only pay to check what changed. The badge records which model formed the verdict and how hard it looked, and gold marks the stricter run.
- Run the audit from your terminal with
npx vibe-audit, and add one step to your build that fails when your code has moved on from the verdict on the badge. - Start an audit, close the Playground, and hear when the verdict is ready. Coming soon
Check that search engines and AI answers can find you
The findability check reads your site the way a search engine does and tells you what to change. It also draws the card people see when your link is shared, from your own name, tagline and color, and puts it where it belongs. No design tool and no credit spent.
- The findability check keeps going after you close the window. Coming soon
Everyone who got in touch, in one list
The Contact Hub puts the forms people fill in on your site beside the other sources you connect, on one timeline. A source you have not connected says so, and when one cannot be read the list tells you it is incomplete instead of quietly showing you fewer people.
- An early-access waitlist that collects names before you launch. Coming soon
Add a block to an app you already built
Payments, logins, uploads and search basics can go into an app you made months ago, in the layout it already uses. It finds where your routes and config really live, shows you what it would write before writing anything, and the Undo panel reverses every change.
A brand kit from your own site
One click turns your site into a brand sheet with its colors, type, spacing and logo, ready to hand to a designer or a video editor. It costs nothing, so make a new one whenever the site changes.
A board of every feature and where it stands Coming soon
Drag what matters to the top of the version you are building, and the next task is picked in the order you chose. It will come with Cloud.
Hosting and your database
Nothing you build goes online by itself. Every app runs on your own computer until you publish it, and publishing is a separate step you confirm. An app you keep at home has nothing online for anyone to attack, so a tool you only use yourself can simply stay there.
When you do want it online, you host it on an account you own, so the bill and the keys stay yours. Picking a host and publishing with one button is Coming soon: the flow is built, and it has not yet been proven against a real account at every host, so we will not name one as working until it has.
Your database is where a launch usually goes wrong. The audit reads how your app talks to it and says whether the public could read your data: keys left in the browser, row-level security missing, a database port open to the internet. When it cannot tell, it says ungraded rather than clean. Connecting a database to run your migrations works with Postgres today, and the audit names other databases it recognizes without connecting to them.
A launch you can check before you announce it
None of these steps needs Cloud or a paid plan.
- Run the audit and fix what it finds. Each finding comes with its fix, and the re-audit only checks the code you touched.
- Run the findability check. Fix what stops search engines reading the page, and let the Playground draw your link card.
- Open the Contact Hub. Make sure the form on your site lands somewhere you will read it.
- Publish when you are ready, and only then. Until you confirm, the app stays on your computer.
- Keep the badge honest. Add the audit step to your build so the badge cannot quietly go stale after launch.
Why Cloud helps, and the free path beside it
Cloud is optional, and it is Coming soon. It does not take over your hosting: your apps still run on your own account, and Cloud is the online place where you manage them.
Everything on this page, on your computer
- Build and run your apps on your own machine.
- The audits and the audited blocks stay free in the Playground. The audit runs on your own AI key.
- Host on an account you own, and publish only when you confirm.
The same work, reachable from anywhere
- Manage your live sites, your marketing and your contacts online, and log in from more than one computer.
- Share the work with employees and business partners.
- Run the audits and drop in blocks from inside your own Claude session, on your own plan. A result run that way is labelled self-run and does not earn the public badge, because we did not run it.
- The Playground Manager: one place to watch who signed up, who is paying and what is breaking.
See pricing for what Cloud will cost when it opens.
Moving between levels
The levels decide what the app shows you, not what you are allowed to do. Switching is free and never requires a payment. Picking your level inside the app is Coming soon. Until then, everything above is simply there when you open the Playground.
- Level 1: Learning. Build and run apps on your own computer, and fix what the audit finds.
- Level 3: Professional. See who visits, check whether a buyer would clear your app, and bring in a team.
Free reading before you launch
None of this needs the app. The SEO audit checklist walks through what a search engine needs from your page. The vibe code audit explains what the Standard checks and why. And the Coding Guide answers the questions a first launch raises.