ADoor vs Hasura DDN
Hasura DDN puts one API over the databases you already have, with permissions defined in metadata. ADoor is the data account where the records themselves live, with Postgres underneath, and every person, app, assistant and job gets its own access.
Where ADoor stands out
Approvals and per-agent caps
Hasura already has row-level and field-level permissions per role. ADoor adds approvals: agents ask for more access, and an assistant never gets more than the person who connected it.
A hosted MCP server
Hasura's PromptQL MCP server is open source, runs locally and is marked unstable. ADoor's MCP server is hosted, with an OAuth sign-in.
Nothing to build
Hasura permissions are written in metadata and need a new build. In ADoor, you describe what to keep in an assistant like ChatGPT.
The products
Hasura DDN
Hasura DDN is a data delivery network: a supergraph API over many data sources.
- Access
- ModelPermissions for rows, TypePermissions for fields, CommandPermissions for commands
- Assistants
- An open-source PromptQL MCP server
- Plans
- DDN Free. DDN Base from $5 per active model a month.
ADoor
ADoor is your data account. You keep lists and tables in a workspace you own, personal or team: a reading list, an incident log, a list of customers. Describe what you want to keep track of and it's set up for you, with real Postgres underneath. Every person, app, assistant, device and job gets its own access.
- Assistants
- ChatGPT, Claude, Grok and Cursor connect through MCP with a sign-in.
- Apps and scripts
- An HTTP API with keys, running the same actions assistants use
- Access
- Per space, list or field, or just the entries where a field equals a value you choose. Reading, adding, editing and deleting entries, and changing a list's fields, are separate permissions. An assistant never gets more than the person who connected it.
- Approvals
- Agents ask for more access and you approve or deny. A new device signs in only after you approve it and choose its access.
- CI jobs
- GitHub Actions signs in with short-lived access, 15 minutes by default and up to 30 days, with no stored secret.
- Revoking
- Takes effect on the next request. What was already saved stays.
- History
- A history of changes, with who made each one and the before and after
- Underneath
- Standard Postgres
- Plans
- Free for 3 tables and 100 rows. Pro is $10 a month per workspace, with 1 GB of storage.
Pricing
| Topic | ADoor | Hasura DDN |
|---|---|---|
| Free plan | 3 tables and 100 rows, with a few MB of storage | DDN Free |
| Paid plans | Pro: $10 a month per workspace, 1 GB of storage, no per-GB charges | DDN Base from $5 per active model a month |
Latency
| Topic | ADoor | Hasura DDN |
|---|---|---|
| Published figure | Not published | Not published |
ADoor doesn't publish a latency figure, and Hasura DDN doesn't publish one we could find. Speed depends on your network and on what you ask for.
Connectors and API
| Topic | ADoor | Hasura DDN |
|---|---|---|
| MCP server | Hosted, with OAuth sign-in. ChatGPT, Claude, Grok and Cursor. | Local, open source, marked unstable |
| HTTP API | HTTP API with keys: read, add, edit, delete, and change lists and fields | GraphQL |
| SQL access | Standard Postgres SQL through MCP and the API, within your access | Through your connected databases |
| Access per agent | Its own access per assistant, app, device and job, down to specific fields, or just the entries that match a value you choose | Role-based permissions |
| OAuth or tokens | OAuth for assistants, keys for apps, short-lived sign-in for GitHub Actions | PromptQL API key plus DDN auth token |
| SDKs | Coming soon | Not published |
| Webhooks | No | Not published |
| Import and export | Export to CSV or JSON. Import by attaching CSV or JSON in an assistant. | Not published |
ADoor has no sync connectors and no file storage.
Which one should you use?
Use Hasura DDN when
you have many databases and want one governed API across them.
- Many sources. One supergraph over your existing data. ADoor doesn't connect to outside databases.
- Fine-grained permissions. Row and field permissions per role. Hasura is strong here.
- Enterprise governance. SOC 2 Type 2 and GDPR compliance on DDN.
Use ADoor when
you need a place for records that don't live anywhere yet, with per-agent access set from a chat.
Technical
- A GitHub Actions job writes each schema review to ADoor with short-lived access, while your APIs stay on Hasura.
- An agent that triages data quality issues adds entries to Issues and asks before editing.
Personal
- Your band's setlists and who plays what. Bandmates edit, the sound tech reads.
- Your children's vaccinations and checkups, shared read-only with their other parent.
Team
- Data, platform and analytics share a Data contracts list with separate edit rights.
- A history of changes shows who changed each contract and what it was before.
- Support adds customer reports to an add-only list that engineers read.
Business
- Each domain team edits only its entries in a company-wide Data catalog.
- A consultancy reads one space for a project, and you revoke it afterwards.
Questions people ask
Is ADoor an API layer?
No. ADoor keeps its own records and doesn't connect to your databases.
Does Hasura already have field permissions?
Yes. ADoor's difference is per-agent caps, approvals, short-lived CI access and setup from a chat.
Which assistants work with ADoor?
ChatGPT, Claude, Grok and Cursor connect through MCP with a sign-in. You approve each one and choose what it can reach.
Start
More comparisons
Checked October 20, 2026. Sources: hasura.io/pricing, Hasura permissions, PromptQL MCP.