Skip to main content
Every project gets two databases: one for development, one for production. Anything handles the structure, the queries, and the code. You just describe what you want to store. Your database runs on PostgreSQL (via Neon) and scales automatically as your app grows.
Development vs. production: When you publish, Anything pushes the database structure (tables and fields) to production, but data stays separate. Test data you create while building won’t appear in your live app. This protects your production data while you experiment.

​
How it works

When a feature needs data, Anything:
  1. Designs the database structure
  2. Creates Functions to save and retrieve data
  3. Builds pages and components to display it
  4. Wires everything together

​
Example

Say “make me a tasks app” and Anything:
1

Creates a tasks table with title, due date, and other fields

2

Creates Functions to save and fetch tasks

3

Builds a Page with a task list and add form

4

Makes your Page use your Functions to save and grab tasks from the database

As you keep building, Anything updates the database structure, functions, and pages to match.

​
Common changes

Describe what you want and Anything handles the database updates. 
Add a description to todos. Show it below the title in italics.

Remove the priority from todos, we won't use it anymore

Let users add comments on todos. Each comment should have the text and who wrote it

Instead of due dates, let's use status (Todo, In Progress, Done) to track progress

Generate 10 sample todos with different statuses and assignees

Make sure every todo has a title
The more specific you are, the better. “Make a todo app” works, but “make a todo app with a title, due date, and priority field” gives you exactly what you want.

​
Database viewer

The built-in database viewer lets you see your data, edit rows, sort, filter, and run SQL queries. Open it from the Project Selector or tap a database mention in chat.
Demo mode uses the development database. Your live data stays untouched while you experiment.

​
Publishing

When you publish, Anything pushes the database structure (tables and fields) from development to production. Data stays separate.
If you remove a field in development that exists in your live database (like a phone number column with real data), Anything warns you before publishing. You can either keep the field or accept the data loss.

​
Troubleshooting

If data isn’t saving, check these three things in order:
  1. Database structure — open the viewer and verify your tables and fields look right. If not, describe the correct structure in chat.
  2. Functions — ask the agent to test the function that saves data. If it errors, paste the error into chat.
  3. Page to function — try the app in Demo mode and watch the database viewer. If records don’t appear, tell the agent what should happen (e.g., “submitting the form should save a task”).
Paste any error message directly into chat. Anything recognizes common patterns and can usually fix them.

​
Reset database structure

If you’ve made changes to your development database and want to undo them, you can reset to the structure of your last published version.
  1. Open the database viewer
  2. Click Reset in the top right
  3. Confirm
Resetting removes all structure changes since your last publish. Any tables or fields you added since then (and their data) will be lost.

​
Remove extra databases

Most projects only need one database. A single database can have as many tables as you want, and that’s easier to work with than multiple databases. If you have extras, remove them by selecting the database in the Project Selector, clicking Remove from Project in the top right, and confirming. Remove from project

​
Duplicate a project with data

When you duplicate a project from the dashboard, you can choose whether to include database data in the copy. A dialog lets you pick development data, production data, both, or neither. The database structure (tables and fields) is always copied. This is useful for creating a staging version of a live app or starting a new version with real data to test against.

​
Use an existing database

If you already have data in another project’s database and want to reuse it:
  1. Open your new project
  2. Press / > Databases > select the database
  3. Describe what you want to build
Both projects will share the same data. This is useful for building an admin tool alongside a customer-facing app.

​
Export

Export your entire database as a ZIP file containing SQL dumps for both development and production.
  1. Open the database viewer
  2. Click Export database
  3. You’ll get an email when the export is ready
The ZIP includes development.sql and production.sql with your full database structure and data.

​
FAQ

Yes. Every database runs on PostgreSQL via Neon and autoscales as your app grows.
Free plans include 1 GB of storage. Pro plans get 10 GB. Business and Enterprise get 100 GB. Upgrade your plan if you need more.
Yes. Click Export database in the database viewer to download a ZIP with SQL files for development and production. See Export.
Not yet. Import is coming in a future update.
Use Functions to connect to external databases like Supabase or your own backend.
Yes. Databases are automatically backed up. Email hello@anything.com if you need to restore data.
Anything writes queries automatically. For custom queries, use the SQL editor in the database viewer or create a Function and describe what you need.
Ask the agent to add sample data and be specific about what it should look like. See this video for a demo.

​
Terminology

Think of a database as a collection of connected spreadsheets.
TermWhat it means
TableLike a spreadsheet (e.g., “Users”, “Products”)
FieldsThe columns (e.g., “name”, “email”)
RowsIndividual entries
SchemaThe overall structure of your tables and fields
QueryInstructions to get or save data
MigrationA change to your database structure
You don’t need to memorize these. Describe what you want to store and Anything handles the rest.