Your data & database

Every onvibe app comes with its own real database — automatically, with nothing to set up. That's what lets your app remember things between visits: the RSVPs people submitted, the items on a list, the posts in a guestbook.

What this means for you

• You don't create or configure a database. It's there from the moment your app exists.
• When you ask for an app that "saves", "remembers", "keeps a list of", or "tracks" something, your AI uses this database behind the scenes.
• Your data persists. Updating your app's design or features does not erase what's stored.

What to ask for

Just describe what should be remembered, in plain words:

• "Save each sign-up with their name, email, and the date they joined."
• "Keep a running list of expenses with amount, category, and a note."
• "Remember which items are checked off so they stay checked when I reload."

Seeing and editing your data

You can ask your AI about the stored data directly:

• "How many people have signed up so far?"
• "Show me the last 10 messages."
• "Delete the test entries I added earlier."

Your AI can read and change the data for you — you don't need to know any database language.

Changing what gets stored

If you later want to store something new (say, add a phone number to each sign-up), just ask. Your AI will evolve the structure without throwing away the data already there. This is done carefully so the live app keeps working during the change.

"Add an optional 'company' field to the sign-up form and store it too."

Good to know

• Each project has its own separate database — apps don't share data with each other.
• There's a generous storage allowance per project; see Limits & good to know.
• For files and images specifically (not text data), see Files & images.