vibemaster

Vibemaster 2.1 — security built into every project, and an easier start

Published

We've just released Vibemaster 2.1. Here's what's new — starting with the part we care most about.

Security rules in every project that uses a database

Earlier this year, researchers examined almost 25,000 apps built with AI coding tools and found that roughly 7,400 of them exposed user records — email addresses and more — to anyone, without a login. The cause was almost always the same: the database had no access rules, or rules that were too open. The code worked, so nobody noticed.

Vibemaster now guards against this for you. Whenever your project uses a database — Supabase, Firebase, Postgres, MongoDB or any other — the code prompt opens with a fixed set of data-access rules:

These rules are inserted by Vibemaster itself, not generated by the AI, so they are identical in every project and can't be forgotten. And they don't stop at the code prompt: your business plan, roadmap and analysis now account for the same thing — as a task in the MVP, a line in the budget and a risk with a mitigation — so security is part of the plan, not an afterthought.

Apps that only store data on the device aren't affected; the rules appear only where a database is involved.

An easier start

Smaller things you'll notice

As always, you're welcome to reach out with feedback, questions or anything you need help with — write to support@vibemaster.ai. We read everything.

Thanks for building with Vibemaster.

Johan
Vibemaster

Start free

Share: LinkedIn X Facebook