Skip to main content
Every app comes with its own PostgreSQL database. You describe what you want to store, and the AI creates the tables and writes the code that reads and saves the data.

​
Preview and the live app share one database

Your app’s Preview and its published version use the same database. Data you create while testing in the preview shows up in the live app, and schema changes the AI makes while building take effect right away, not when you publish.
What this means in practice:
  • Test data is live data. Sample records you or the AI add are visible to everyone who uses the published app. Remove them before you share the app.
  • Schema changes don’t wait for Publish. If the AI renames or removes a column the live app still uses, the live app can break until you publish the matching code.
  • There’s no staging database. You can’t test against a separate copy of your data.
For apps people already use, prefer changes that only add things. Ask the AI to add a new column rather than rename or drop an existing one, and publish soon after the change.

​
Browse data in the Data tab

The Data tab is open by default in the app editor. Under App Database, switch between Data and Schema.

​
Data view

The Data view is a read-only table browser:
  • Pick a table from the list on the left.
  • Rows load 10 at a time. Use Previous and Next to page through them.
  • Click a row to open a side panel with every field. Columns that hold JSON or other structured values appear only in this panel, not in the grid.
You can’t add, edit, delete, sort or filter rows here. To change data, ask the AI (see below). Until your app saves something, the table list reads “Tables will populate as soon as your app saves information”.

​
Schema view

The Schema view is a diagram of your database: each table with its columns and their data types, and lines showing how tables relate to each other. Use it to check the structure after the AI changes it.

​
Apps without a database

Some older apps don’t have a database. Their Data tab shows “No database yet”. Click Add Database to create one.

​
Other sub-tabs

The Integrations and External Database sub-tabs show your organization’s connected integrations and external databases. See Integrations and Databases.

​
Change data and schema with the AI

The AI changes your database by running SQL directly. Each time it does, the chat shows Ran SQL query. Ask in plain language:
Create a table for support tickets with a title, status, priority, assignee email and created date.
Add a “region” column to the customers table. Allowed values: North, South, East, West.
Show me all tickets created in the last 7 days.
Delete the test tickets whose title starts with “TEST”.
Vybe doesn’t ask you to confirm before the AI runs SQL, and every change reaches the live app straight away. For deletes and bulk updates, be specific, and ask the AI to show you the rows it will change before it changes them.
Tips for good results:
  • Say what the data means. Mention types when they matter: dates, amounts of money, a fixed list of values, or free text.
  • Check the Schema view after the AI creates or changes tables.
  • Seed sample data to test your UI, for example “Add 20 realistic sample tickets”, then remove it before people start using the app.

​
Use other databases from your app

An app isn’t limited to its own database. It can also use: Set them up first. See Databases and Data queries. Then ask the AI to use them. You can type @ in the app chat to mention a database or data query by name.
Show open orders from our Postgres warehouse on the dashboard.
Store our team OKRs in a new organization database so our coworkers can read them too.
To see the queries your app sends to external databases, add the External DB Queries tab from the + menu. It lists each query with its status, database, duration and any error.
Renaming a data query breaks apps that run it by its old name.

​
Backups and deleting data

  • Checkpoints don’t touch your data. Restoring a checkpoint in the chat reverts code only, never the database. See Version history.
  • There’s no database restore in the editor. Before a risky change, ask the AI to make a copy first:
    Before you change anything, copy the orders table to a new table called orders_backup.
  • Archiving an app keeps its data. Deleting an app permanently deletes its database, and you can’t undo it. See Publishing.