One pane of glass for every clock in your network.
Sub-second
Alerting latency
1 agent
Per host
Cloud or self-host
Deploy anywhere
REST + gRPC
Full API access
The Timebeat App is the core of the TimeBeat platform — a lightweight agent for Linux and Windows that streams real-time PTP, NTP and GNSS telemetry from every host, switch and grandmaster into a single unified dashboard. If you’ve ever had to correlate drift across three vendors’ tools during an outage, you already know why it exists. Deploy one agent per host, watch every clock in your infrastructure, and get sub-second alerting when anything starts to drift.
What it does
Continuous telemetry for PTP offset, path delay, GNSS quality, oscillator drift and holdover state — every clock in your network, always on.
The agent maps your PTP domain automatically — grandmaster → boundary clock → transparent clock → slave — and keeps it up to date as equipment comes and goes.
Set thresholds on drift, GNSS loss, holdover events or any other metric. Route alerts to Slack, PagerDuty, email or a webhook — sub-second latency end-to-end.
Every metric is stored for months by default. When someone asks “what did the clock do last Tuesday at 14:32?” — you actually have the answer.
Already running Grafana, Datadog or your own observability stack? TimeBeat ships all its data in the formats they understand. No lock-in.
Managed service providers and large enterprises get organisation-level separation, per-team access control and audit logging out of the box.
How it works
Step 1
A single binary (Linux or Windows) runs on every host — bare metal, VM or container. Auto-detects PTP and NTP clients, GNSS receivers and PHC devices.
Step 2
The agent streams structured telemetry over gRPC to a backend you host (or to TimeBeat Cloud). Low-bandwidth, encrypted in transit.
Step 3
The web dashboard gives you topology, live metrics and historical replay. The API lets you wire everything into the observability stack you already run.
Where it lives
01
When a production system glitches, the first question is always “was the clock okay?” Historical replay lets you answer it in seconds, not hours.
02
Continuous evidence that every host is within MiFID II / CAT / FINRA timestamp tolerance — no manual audits, no spreadsheets.
03
Catch oscillator aging, antenna degradation and slow-burn problems long before they become outages.
04
Visualise every PTP flow in your network and spot single points of failure, unbalanced grandmasters or overloaded boundary clocks.
Hardware pairs
The capabilities of Timebeat Agent pair naturally with these products. Deploy together for the fullest experience.
Standards & compatibility
Also in the platform
Book a demo
Thirty minutes with a TimeBeat engineer. We’ll show you live dashboards, answer your architectural questions, and map the platform to the problem you’re actually trying to solve.
Further reading
Pillar guide
What a grandmaster actually does, how to choose one, and the three things that separate a grandmaster you can trust from one that quietly drifts.
Cluster
Choosing the right oscillator class — the drift numbers that matter and the deployment scenarios where each is correct.
Interactive tool
Model the regulatory and operational cost of a GNSS disruption for your industry and oscillator class.
Library
Guides, blogs and case studies for teams evaluating or deploying this solution.
Why a single-grandmaster deployment is a DORA Article 11 problem, what A/B/C redundancy looks like in a single rack unit, and how the Open Time Appliance Shelf turns three independent Rubidium Black+ grandmasters — with independent GNSS antennas — into the default finance-venue topology for 2026 and beyond.
A speculative question, not a product pitch: imagine if every machine could hand anyone independently verifiable proof of what its clock was doing at any moment in history. Would it matter? Who would benefit, what might it cost us, and would the world actually be better for it? An exploration of the idea of cryptographic UTC attestation.
An engineering-level tour of the 167 telemetry fields the Timebeat Agent emits per cycle to Sync Insight. Nine measurement domains, why each one matters for operations or compliance, and how to pick the handful of fields your Grafana dashboard actually needs day-to-day.
How the Timebeat Agent fuses GNSS, upstream PTP feeds, PPS inputs and oscillator discipline into a single weighted clock output — the same BIPM-style ensemble approach used to produce UTC itself, applied at the site level.
How PTP² Mesh turns a fleet of Timebeat Agents into a self-discovering, self-healing time distribution network. mDNS and DHT peer discovery, seat-based capacity, active-active operation and millisecond failover — for when you need redundancy without the rigidity of classical BMCA hierarchies.
What jitter attenuation actually does inside a PTP timing fabric, why raw timestamps are unreliable, and how TimeBeat's signal-processing engine delivers sub-nanosecond residual noise from noisy real-world inputs. Written by TimeBeat's engineering team.
