Login with ADoor
Coming soon. Login with ADoor will let people sign in to your app with their ADoor account and keep your app's data in a space inside their own data account. The SDKs are coming soon too. Nothing on this page can be installed yet.
The model
- Identity and storage together. A person signs in to your app with ADoor. On first sign-in, they approve a new space for your app's data and the access your app gets, such as reading and adding entries in that space only.
- No user database for you to run. Your app reads and writes its tables in each person's space, with the access that person approved.
- The person keeps the data. If they stop using your app, the space stays in their account. They can export it, and their assistants can still read it.
- Revocable. The person can take your app's access back at any time. It applies from the next request.
How it differs from Sign in with ChatGPT
Sign in with ChatGPT gives your app a person's ChatGPT identity, and for some apps the use of their ChatGPT plan for AI requests. It does not give your app a place to store that person's data. Login with ADoor is identity plus storage: the data your app saves lives in the person's own account.
What works today
The same consent model already runs for assistants and your own code:
- Assistants. ChatGPT, Claude, Grok and Cursor connect over MCP with OAuth. The person chooses the space, approves the access, and can revoke it. See Connect.
- Apps you build for yourself or your team. Use the HTTP API with a key from Access, then New connection, limited to the tables and actions the app needs.
- Jobs. GitHub Actions signs in with short-lived access and no stored secret. See Workload identity.
What doesn't exist yet: a sign-in button for your app's users, the consent screen for a new app space, and the SDKs.
Status
There is no release date yet. To hear when it ships, email support@halmoslabs.com.