Getting started

• Getting started
• One-line setup (size labels)
• Which jobs can move
• Fallback & rollback
• Build cache (Nx / Turborepo)
• Get started with your box
• Connect Claude (MCP)
• Billing
• Usage analytics & your data
• Data processors for Code review and Insights
• Help

There are two ways to start, and both begin with the same step: sign in with GitHub and install the compiler.dev App.

• One line: after installing the App, change runs-on to compiler-8cpu (or 2, 4, 16). See One-line setup (size labels). No automatic fallback.
• Setup pull request: pick a repository and a mode, including Try safely, and merge the setup pull request. This is the routed setup, with automatic fallback. Steps below.

1. Sign in and install the GitHub App. Sign in with GitHub, then install the compiler.dev App on your organization and choose the repositories it can see. The App reads workflows and job metadata, registers one-time runners for jobs routed to compiler.dev, and — only through the setup PR — proposes workflow changes. It never merges anything.

2. Pick a repository and a mode. We analyze its workflows and show which jobs can move. Choose Try safely (comparison: a copy runs on our machines, your results still come from your runners) or Switch now with 10%, 25%, 50% or 100% of pull requests. A PR stays on the same side for all of its pushes and re-runs.

3. Merge the setup PR. Each routed workflow gets a small compiler-route job that asks compiler.dev where the job should run; your jobs use its answer as runs-on. Your steps are unchanged. Nothing moves until the PR is merged.

4. Watch the first run. The app shows each job live — queued, booting, running, done — with the machine name and the duration against your previous runners.