ADoor vs Nhost
Nhost is an open-source backend on Postgres with a GraphQL API, auth, storage and functions. ADoor, your data account, keeps records a team or a company shares, with Postgres underneath, where every person, app, assistant, device and job has its own access.
Where ADoor stands out
Capped at the person who connected it
Nhost already has role-based permissions, and recommends a dedicated GraphQL role for AI access. ADoor adds a rule you don't configure: each assistant gets its own access and never more than the person who connected it.
Approvals
When an agent in ADoor needs more, it asks and you approve or deny. A new device signs in only after you approve it.
Set up from a chat
In Nhost, roles and permissions are part of your backend setup. In ADoor, you describe what to keep in an assistant like ChatGPT, and the list and its access are set up for you.
The products
Nhost
Nhost combines Postgres, GraphQL, auth, storage and functions in one backend.
- Assistants
- Backend MCP, using Nhost Auth OAuth2 for end users, or an admin secret or personal access token for developers
- Access
- GraphQL roles, including a dedicated role for AI
- Change history
- Point-in-time recovery from $100 with 7 days of retention
- Plans
- Starter free (1 project, paused after a week of inactivity). Pro from $25 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 | Nhost |
|---|---|---|
| Free plan | 3 tables and 100 rows, with a few MB of storage | 1 project, paused after a week of inactivity |
| Paid plans | Pro: $10 a month per workspace, 1 GB of storage, no per-GB charges | Pro from $25 a month, Team from $599 |
Latency
| Topic | ADoor | Nhost |
|---|---|---|
| Published figure | Not published | Not published |
ADoor doesn't publish a latency figure, and Nhost doesn't publish one we could find. Speed depends on your network and on what you ask for.
Connectors and API
| Topic | ADoor | Nhost |
|---|---|---|
| MCP server | Hosted, with OAuth sign-in. ChatGPT, Claude, Grok and Cursor. | Backend MCP per project |
| 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 | Postgres |
| 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 | A GraphQL role for AI access |
| OAuth or tokens | OAuth for assistants, keys for apps, short-lived sign-in for GitHub Actions | Nhost Auth OAuth2, admin secret or personal access 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 Nhost when
you're building an app with GraphQL and want role-based permissions in your own backend.
- Field and row permissions. GraphQL roles control what each role sees. Nhost already has the fine-grained model many tools lack.
- A full backend. Auth, storage and functions included.
- Open source. Nhost can be self-hosted.
Use ADoor when
you want the fine-grained access too, but for every assistant, device and job without setting up roles.
Technical
- A GitHub Actions job writes each migration to a Migrations list with 15 minutes of access and no admin secret.
- An agent in production reads Feature flags and asks before it can edit them.
Personal
- Christmas card addresses, who sent one last year and who moved. Your partner edits too.
- Your sneaker collection with sizes and what each is worth.
Team
- Backend, frontend and support share a Known bugs list where support adds and engineers edit.
- A history of changes shows who changed each bug's status and what it was before.
Business
- A partner's assistant reads only its customers, capped at the partner's own access.
- An agency's access ends the day you revoke it, and its entries stay.
Questions people ask
Nhost has roles. Why ADoor?
For per-agent access capped at the connecting person, approvals, short-lived CI access and setup from a chat.
Does ADoor have GraphQL?
No. ADoor has MCP and an HTTP API, with SQL through both.
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: nhost.io/pricing, Nhost Backend MCP.