See it

Two surfaces, and both of them ship with the product. On one side, the pages your users meet - sign-in, the navigation bar, the account menu - already wearing your colours. On the other, the console an operator lives in.

Get started
What it does

What your users meet

These pages are served by the gateway itself. Nothing in the application behind them ships a line of code for this: the colours, the logo and the navigation come from the console.

The sign-in page — The sign-in page, with your name, your logo and your palette. Passkeys sit beside the password, not behind an option.

The sign-in page in dark — The same page in dark, with its own background picture if you want one.

The navigation portal — One bar across every application the gateway serves, filtered by what the visitor may open.

The navigation portal in dark — The visitor's colour scheme is carried into the proxied application, even when the application has its own.

The account menu — The account button: who you are, the language, the light and dark switch, and the way out.

A route under maintenance — A route closed on purpose answers a page, with a reason, rather than a 503 nobody can read.

Routing

The routes screen — Every route in order, what it matches, where it goes, and whether it is on.

A route's target — The upstream, and what the gateway offers to fill it in with.

Predicates — The conditions a request must meet for this route to take it.

Filters — What happens to the request, and to the answer, on the way through.

Per-endpoint security — A rule per operation, read from the service's own OpenAPI description.

Identity and access

Users — The accounts, what they can administer, and the fields you decided to ask for.

Roles — A hierarchical catalogue: a role that inherits another gets everything it opens.

Groups — Groups per organisation, so a role is granted by membership rather than one by one.

Members — Who belongs to an organisation, and as what.

Authorities — OpenID Connect, LDAP, Active Directory, GitHub. They authenticate; they never decide roles.

API tokens — Tokens with a plane and a perimeter, and a secret shown exactly once.

Looking after it

Traffic — Live traffic with nothing to install: requests per second, mean and p95 latency, refusals told apart from failures, and the routes ranked by slowest, failing or costliest.

The audit trail — Every administrative change, with its author and a field-level diff.

The vault — Secrets sealed at rest and plain values, both referenced by name.

Domains & TLS — Certificates, their names and their expiry, issued or uploaded.

Configuration — The whole installation as one document, to export and replay elsewhere.

Making it yours

The theme — A palette built from one seed colour, in light and in dark, applied to every page the gateway serves.

Branding — The name, the logo, the tagline and the background picture.

The portal editor — The navigation bar, arranged: modules, submodules, icons, and a live preview.

General settings — What this installation is, and the policies every account lives under.

The agent endpoint — MCP on the control plane, so an assistant can work under the same rules.