Operator Console

Operator Console

What it is

ops.id-me.ai is the manager's view of the whole platform on one page, the way an analytics dashboard shows a website: whether every host is up, how much traffic the site gets and from where, who signed up, what the production and sandbox tenants are doing, which Contact Sales inquiries are waiting, and where the project is being talked about. It reads live sources; nothing on it is typed in by hand.

It is one Cloudflare Worker (platform/ops), deployed from the repository like everything else, and it writes to exactly one thing: the status and notes on an inquiry.

What is on the page

Section	Source	What you see
Health	A request to each host	Whether id-me.ai, api.id-me.ai, sandbox.id-me.ai and auth.id-me.ai answer, and how fast
Site traffic	Cloudflare zone analytics for id-me.ai	Page views, visits, top pages, referrers, countries and status codes for the last 1, 7, 30 or 90 days, with sparklines
Repository	GitHub	Stars, forks, watchers, open issues, latest release, and with a token the repository's views, clones, referrers and popular paths
Production	The production database	Tenants and signups, identities, active keys, projections served, audit events, runs, and the newest tenants
Sandbox	The sandbox database	The same figures for self-serve signups
Inquiries	The intake database behind Contact Sales	Every inquiry with company, size, region, interests, timeline and message; set status (new, contacted, qualified, closed) and keep notes
Mentions	Hacker News, Reddit and GitHub search	Where id-me.ai is being discussed, which is the early signal of a launch catching
npm	The npm downloads API	Weekly and monthly downloads once the package is published

Every source that is not configured says so, with the reason, instead of showing a blank. The page is never allowed to pretend.

Signing in

The console has its own sign-in page. The username is admin (the OPS_ADMIN_USER variable) and the password is the OPS_ADMIN_PASSWORD secret set on the Worker in the Cloudflare dashboard; it is never stored anywhere else and never shown again. A successful sign-in sets a signed, HttpOnly, SameSite=Strict session cookie that lasts twelve hours. Five wrong attempts from one address inside fifteen minutes lock that address out for fifteen minutes, and the counter lives in the shared database, so the lockout holds across every Worker instance. Changing the password signs everyone out.

Cloudflare Access can be used instead, which lets operators sign in with their Google Workspace accounts and lets you manage who has access from the Zero Trust dashboard. When Access is configured it takes precedence and the built-in page is not served. With neither configured the Worker answers 503 to everyone; a misconfiguration fails closed rather than exposing traffic and customer data.

What it needs to show everything

Need	Where it goes	Why
OPS_ADMIN_PASSWORD	Worker secret	Sign-in
CLOUDFLARE_API_TOKEN with Zone Analytics Read and Zone Read on id-me.ai	Worker secret	Site traffic
GITHUB_TOKEN with push access to the repository	Worker secret, optional	Repository traffic (views and clones); public figures work without it
NPM_PACKAGE	Worker variable	Downloads, once published

The three database bindings (intake, production, sandbox) are in the Worker configuration already.

Why a console and not a spreadsheet

Because the questions it answers are the ones that come up every morning of a launch: is everything up, did the post land, who came in overnight, what should sales call first. Having them on one page, with the data read live from the systems that own it, is the difference between running a launch and reconstructing one.