What it does
Platform accounts are operator identities. They hold a role of super_admin, admin, editor or viewer, belong to organisations, and reach the administration plane. They sign in without a project key, are managed by administrators over HTTP or with the kynetra admin command, and can be protected with TOTP and an organisation MFA mandate.
How it works
The first platform account created on a fresh deployment becomes admin and later sign-ups become editor. A deployment can also seed a super_admin at start: set KYNETRA_SUPERADMIN_EMAIL together with KYNETRA_SUPERADMIN_PASSWORD, which must be at least 16 bytes and use at least three character classes, and the primary creates that account when no super_admin exists. A replica refuses to start with the email variable set, because the account replicates from the primary.
Administrators list and create accounts with GET and POST on /v1/auth/users, change a role or display name with PATCH on /v1/auth/users/:id, set a password with POST on /v1/auth/users/:id/password, which revokes that user's sessions, and clear a second factor with POST on /v1/auth/users/:id/2fa/reset. A super_admin is required to grant super_admin, nobody can change their own role, and when the acting administrator has a second factor enrolled each sensitive action needs a fresh step-up token. The kynetra admin command wraps the same routes and can fan out across several instances listed in a local instances file.
Platform sessions are bound to the context they were issued under: the account's organisation memberships, the MFA policy version of each organisation and a per-account epoch. A renewal is refused when any of those changed since the session was issued, so removing a member or switching on an MFA mandate ends their existing renewals.
Organisations hold members with owner, admin or member roles. Organisation owners and admins manage that organisation's projects, keys and security policy through /admin/v1.
Where you reach it
- HTTP
POST /v1/auth/signup, POST /v1/auth/login, GET /v1/auth/me - HTTP
GET|POST /v1/auth/users, PATCH|DELETE /v1/auth/users/:id - HTTP
POST /v1/auth/users/:id/password, POST /v1/auth/users/:id/2fa/reset - CLI
kynetra admin users | create-user | set-role | set-password | delete-user - SDK
TypeScript AuthClient: signup, login, me, listUsers, createUser, deleteUser - Config
KYNETRA_SUPERADMIN_EMAIL, KYNETRA_SUPERADMIN_PASSWORD
Limits
- Platform accounts and the global key are operator credentials with deployment-wide authority. Issue them only to operators, and keep operator endpoints off the public internet.
- Keep operator endpoints, including platform account creation, reachable only by operators.
- The first account created on a fresh deployment receives admin. Seed a super_admin, or create the first account yourself, before the server is reachable by others.
- The legacy /v1/auth/login route returns a single access token and no refresh token. The TypeScript SDK login helper expects that shape and does not handle an MFA challenge, which must be completed through the HTTP routes.
- No sign-in throughput figure is published for this edition.
Evidence
- On this siteAPI reference: authentication endpoints
- On this siteSecurity overview
- Tests8 server tests for step-up gating, forced enrolment, notices and session replay, and 39 control-plane tests that include refresh fencing when MFA policy, membership or factor state changes
Test coverage is listed as present in the engine repository at this edition. This page does not report test results.
KynetraDB is in private preview
Request a preview to talk through the limits above against your own workload.