Core Trail KitCoreTrailKit™
Download

Clarity for your running software

Less guessing.More knowing.

Monitor Docker containers and local services on your Mac. Inspect health checks, alarms and event timelines. Your project logs stay on your machine.

Download CTKExplore the docs
Local by designBuilt for macOS

Overview in the desktop app

Live service state, signals, and incidents in one workspace.

The real desktop app. Eight services, one local view. Click to explore.

The app

The record, on screen.

Spot an alarm. Follow a request across repositories. Open the records behind the explanation.

One alarm view. Across your repositories.

Memory failures, failed health checks, and stopped services — with the causes stated by the source.

One alarm view. Across your repositories.Memory failures, failed health checks, and stopped services — with the causes stated by the source.

Less guesswork. More evidence.

Read the observations behind each incident, alongside the services that are still running.

Less guesswork. More evidence.Read the observations behind each incident, alongside the services that are still running.

Timeline

Rewind timestamped state changes to see the sequence, not just the latest symptom.

TimelineRewind timestamped state changes to see the sequence, not just the latest symptom.

Follow one request across repositories.

Explore storefront, orders, and payments through recorded events linked by a correlation key.

Follow one request across repositories.Explore storefront, orders, and payments through recorded events linked by a correlation key.

From a reported issue to its records.

Select an exchange to inspect matching send and receive records, stated causes, and evidence still needed.

From a reported issue to its records.Select an exchange to inspect matching send and receive records, stated causes, and evidence still needed.

Evidence you can actually inspect.

Check the source record: service, channel, direction, correlation key, timestamp, and reported cause.

Evidence you can actually inspect.Check the source record: service, channel, direction, correlation key, timestamp, and reported cause.

Actual CTK screens from a controlled local demo: three repositories, fourteen services. No customer data.

One workspace. The way you run.

Already runningDockerStart with ToolkitKubernetes
Available runtimes vary by plan

FROM SIGNAL TO UNDERSTANDING

Find the thread. Follow the evidence.

A clear path from your project to what actually happened.

  1. 01

    Connect a project

    Point CTK at a project you already run. The folder stays on your machine.

  2. 02

    Watch the services

    While the app is open, it follows the services in that project and writes down what each one is doing.

  3. 03

    Read the cause

    When something is wrong, you see the cause the system itself reported. CTK does not invent one.

YOUR WORKSPACE, YOUR RECORD

Close to your code. Kept on your machine.

How your data is handled

What stays with you

The project itself. Its name, its place on disk, its logs, and the record of what the services did.

What we keep

Your name, your email, and the plan. Also two numbers: how many projects are connected, and how many services are being watched.

A free plan to begin

Make sense of what’s running.

Connect your first project. Give the next incident some context.

See plans