Gate Studio
Gate Studio is the visual command centre for authoring against Gate — Kilimanjaro's Identity-Aware Kernel — without writing JSON-policy expressions by hand. Pathmaker-authored login pages, Maker-Checker registration flows, jurisdictional ingress policies, branded UI, and white-labelling all compose through Gate Studio's authoring surface and ship as live Gate configuration.
Gate Studio is built on the same extension framework available to every extension class — Anchor and Circuit extensions ship against the same contract.
1. What Gate Studio covers
| Surface | Role |
|---|---|
| Login-page authoring | Visual editor for branded sign-in / sign-up / passwordless / passkey / social-provider flows. White-labels to the customer's domain. |
| Maker-Checker registration | Author Gate-issued account-creation flows that route through approval policies before the new end-user record commits |
| Jurisdictional ingress policies | Per-region access controls composing against the Native-mode auto-scoping the gateway applies for end-user JWTs |
| Theme tokens | Per-project theme overrides — colour palettes, typography, illustration set, copy register, embedded asset management for customer-visible Gate surfaces |
| White-labelling | Custom domain binding (e.g., auth.customer-domain.com), email-sender domain, transactional-email template overrides |
| Multi-tenant authoring | Per-tenant configuration overrides for B2B-platform customers serving identity to their own customers |
Gate Studio is a full-surface extension: Console UI + runtime API + background-logic functions.
2. Authoring a login page
The canonical workflow:
- Start from a template. Gate Studio ships a set of starter templates — minimalist, brand-prominent, password-led, passwordless-led, B2B-focused. Each starter is a sane default that can be edited.
- Configure methods. Toggle email/password, magic link, OTP, passkeys, MFA, and any configured identity providers (OIDC, SAML, OAuth2, AD/LDAP). Methods rendering on the page are bound by the project's enabled Gate configuration; Gate Studio cannot enable a method that isn't configured.
- Theme. Apply project theme tokens — Gate Studio surfaces a live preview so the brand-mark, palette, and copy register settle visually before publish.
- Compose copy. Override default headings, labels, error messages, and CTAs. Multi-language overrides are first-class — translation strings bind per locale.
- Bind to a domain. Production traffic comes from either the platform-hosted Gate domain (
<project>.gate.k9o.io) or a custom white-label domain. Domain binding triggers DNS-verification and certificate provisioning. - Publish. Publishing makes the login page live; existing in-flight sessions continue against the prior configuration; new sign-ins hit the new page.
3. Maker-Checker registration flows
For projects where Gate-issued account creation must be approved before the end-user record commits, Gate Studio authors a Maker-Checker registration flow:
- Sign-up path — a user completes the sign-up form on the Gate login page.
- Pending registration — the platform creates a pending-state end-user record; no JWT is issued yet.
- Approval routing — the registration enters an approval queue per the project's Maker-Checker policy bound through Control. Approver(s) — typically
PROJECT_ADMINor a delegated role — review and decide. - Commit or reject — approval commits the end-user record to the project and emits a verification email; rejection drops the registration and notifies the would-be user with a configurable message.
Gate Studio surfaces this flow as a visual graph — input form → review queue → decision branch → terminal states — that Pathmakers wire without hand-authoring the underlying policy expressions.
4. Jurisdictional ingress policies
Per-region ingress decisions — which jurisdictions can issue tokens, what additional verification a particular region triggers, which regions are blocked outright — compose visually in Gate Studio against the gateway's per-request ingress check.
| Decision point | Authored as |
|---|---|
| Region allowlist / blocklist | Inclusive or exclusive list of ISO 3166-1 alpha-2 country codes |
| Per-region MFA elevation | Configure regions that require step-up MFA even for users who haven't enrolled an MFA factor in their profile |
| Per-region session policy | Tighter idle / absolute session timeouts for sensitive jurisdictions |
| Per-region webhook trigger | Fire a configurable webhook on every sign-in from a flagged region (e.g., for SIEM alerting) |
Ingress decisions compose against the Native-mode auto-scoping the platform applies to end-user JWTs — Gate Studio ingress rules govern whether a JWT issues; auto-scoping governs what data the issued JWT can reach.
5. Theming and white-labelling
The Gate Studio theme system is token-based: colour, typography, spacing, illustration, copy register all bind as named tokens that compose into the rendered surface. The theme applies to:
- The login page itself.
- Transactional emails (verification, password reset, magic link, MFA enrollment, invitation, email change).
- Embedded Gate widgets if used in a customer application.
White-labelling extends theming with custom-domain binding (auth.customer-domain.com), custom email-sender domain ([email protected]), and removal of the platform brand-mark from rendered surfaces. White-label binding is available to every project.
6. The @k9o/gate-studio package
Gate Studio ships its own SDK package, @k9o/gate-studio, separate from the core @k9o/sdk and @k9o/kibo packages. The package surfaces:
- A React-component library for embedding Gate Studio-authored surfaces (login pages, registration flows) into custom applications.
- A programmatic API for reading the project's current Gate Studio configuration (useful for server-side rendering and for white-label provisioning workflows).
- Type definitions for the theme-token schema and the ingress-policy expression language.
The package mirrors the standalone-SDK pattern @k9o/gate follows — install once, compose with the rest of the platform when needed.
7. Permissions Gate Studio requests at enable
| Permission | Why |
|---|---|
documents/read,write/* qualifier-bound to the Gate Studio configuration collection | Authoring + persisting login-page / flow / theme / ingress configuration |
collections/read/* | Reading project schemas referenced by Maker-Checker approval flows |
users/read/* | Resolving approver identity for Maker-Checker routing |
files/read,write/<gate-studio-assets-bucket> | Storing brand assets (logos, illustration sets) |
functions/invoke/gate-studio:render | Server-side rendering of login-page previews |
webhooks/subscribe/* | Reacting to auth.identity_provider.* events for provider-configuration syncing |
The grant binds at enable time; PROJECT_ADMIN reviews each line before authorising.
8. Events
| Event | Fired when |
|---|---|
gate-studio.login-page.published | A new login-page version goes live |
gate-studio.flow.committed | A Maker-Checker registration flow finalises (after approval or rejection) |
gate-studio.ingress-policy.changed | A jurisdictional ingress policy is updated |
gate-studio.theme.published | A new theme version goes live |
9. See also
- Extensions API reference — the framework contract Gate Studio installs against.
- API → Auth — the underlying Gate API surface Gate Studio composes against.
- Identity-Aware Kernel — the conceptual model of Gate's two consumption paths.
- Architecture → Architecture — Native-mode auto-scoping that Gate Studio's ingress policies compose with.
- API → Control — JSON-policy layer Maker-Checker registration flows generate.
- Gate Overview — Gate Standalone vs Native consumption paths.
- Gate Migration — migration paths from third-party identity vendors.