tomorrowtools Sign in

Telemetry / unified operations

See the automation system around the product.

telemetry.tomorrowtools.dev is the operational view for the services, automations, gateways, health signals, and deployment surfaces that keep TomorrowTools running.

Not a Claude or Cursor usage tracker.

The original idea was a narrow usage monitor. The system has grown into something more useful: one authenticated place to understand the automation environment as a whole.

That means service health, automation state, runtime surfaces, hosted product dependencies, and the operational context needed when something is slow, unavailable, or changing.

Telemetry is where the platform explains itself to the person operating it.

What the dashboard brings together

From signal to action without changing context.

01

Service catalogue

Know which hosted surfaces exist, where they run, what they are for, and how they relate to the rest of the environment.

02

Automation operations

See scheduled and on-demand automation surfaces, their recent state, and the operational windows around them.

03

Health and recovery

Keep health checks, failure context, restarts, and uncertain work visible so the next decision is based on evidence.

For the operator

One view of what is running, what changed, and where attention is needed.

For the builder

A feedback loop between implementation and the behaviour of the system in production.

For the platform

A shared operational language across RocketCV, MPI, TT Manager, and future automation products.

For AySentra Labs

A practical foundation for learning how small automation products become dependable platforms.

The live surface

Telemetry is the explanation layer.

Open telemetry