Platform
Identity, organisations, and access — solved once.
The Oidot platform provides the capabilities every product needs and no product should rebuild. One identity across the ecosystem, organisations that own their membership, and explicit control over which organisation can use which product.
The same foundation, rebuilt every time
Every data product needs the same things before it can do anything interesting: someone has to sign in, belong to a company, be granted access, and be billed for it. It is unglamorous work, and it is usually rebuilt from scratch for each new product.
The cost is not the first build. It is the fourth — four user tables, four permission models, four billing integrations, each subtly different, none of them the system of record. Users end up with an account per product. Administrators end up managing access in four places.
A platform layer with a hard boundary
Oidot's platform owns identity, organisations, product entitlement, and billing — and nothing else. It contains no product business logic by design.
That boundary is the point. Because the platform holds only what is common and stable, products built on it stay genuinely independent: each owns its own data and its own runtime, and can be built, changed, scaled, or replaced without disturbing the foundation or the other products.
Identity
One account per person across every Oidot product. Registration and authentication, password hashing with modern algorithms, and short-lived access tokens paired with rotating refresh tokens.
Organisations
Any user can create an organisation and becomes its owner. Owners invite and remove members and assign roles. Users belong to many organisations; organisations use many products. Invariants are enforced at the platform — an organisation always retains at least one owner.
Product entitlement
A registry of Oidot products and an explicit record of which organisation may access which. Entitlements are carried as claims inside the issued token, so a product can authorise a request without a round trip to the platform.
Billing and subscriptions (planned)
Plans and subscriptions are held per organisation, and an active subscription grants the matching product entitlement. Access follows billing state rather than being maintained separately. Payment-provider integration is not built yet — it is the last phase of the platform roadmap, deferred until there is something to sell.
Built to be built on
The platform is in active development. If you are interested in what we are building, or in building with us, get in touch.