Your app's database

Every Vaulter app gets a database, and you never have to set it up. The moment your app needs to store something, the storage is already there, in your app's own isolated space with privacy rules built in.

It is automatic

When you ask for a feature that needs data, "let users save their bookings", the agent creates the right tables as part of building the feature, and declares who should be able to see each one. You do not design schemas or write queries. You describe what the app should remember, and the data model follows. Schema changes are applied automatically when they are saved.

The Database panel

Open the Vault tab and choose Database. It is a full workbench:

• Tables. Browse every table with its row count. Click into one to page through rows (100 at a time), add rows with a form, edit rows inline, and filter by any column with real operators (equals, not equals, greater and less than, contains, is empty). A Who can see this button shows the exact privacy rules protecting each table. From here you can also import a CSV as a new table, and download any table as a CSV.
• Logs. Your app's real runtime output while you build: console messages, requests, and errors from the preview. The server-side page covers reading them.
• Sample data. While you build, the preview's database can hold sample rows so pages have something to show. They never reach your published app.

Images and other files your app displays live in their own tab, Vault → Storage; see Files and storage.

Let the agent work with your data

You can also ask the agent in chat:

• "Add ten sample products so I can see how the page looks."
• "Delete the test bookings I made yesterday."
• "Show me every user who signed up this week."

Changes that could lose data are checked

Every change to your app's data model is checked before it reaches the database:

• A table or column is removed only when you asked for it to be deleted, in your own words. Otherwise the change is refused and nothing is lost.
• Changes that would break or lose existing rows, like changing a column's type or adding a required column with no default, are refused with the reason and what to do instead.
• Making data visible to more people than before needs you to have asked for it.

Where your data lives

Your app has its own database on Vaulter, separate from every other app, so there is nothing to configure and privacy rules are enforced for you. Two different apps can each have their own todos table without ever colliding.

The preview and the published app have separate databases. What you create while building stays in the preview; the published app starts with its own data, and publishing never copies preview rows across.

To understand who can read which data once your app has users, read How data privacy works. It is the most important thing to get right before you publish an app with real users.

Frequently asked

Can I import data I already have?

Yes. The Database panel imports CSV files into a table. Who can see the rows follows that table's privacy rules.

Do the preview and the published app share the database?

No. Each has its own database. Rows you create while testing in the preview, and any sample data, stay in the preview and never appear in the published app.

Can the agent delete my data?

The agent can edit data you ask it to, and it removes a table or column only when you asked for that in your own words. Treat panel deletes as permanent.

Do I need to know SQL?

No. Browsing, filtering, and editing are all point and click, and the agent handles the data model.