The Hub
One account for every platform you use.
Somebody who belongs to two of our customers’ platforms used to have two logins and no way between them. The Hub ends that: one identity, the platforms you belong to in one list, and one click into any of them — arriving already signed in.
How it works, for engineers
It is for the people who use the platforms our customers run — not for the makers who build them. Makers already have the Console.
Status
Live. Sign up, and one click opens a platform already signed in.
The Hub is live at app.alodai.com. You sign up, verify your address, and see the platforms you belong to listed for you. Opening one takes you inside it already signed in — through a single-use link, valid for sixty seconds, that mints that platform’s own session for you.
Live
Two things are not there yet: there is no way back into the Hub from inside a platform, and a Hub account has no second factor or provider sign-in — the tables are there and the routes are not.
How it works, for engineers
The architecture decision is on the record — ADR-072, a third identity plane alongside Console makers and per-platform end-users — and it is accepted. The plane, the app, the address and the bridge are all in production: sign-up, email verification, the claim that links a verified address to the platform identities already carrying it, the launcher, account management, and the single-use code that mints a tenant’s own session when you open a platform. Two named pieces are not: signing back into the Hub from a platform, which has no route and no ticket, and MFA or provider sign-in on a Hub account, whose tables exist and whose routes do not. The facts pod is no longer one of them — its tables, its read door and its screens are built.
What it holds
What the Hub holds, and what it will not.
A launcher
The platforms you belong to, in one list, each one a way in rather than a second login.
One sign-in
Your sign-in held once, for you, instead of once per platform: you authenticate at the Hub and enter a platform without a second password.
A way in, not a merge
Entering a platform hands you that platform’s own session. Nothing you hold in the Hub is ever presented to a company whose product you use.
Linked by a verified address, then held for good
Your account is attached to a platform identity only after the address is verified — and changing your email later never silently re-maps who you are.
Facts you grant, and can withdraw
A place for facts about you that a platform may read only through a grant you gave it and can take back — every read logged for you to see.
What it is not
No products, no content, no company’s data, and no second website. The Hub is who you are and where you can go. The products are the platforms.
Deleting your account unlinks the platform identities it gathered and leaves them where they belong. It does not reach into a company’s product and delete their record of you — that is your relationship with them, not with us.
How it works, for engineers
Entering a platform mints that platform’s own session through a single-use code; the Hub’s session is never presented to a tenant and no cookie spans the two. A platform identity is attached to an account only when the email has been verified, and afterwards the link is held by id.
The facts pod is built: four tables, a closed versioned registry of scopes and keys, one read door a platform’s server calls with a credential that is itself the caller’s identity, and the screens where a person grants, revokes, exports and erases. By decision rather than omission, the Hub carries no modules, no content, no tenant data and no second marketing site.
app.alodai.com · hub_bridge_tokens · platform_users.account_id
The Hub · next step
It is open. Create an account at app.alodai.com.
There is no waitlist and no invite: create an account today, and the platforms you belong to are already there. If you run a platform and want the people who use it to arrive through the Hub, say so in a message.