# A database for vibe-coded apps, with access built in

Keep the data for the apps you build with Cursor or Claude in your ADoor space. The app reads and writes through the HTTP API with a key, your assistants query the same tables over MCP, and each person, app and assistant gets only the access you give it.

## Do I need a database for my app?

If the app has to remember anything between visits, or on more than one device, yes. A run tracker, an inventory list or a client log all need somewhere the data survives a reload and doesn't get overwritten. ADoor gives you that without running a database: describe the tables, and they're set up in your space.

**You:** I'm building a run tracker in Cursor. Set up a Runs table: date, distance in km, time, and a note.

**ADoor:** Created Runs in your space and added 2 entries

**Runs**

| Date | Distance (km) | Time | Note |
| --- | --- | --- | --- |
| Oct 19 | 8.2 | 41:10 | Hills |
| Oct 20 | 5.0 | 24:32 | Easy |

The app you build writes each run. On your phone, ask ChatGPT “How far did I run this week?” and it reads the same table.

## Access per app and person, without writing policies

On most app databases, who can read which rows is a policy you write and test, and one missing policy can leave every row public. In ADoor, access is set per person, app and assistant, down to a table, specific fields, or just the entries that match a value you choose, and Postgres enforces it on every request.

- **The app** uses only the tables and actions its key allows, such as adding runs.
- **Your assistants** read and update the same tables, each with its own access.
- **People you share the space with** each get their own access, and see only what you choose.
- Revoke a key, and the app stops on its next request. The data stays.

For apps where other people sign in, [Login with ADoor](/docs/guides/login-with-adoor/) is coming soon. It keeps each person's data in their own account.

## How to connect your app

1. **Describe the tables.** Tell your assistant what the app needs to keep, and it sets them up in your space.
2. **Give the app a key.** In ADoor, open Access and choose New connection, with only the tables and actions the app needs.
3. **Call the API.** The app sends SQL with the key:

```sh
curl https://app.adoor.halmoslabs.com/api/query \
  -H "Authorization: Bearer $ADOOR_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"sql":"SELECT date, distance_km FROM runs ORDER BY date DESC LIMIT 5"}'
```

The [API reference](/docs/reference/api/) lists every operation.

## How it compares with Supabase, Firebase or Neon

[Supabase](/compare/adoor-vs-supabase/), [Firebase](/compare/adoor-vs-firebase/) and [Neon](/compare/adoor-vs-neon/) are better for an app with many users today: sign-in for your customers, file storage, realtime and scale.

ADoor fits a tool you build for yourself or your team, where the data should outlive the app and your assistants should read it too.

## Questions people ask

### What's the best database for vibe coding?

It depends on who uses the app. For a public app with many users, Supabase is the usual pick: auth, storage and realtime in one project. For a tool you build for yourself or your team, ADoor keeps the tables in your own account, with access per person, app and assistant and no policies to write, and your assistants can read the same data.

### What happens to the data if I drop the app?

It stays. The tables are in your ADoor space, so you can keep using them from your assistants, point a new app at them, or export them as CSV or JSON.

### Can other people sign in to my app?

Not yet. Login with ADoor, which lets people sign in and keep your app's data in their own account, is coming soon. Today, people you share the space with use it through their own assistants.

### Is it free?

A free workspace holds 1 space with 3 tables and 100 rows. Pro is $10 a month per workspace, with 1 GB of storage. See [pricing](/pricing/).

## How to start

1. Sign in to ADoor and connect the assistant you build with.
2. Describe the tables your app needs.
3. Create a key for the app and call the API.

[Get your account](https://app.adoor.halmoslabs.com/signup)

## Related

- [Back an internal tool](/use/internal-tool-backend/)
- [Store a customer-facing app’s data](/use/customer-app-data/)
- [Apps come and go. Your data stays.](/apps-come-and-go/)
- [ADoor vs Supabase](/compare/adoor-vs-supabase/)
- [All use cases](/use/)

Updated October 20, 2026.