Get CTK

Install the signed entry point for Core Trail Kit.

CTK Launcher is the authoritative desktop entry path for CTK Reason, CTK Replay, and CTK Lens. This page now exposes the signed macOS and Windows release lanes on the Core Trail Kit site, while Linux remains intentionally deferred until support quality matches.

Platforms

macOS + Windows

Packaging

Signed desktop lanes

Linux

Intentionally deferred

Release Board

The page is product-facing, but the operating model stays strict: signed lanes first, workspace authority second, product surfaces after launch.

Signed Channels Live

macOS

Signed DMG

Apple Silicon and Intel lane

Windows

Installer EXE

Governed installer lane

Linux

Deferred

Held until support quality matches

Trust posture

CTK should not feel like a random installer. The acquisition surface has to make signed packaging, workspace scope, and product entry boundaries explicit before any download lane goes live.

Release Channels

Choose the lane that matches your platform.

We are carrying over the CTL Web download CTA model, but adapting it to the Core Trail Kit product line. The page should make one thing clear immediately: CTK installs the workspace entry surface that opens Reason, Replay, and Lens under one authority model.

Distribution

Signed release lanes

Trust posture

Operator-visible packaging

Install flow

One entry point for all CTK surfaces

macOSReady

Apple release lane

Download for macOS

Signed DMG lane for Apple Silicon and Intel systems. CTK Launcher establishes workspace authority before Reason, Replay, or Lens open.

  • Apple Silicon and Intel packaging
  • Signed distribution path
  • Workspace-scoped startup model
WindowsReady

Windows release lane

Download for Windows

Installer-based Windows lane with the same authority model: launch scope first, product surfaces second.

  • Installer-first desktop packaging
  • Signed release discipline
  • Reason, Replay, and Lens from one entry shell

Linux

Intentionally deferred

Planned

We are not shipping a placeholder Linux lane. It only opens when packaging, update behavior, support posture, and documentation quality match the macOS and Windows bar.

Install Principles

Why the page is shaped this way.

CTK Launcher stays authoritative for access, workspace scope, and product entry.
Downloads should open a governed operating surface, not a disconnected binary.
Linux remains deferred until packaging, updates, and support quality reach the same bar.

Recommended Path

Read the model, then take the lane.

Step 1

Review the startup model

See why CTK Launcher sits in front of Reason, Replay, and Lens before artifact lanes open.

Step 2

Understand installation posture

Installation docs explain the launcher-first operating model and how product surfaces inherit scope.

Step 3

Choose the product you will enter

Reason, Replay, and Lens stay distinct after launch. Pick the surface that matches the operational job.

Acquisition FAQ

The install route should answer platform and product-boundary questions immediately.

What do I install from the Get CTK page?

This page distributes CTK Launcher, the authoritative desktop entry point that opens CTK Reason, CTK Replay, and CTK Lens under one workspace model.

Which platforms are supported today?

The live release lanes are macOS and Windows. Linux is intentionally deferred until packaging and support quality match the same bar.

Do Reason, Replay, and Lens install as separate entry products here?

No. The installation flow starts from CTK Launcher, which owns workspace scope, access, and launch context before any product surface opens.

Why is Linux not available yet?

Linux remains deferred because the team is not opening a placeholder lane before packaging, update behavior, and documentation quality are ready.

Next Action

Keep acquisition simple, but keep trust explicit.

The primary job of this page is getting teams to the right CTK lane without blurring what is being installed. Startup authority belongs to CTK Launcher; product surfaces stay distinct after launch.