docs changelog cohorts faq closed beta · 0.4.18

Branch-aware tracing
for messy monorepos.

Splitlane is a small developer tool we're testing with about sixty engineering teams. We're not open to the public yet — there's still a lot we want to fix first, and we'd rather break things on a few friends than on the open internet.

per-PR trace overlays github actions · buildkite · circle no telemetry by default self-hosted runners ok 16 mb binary

What you'd get

  • Per-PR trace overlays in your existing CI, posted as a single comment with a collapsible thread.
  • Direct Slack / Matrix channel with the maintainers, with on-call coverage for cohort members during business hours in CET.
  • Lifetime team-of-5 plan if you stick with us through general availability — billed annually after the beta ends.
  • No feature flags, no upsell screens, no telemetry beyond opt-in error reports with full payload visibility.
  • Hot-fix turnaround typically inside 36 hours for cohort members, with a private security disclosure pipe.
  • Quarterly office hours where the team walks through what's coming and what's been retired.

Right now

62
teams in beta
~3 wks
typical wait
v0.5
next milestone · march
36 h
hot-fix sla (cohort)

Side-by-side diffs

Compare traces across branches without leaving your PR. The kind of thing you wanted profilers to do years ago.

Bring your own CI

Drop-in adapters for GitHub Actions, Buildkite, and CircleCI. Self-hosted runners welcome — there's a 16-line YAML snippet to copy in.

Quiet by default

No dashboards you have to check. Splitlane posts a one-line summary in the PR — and shuts up if nothing's wrong.

Selector-aware

Knows the difference between a PR that changed five files and a PR that changed a transitive dep graph. Won't waste your CI minutes.

Encrypted at rest

Customer-supplied keys, region pinning, and per-repository encryption envelopes. Audit log retained for 90 days.

Fully revertible

If you uninstall, Splitlane removes its PR comments and webhooks within ten minutes. We hate residue too.

# in your existing PR check, after `actions/checkout`
$ splitlane trace \\
  --base=main --head=feature/x \\
  --budget=2400ms \\
  --upload # non-blocking; posts inline PR comment

# first cohort installs in roughly four minutes
# your existing build cache is preserved verbatim
# requires GH_TOKEN or BK_TOKEN; nothing else

Recent cohorts

CohortOpenedTeamsFocusStatus
c-001Sep 20234Toolchain teams · Java monoreposretired
c-002Dec 202311Mixed JS / Rust shopsretired
c-003Mar 202423Platform engineering teamsactive
c-004Jul 202424Infrastructure consolidationonboarding

"We replaced three internal scripts with Splitlane on day two. The PR comments are the only place where any of this stuff is now legible — even the new hires can read them on their second week."

— S. Mendelhall, platform lead at a 40-person infra company · cohort 3

—— frequently asked ——

Is there a price tag I can plan around?

The beta is free. After GA we expect to charge per repository, with a generous free tier for small teams. Cohort members keep their tier and discount forever.

What languages and stacks are supported?

Anything with a CI runner. We have first-class adapters for JS/TS, Go, Rust, Python, Java, and Kotlin. Other stacks work via a generic JSON ingestion.

Do you store our source code?

No. Splitlane operates on metadata, traces, and PR diffs. The repo content stays on your runner. The only artifact uploaded to us is a compact trace bundle.

Apply for an invitation
$ splitlane request-access --tier=team --org=<your-org>
// queued. expect a manual reply within 48h.
splitlane.dev built for build engineers · made in Zürich + Tallinn