ADoorYour data account Get your account

Store a customer-facing app’s data

Your app’s data, with each client limited to the entries where Client is their name. PostgreSQL enforces that limit on every request.

Use cases All use cases

For builders

How to connect ChatGPT and Claude to the same data How to give an AI agent safe, scoped access to data A database for vibe-coded apps, with access built in

AI and engineering

Keep a daily work log Keep a prompt library for Claude, ChatGPT and Cursor Let agents build on each other’s findings Run a task queue for your agents Share agent traces across a team Share research notes Track eval results over time Start an experiment tracker Keep a model training log Keep feature flags and config agents can read Keep bug reproductions and test cases Record deploy and release history Keep an inventory of API keys and services Start a dataset registry Collect standup notes from assistants Keep an incident log Log benchmarks and latency measurements Track GPU and compute spend Start a labeling and annotation queue

Personal

Keep a side-project idea backlog Start a habit tracker Start a reading log Track what you’re learning Track subscriptions Start a budget tracker Start a movie and TV tracker Start a home inventory Keep a plant care log Keep a car maintenance log Plan your travel Keep a tasting journal Track a collection Keep notes on the people you know Track job applications Keep a vocabulary list Track important documents Keep a food log Start a training log Keep a log of your own numbers Keep a schedule of what is due and when to refill Start a recipe collection Keep a list of things to buy Share a pet care log Keep a daily journal Keep gift ideas and birthdays

Business

Track consulting time Track freelance clients and invoices Track fundraising Start a lightweight issue tracker Back an internal tool Store a customer-facing app’s data Plan a content calendar Collect customer feedback and feature requests Manage event attendees and sponsors Report from many sources Start a customer list Track sales deals Keep a customer support log Track hiring Start an employee directory and onboarding checklist Track inventory Track orders and suppliers Start an asset and equipment register Track partners and resellers Track contracts and renewal dates Keep a price list and build quotes

Collaborative

Split expenses Share a research reading list Plan an open-source project roadmap Build a shared world-building bible Plan a house renovation Start a shared household list Share a household chores rota Keep a family schedule Track kids’ activities Plan a trip with friends Plan a wedding or party Run a book club Run a sports team or club Run volunteer and community sign-ups Run a student group project Start a neighborhood tool-lending list Share a weekly meal plan Write babysitter and caregiver handover notes Plan a shift schedule Plan a carpool rota Share a packing list Coordinate help for a parent

An example

@ADoor Set up storage for our client portal: Clients, Projects and Messages. Each client should only ever see their own projects and messages.

ADoor Started Clients, Projects and Messages. Each client’s access can be limited to the entries where Client is their name, one grant per client

Projects

ClientProjectStatusUpdated
CalderWebsite redesignIn reviewOct 20
RidgewayBrand guideIn progressOct 18

What you can ask later

  • “Which projects haven’t been updated in two weeks?”
  • “Show project status counts per client.”
  • “Who changed the Calder project status, and when?”
  • “Add a Due date field to Projects.”

Who can see what

  • Each client reads and writes only the entries where Client is their name, set once per client and enforced by PostgreSQL on every request.
  • Your team sees every client.
  • Your app’s server uses an API key limited to the lists it needs.
  • An agent that answers client questions can be limited to the one client it’s helping.

How it compares with Supabase or Firebase

Supabase and Firebase are better for apps at scale: SDKs for every platform, auth for your end users, file storage, realtime and years of production use. ADoor doesn’t publish latency figures, and Login with ADoor and its SDKs are coming soon.

Pick ADoor when access is the hard part. Every person, app and agent gets its own access down to specific fields, or just the entries that match a value you choose, an agent never exceeds the person who connected it, and the history shows every change.

How to start

  1. Open an assistant like ChatGPT, Claude, Grok or Cursor and connect ADoor through MCP.
  2. Tell it: “Set up the data for our client portal: describe each list and who should see what, then create an API key for the app.”
  3. Create an API key for your app’s server, limited to the lists it uses.

Get your account

Questions people ask

Does ADoor handle my end users’ sign-in?

Each client signs in to ADoor itself, with access limited to the entries where Client is their name. You give each client that limit when you invite them. Your app’s server talks to ADoor with its own key, limited to what it needs.

Can I use plain SQL?

Yes. Standard Postgres SQL, within each caller’s access.

How much does ADoor cost?

The free plan holds 3 tables and 100 rows, enough to start a list like this. Pro is $10 a month per workspace, with 1 GB of storage and no per-GB charges.

Can I export everything?

Yes, as CSV or JSON, whenever you want. Ask your assistant for the export or download it yourself.

Updated October 20, 2026.

This page as Markdown