Owner only
Admin
Checking who you are…
Locked out? Use a recovery code
For the owner only, when Google, Microsoft and the e-mail link all fail. Each code works once and every use is e-mailed to the alert address.
Loading…
What is this?
Reading the owner services.
Health
What is this?
What is switched on, and whether last night's jobs worked. A variable is shown by its name only, set or not set — never its value.
What is this? Configuration
Configuration
| Variable | State | What it does |
|---|---|---|
| Loading… | ||
Numbers at a glance
Loading…
journeys published
dots on the coverage map
teams (accounts that own one)
Qualified leg
What is this?
The paid third timestamp authority, read from the ledger of real draws — the nightly anchor, paid stamps, renewals — never from a probe. Counts are a floor; the supplier's own ledger is authoritative. Slot names are printed here and on no public page.
Reading…
Supply
What is this?
What the ladder has promised at full included use over the guard's horizon (a year, unless the card names fewer months), against the qualified tokens on file. A floor, not a forecast: the trial tokens already drawn count, unspent trial grants and managed renewals sit outside it, and the supplier's ledger is authoritative. A trial draws a qualified token only while there is room to spare. The till refuses a rung or a block that would push the promise over the supply; the owner's account is the one exception.
Reading…
Log founder minutes
What is this?
Minutes you spent on accounts — onboarding, support, chasing a supplier on someone's behalf. Nothing measures this; what you log here is all the fifth number has. Each entry is added to the running total, never written over it.
What is this? Definitions
Every figure is a count over the account records this deployment holds, taken at the moment the page loaded; nothing is cached and nothing is sampled. A request is a hand-off request the desk created; a deposit is a supplier record that landed on one. A paid period is what meter.mjs calls entitled: a plan other than the trial, paid through a date still ahead. The scan stops at 5,000 accounts and says so. No e-mail, no account id and no key leaves the route — it answers numbers. The definitions in full are in the repository, docs/OPS-DASHBOARD.md.
Scheduled jobs
What is this?
Schedules and next invocations are UTC. Last results come from the existing status store. Recording starts with this release; no recorded run is not evidence of a failure. A disabled job still receives its scheduled invocation and records that it skipped work.
| Job | Schedule (UTC) | Last run | Result | Next run |
|---|---|---|---|---|
| Loading… | ||||
Feature switches
Switch released features on or off here. Changes apply to new page loads and the server operations connected to that feature; an offline page keeps its saved version. Scheduled jobs and provider services have separate service gates. A disabled switch explains the release or service gate that still needs to be met.
| Feature | State | What it does | How to switch |
|---|---|---|---|
| Loading… | |||
Backups
What is this?
Every night at 03:30 UTC everything is copied, encrypted with your backup key, read back and compared. Test the latest backup goes further: it opens the newest archive with the key, restores it into empty scratch storage, reads it all out again and compares every byte — a full restore rehearsal that touches nothing live. Download an archive now and then as your own offline copy: it stays encrypted, and only your backup key opens it.
Archives kept
| Day | Size | Key | |
|---|---|---|---|
| Loading… | |||
After any real restore, replace the entire admin recovery-code set and rotate the session secret before reconnecting. A scratch test does not perform or verify those steps. A full restore onto the live site is deliberately not a button: it is the runbook's command (docs/BACKUP-AND-RESTORE.md), run with the archive and the key on your own computer, into empty storage.
Customers
What is this?
Look someone up by e-mail. Grant or remove qualified stamps (a reward, a reimbursement), give a complimentary plan for some months, or add a private note — all without Stripe, and every action lands in the audit log. Granted stamps use the same qualified supply as bought blocks; see operating numbers for the headroom.
Loading…
| Account | Joined | Plan | Stamps used (period) | Last active |
|---|---|---|---|---|
| Loading… | ||||
Monthly stamp promotions
Add a month, half or quarter of the current plan's included qualified stamps, or a custom amount. All promotions together are capped at 3× the plan's monthly allowance per account per billing period. Existing usage, bought blocks and billing dates stay unchanged. The grant expires at the current period's end.
Free has a one-time trial grant and Stand has no included monthly qualified allowance, so neither is eligible. Batch previews freeze the recipients; processing takes one account per step. Ops receives a summary; recipient copies honour receipt preferences. Notifications can remain queued when mail capacity is unavailable.
Activation is held.
| Account | Stamps | Expires | State |
|---|
Look up one customer
Qualified stamps
Complimentary plan
The customer gets the plan's monthly stamps and features until the end date, with no charge. Refused for someone Stripe already bills — change that in Stripe.
Paid outside Stripe
Record a direct bank transfer only after the funds have arrived.
This manual record prepays a monthly plan. Included stamps renew monthly; entering 12 prepaid months does not grant the paid annual stamp pool. Annual checkout uses a separate paid-invoice process.
A numbered receipt acknowledges received funds. It is not a tax invoice. Use the bank's unique transfer reference. Original payment commands are retained so an interrupted record can be recovered.
Private note
Earlier stamp grants
Review earlier grants here. New grant controls remain held until provider readiness and their own acceptance checks are complete. Existing balances and audit history are retained.
| Made | Stamps | Used | Until | Note | |
|---|---|---|---|---|---|
| Loading… | |||||
Access — your ways back in
What is this?
If one way fails, another still works. Keep at least three.
- Your owner e-mail, with any of the three sign-ins: Continue with Google, Continue with Microsoft, or the e-mail link.
- A second owner e-mail in a different provider (OWNER_EMAILS in Netlify) — if the first mailbox is lost or locked.
- Recovery codes (OWNER_RECOVERY_HASHES): one-time codes you keep in your password manager and, printed, somewhere safe. Use them on this page under "Locked out?". Make new ones with
node scripts/owner-recovery-codes.mjs. - The Netlify account itself: whoever controls it can set OWNER_EMAIL and redeploy. Protect it with two-factor login and keep its recovery codes too.
- The backup key and the archives: with the key (password manager) and any archive (downloaded above, or in Cloudflare), the whole service can be rebuilt — docs/BACKUP-AND-RESTORE.md.
Audit log
What is this?
Every admin action, newest first: who it touched (by a short tag, never the address), what, and why.
| When (UTC) | Action | Account | Detail |
|---|---|---|---|
| Loading… | |||
Links
- Operating numbers — sales, supply, the qualified leg, the security log
- Public status page
- Stripe · Netlify · Cloudflare · CRM