Add a database
Add a database to your app so it can store and read data
When your app needs to store data, connect a hosted database and ask the agent to add the tables you need. It wires your app to read and write them.
When to use it
Use this when your app needs to remember anything between visits: form submissions, user records, posts, orders, or any content you add and edit over time.
What you need
- An account at plutoai.one.
- A database provider connected. The user-connectable options are Supabase, Neon, and Airtable.
Connecting is one click from the integrations catalog through a secure sign-in with the provider. There are no keys to copy. See Connecting your tools.
Steps
- Connect a provider
Pick Supabase, Neon, or Airtable from the catalog and connect it in one click.
- Describe the data you need
Tell the agent what to store, for example a table of recipes with a title, ingredients, and steps.
- Let it wire the app
The agent adds the data model and connects your app to read and write it. It can create and run the database changes (migrations) for you.
- Try it in the preview
Add and edit a record in the running app and confirm it saves.
Choosing a provider
| Provider | Best for |
|---|---|
| Supabase | Structured, relational data with queries, and a place to store users for sign-in. |
| Neon | Structured, relational data with queries. |
| Airtable | Data that already lives in a spreadsheet-style grid, or that you want to edit in a familiar table view. |
Supabase and Neon suit apps that filter, sort, and join across related tables. Airtable works record by record, which is handy for simple content but less suited to heavy relational queries.
Example prompt
I've connected a database. Add a recipes table with title, description,
ingredients, and steps, then build a page to list recipes and a form to
add a new one. Save new recipes to the database and show them in the
list.
Realistic follow-ups:
Add an edit and delete action to each recipe in the list.
Add a category field to recipes and let me filter the list by category.
Expected result
Your app reads and writes real data in the connected database, and changes you make in the app persist between visits.
Common problems
- No provider connected yet. Connect one from the catalog before asking for tables.
- The data model changed and the app expects the old shape. Ask the agent to update the model and the pages together, and to run the needed migration.
- Records are visible to everyone. If each user should only see their own data, add sign-in and scope the tables per user. See Add authentication.