Who it’s for
People who run a project and need to see what its services are doing, without sending the project, its name, its logs, or the record off the machine.
Live
Core Trail Kit
Core Trail Kit is a local macOS desktop app for the software you already run. You connect a project, watch its services, and read the cause the source itself reported. CTK does not invent one. The project, its logs, and the record stay on your machine.
Less guessing. More knowing.
The problem
The failure is rarely a mystery. The report is just somewhere else. An exit code is in one place, a memory limit in another, a health check in a third. A log line gets treated as the explanation before the cause has been read.
How Core Trail Kit approaches it
Point CTK at a project you already run. While the app is open, it follows the services in that project and writes down what each one is doing. When something is wrong, you see the cause the system reported. If the source did not state a cause, that field stays empty.
What you get
What Core Trail Kit delivers
Concrete outcomes — not a feature dump.
- Local by design. The project, its path, its logs, and the record stay on your machine.
- Built for macOS. The account is on the site; the record is in the desktop app.
- Connect a project, watch the services, then read the cause.
- CTK does not invent a cause. A line from a log is not a why.
- One menu for every door: Already running, Docker, Start with Toolkit, and Kubernetes on Team.
Product site: coretrailkit.com
How it works
From the folder to the cause
Each step is a place in the app. The folder stays on your machine. Watching it is a separate step.
- Connect a repository by choosing the project folder. Until a watch starts, it is listed as Not watching.
- Start a watch and choose how the project runs. In this version the doors are Already running, Docker, Start with Toolkit, and Kubernetes on Team.
- Read the cause the source stated. CTK writes neither a why nor a solution on its own.
What stays where
The account is ours. The record is yours.
Signing in does not upload the project. The company holds the account. The machine holds the work.
- With the company: sign-in, the plan, and two numbers — how many projects are connected, and how many services are being watched.
- On your machine: the project, its name, its place on disk, its logs, and the reading of what the services did.
- A green mark means a health check reported healthy. A service that is running, with no health check, stays a plain Running.
The record
The same watch, read on screen
Timeline, topology, and incidents come from the same watch. The menu is the same for every door.
- Overview shows each service and its mark. Discover shows what the watch found.
- Observe is the only place the cause is written out. A missing side is marked as a gap.
- Topology draws a dependency only when the source stated it. Timeline groups the readings of one service into a moment.
- Incidents group the related readings under a service. Recommendations stays empty until a solution is linked.
Also from CTL
Other products
More product lines under Core Trail Labs — each with its own surface and status.
NomadoAI
Trip planner and AI copilotYour whole journey in one companion: day-by-day itineraries, an AI copilot that knows the trip, and the travel story you bring home.
Nomado Puzzles
Daily city puzzlesA fast city quiz for daily play: 3 Clues, City Blitz, City Anagrams, and 2 Truths 1 Lie.
SettleDrop
Shared expenses without holding moneyTracks who owes whom across trips and shared living — never holds or moves funds.