Skip to content

Security model

One rule explains the whole architecture: every arrow points outward. Nothing we run can open a connection to anything you run.

Our side Your cluster
Relay · rustls, step-ca · api.vedavid.dev:8443 ← mTLS, outbound only Connector · read-only
Admin console and API · Cloudflare Workers, D1 Prometheus
The app, signed in with a short-lived token Samples · never leave

Connector to relay. The connector is enrolled with a token from the console, exchanged for a client certificate issued by the relay’s own certificate authority. The token is the only input to the identity; a certificate request cannot choose its own name. The connector dials the relay over mutual TLS and keeps the connection open; the relay routes a phone’s queries down it and never connects back.

Phone to relay. Signing in exchanges an emailed code for a token the console signs, valid for three days, naming the person and their organisation. The relay verifies the signature against the console’s published keys, so a query is answered only for the organisation the token names, and only through that organisation’s connectors.

People to the console. A six-digit code by email, valid for ten minutes and for one use, with five attempts before it is refused. There are no passwords. The link in the email opens the code screen and nothing more; only pressing the button redeems the code, so a mail scanner that follows links cannot use it.

people and organisations Email addresses, organisation names, verified domains, who belongs where and with which role.
connectors Each connector’s name, a hash of its token, when it enrolled, when it was last seen, and whether it was revoked. Never the token itself, and never the private key, which is generated in your cluster and stays there.
sign-in records Every code issued, with when it was used, from which address and client, so a sign-in can be audited. Codes are stored hashed.
not samples Query results pass through the relay in memory and are never written on our side. Dashboards live in your repository and reach the relay only as the render tree the app draws.

Authorisation is your cluster’s job, and the connector asks for none. The chart ships no Role or ClusterRole, the pod’s service account token is not mounted, and the container runs as an unprivileged user with a read-only filesystem and every capability dropped. It talks to one thing, the Prometheus URL you give it, so the phone can see exactly what that Prometheus holds and nothing else. Dashboards reach it as files in a ConfigMap, which is what keeps that true.