Database
Somewhere for it to remember
Bookings, sign-ups, saved work — anything that has to survive a refresh needs a database. It goes on your account, not ours, and nothing touches it without your say-so.
It is your database, on your account
You connect your own Supabase account once, through Supabase's own approval screen. No connection string is typed into Webzy, and you can withdraw access from your Supabase dashboard whenever you like.
The project is billed to you and belongs to you. If you stop using Webzy tomorrow, the data does not go anywhere — it is sitting in an account you already had, in ordinary tables you can open with any tool you like.
Nothing runs without you allowing it
When the app needs a table, Webzy does not create one. It shows you what it wants to do, in plain words, and waits. You allow it once, or you allow that kind of change to keep happening, or you say no.
Anything that could lose data — dropping a table, removing a column, deleting rows — is asked about separately every single time, no matter what you have already allowed. There is no setting that turns that off, because a permission you cannot remember granting is not a permission.
A written record of everything
Every statement Webzy has ever run against your database is kept: what it was, when it ran, whether it worked, and which permission it ran under. So “what has this thing done to my data” has an answer you can read rather than a guess.
The statement you approved is the statement that runs. It is sealed when it is written down, so nothing can be substituted between you reading it and it being sent.
Permissions you can take back
A standing permission is listed in your project settings with the date you gave it, and one click withdraws it. Withdrawing also cancels anything that was approved but has not run yet, so taking it back means what it says rather than only applying to future work.
Access rules belong with the data
Webzy asks the models to include row-level access policies when generating tables. Check that those policies match your app's intended users before connecting real data. AI drafting and review do not guarantee that every access rule is correct.
What are you going to build?
Start with a sentence. Follow the draft and AI review, then test and refine the result.