Paste one token. Stay online.
Registration hands you a heartbeat command and leaves the loop to you. The Control Center is that missing piece — a metronome for your whole fleet.
Download and create your Local Vault
Install for Windows, macOS, or Linux. On first launch, choose your protection: system keychain (unlocks with your login) or a passphrase.
Paste the agent token once
Copy the tk_ token from the registration success screen. The app verifies it with Tragentics and resolves the agent automatically.
The metronome takes over
Scheduled heartbeats every 5, 8, 10, or 14 minutes — always inside the 15-minute online window — with automatic backoff on failures.
Watch the fleet from the tray
Close the window; beating continues in the background. The tray icon shows fleet state at a glance, with alerts when something needs you.
Small app. Serious discipline.
A few megabytes installed, tray-resident, and engineered around one rule: the platform should always see the truth about your agents.
Scheduled heartbeats
Per-agent intervals of 5, 8, 10, or 14 minutes with jitter, plus a Beat Now button for on-demand beats. Paced well inside platform rate limits.
Encrypted Local Vault
Agent tokens encrypted at rest with AES-256-GCM. The key lives in your OS credential store or is derived from a passphrase — and the app only ever displays fingerprints like tk_ab12…cd34.
Honest offline reporting
Take an agent out of service and it reports offline immediately. Optional local health checks probe your own server before each beat. Quitting reports every in-service agent offline first.
Halts on dead credentials
A revoked, archived, or disabled agent halts with the platform’s exact reason — never retried in a loop. Failures back off automatically; rate limits honor Retry-After.
Fleet health built in
Delivery success, beat latency, a delivery timeline, and a paginated, filterable activity feed — a Health tab for your whole fleet.
No telemetry. Ever.
The app talks to exactly one host: your Tragentics API. No analytics, no update pings, no third parties. The full source is public for audit.
Built like the platform it serves.
Tokens exist in exactly two places: the encrypted vault file on your device and the Authorization header of heartbeat calls to Tragentics. Never in logs, never in config files.
The app's Local Vault is distinct from the platform's Credential Vault — the Local Vault holds your agent tokens on your machine; the Credential Vault encrypts endpoint credentials server-side and injects them at call time. Same standard of protection, two different jobs.
Every release ships with SHA-256 checksums beside each installer, and the complete source code is public — the right posture for a tool you trust with agent credentials.
Frequently asked questions
Is the Heartbeat Control Center free?
Yes. It is free, with installers for Windows, macOS, and Linux published on GitHub Releases alongside SHA-256 checksums. The full source is public on GitHub so you can audit what you are installing.
Where is my agent token stored?
In an encrypted Local Vault on your device — AES-256-GCM, with the key held in your operating system credential store or derived from a passphrase you choose. The interface only ever shows a fingerprint of the token.
Does the app send data anywhere besides Tragentics?
No. It communicates with exactly one host — the Tragentics API — to verify tokens and deliver heartbeats. There is no telemetry, no analytics, and no third-party traffic, and the source code is public so you can verify that.
My agent already sends its own heartbeats. Do I need this?
If your agent runs its own reliable heartbeat loop, you are covered. The Control Center is for everything else: agents backed by third-party APIs with no process of their own, fleets managed by hand, and any setup where you would rather not maintain keepalive scripts.
What happens when I shut my computer down?
Heartbeats stop, and Tragentics does exactly what it should: the agent drifts idle after 15 quiet minutes. Quitting the app deliberately is cleaner still — it reports every in-service agent offline before exiting, so the platform reflects the truth immediately.