About

Heartbeat exists because its builder got tired of waiting a day to find out whether an update helped or hurt.

It started as an internal pipeline for a live Roblox game: server-side tracking, five-minute batches, and a dashboard that stamped every number with how complete the underlying data was. The pipeline caught a deliberately dropped batch on its first stress test, reconciled with the platform's own revenue numbers, and it became obvious other developers would want the same thing.

What we believe

• Latency kills iteration. A developer who sees numbers five minutes after shipping makes different, better decisions than one who sees them tomorrow.
• Analytics must admit what they missed. Game servers crash and packets drop. A dashboard that silently pretends to be complete is a dashboard you cannot bet an update on. Every Heartbeat number carries a completeness score, and rates measured on too few players say so instead of showing noise.
• Players are not the product. Numeric platform ids only, no names, nothing sold, nothing shared across games. The code that runs inside your game is open source so you can check.

Where we are

Heartbeat is in closed beta with indie developers on Roblox and Steam. The dashboard is live, the ingest pipeline is being hardened against real traffic, and the first public accounts open when it holds. If you want in early, say hello.