Photographs, not mock-ups
Every image below was captured from a real Talon Control instance — cloned, migrated, booted and photographed. Where a page needed something a fresh install can't have, it was left out rather than faked.
Real screenshots of a running instance. The data is a small illustrative seed.
Your Project Manager, live, with a voice and a face. Today's plan, what needs you, what's awaiting approval — beside a rail carrying money, pipeline, the fleet, the inbox and the append-only record.
Who your customers are, and what they hold
Control started life as a customer registry and licence-key issuer, and that discipline still anchors it: every customer, every Ed25519-signed key you mint, reveal or revoke, and every hosted tenant you operate — in one place, with every commercially meaningful action landing in an append-only event log.
The money, the mail, the message — one surface
Not a dashboard over other tools — the tools themselves, sharing one database, so the deal, the invoice, the payment and the customer email are the same record seen from four sides.
An AI workforce that reports to you
Named agents work the queue through a lease → checkpoint → events lifecycle, a voice-first stand-up starts the day, and built-in automations run on a minute tick. What none of them can do is act outward on their own.
One memory, and every run reads it
The Brain is the library your company writes in — notes, decisions, policies, repo briefs, runbooks — linked into one graph and retrieved into every agent run, so nothing starts from a blank context window.
Bought at lunch, live by dinner
The whole install is a compose file: no cluster, no queue service, no vendor call. If you can run a container, you can run your company on one.
Agents propose. Humans approve.
It's the invariant the whole fleet is built around, and every agent we ship holds it. Drafts, plans and proposals arrive ready to review; sending, deploying and spending stay yours. That's not a setting you could misconfigure — the outbound tools simply aren't there in autonomous runs.
Yours to run, built to be boring to operate
One container, one Postgres
The web server, the background scheduler and dev sessions live in one process against one database. docker compose up, migrations run at boot, done.
Encrypted at rest
Mail credentials, AI provider keys and connection secrets are encrypted before they ever touch the database — and every section sits behind per-user access control.
Offline licensing
Your licence is an Ed25519-signed key verified locally — no licence server, no phone-home. The same machinery lets you mint keys for your own customers.