klair·apollo

What builds your software no longer sleeps.

live01234567890123456789012345678901234567890123456789events todaylastPR-OPENED12s ago

Hand Apollo a backlog. It drafts plans (asking you the questions), builds on isolated lab branches, runs your tests, retries on failure, and opens clean changes for review. Through nights, weekends, meetings. Every hour you'd rather spend on something else. A human on your team signs at the end. Always.

Request accessSee indicative pricing
  • Your repo · your IP
  • Human-signed merges
  • No training on your code
  • 72-h human reply to cohort applications
02The canonical dossier

What Apollo is, in four cards.

Read once. Quote at the next meeting. The shape of the product, named in primitives.

01primitive
ARCHITECTURE
A build platform.

Not a chatbot, not an editor. A service that takes a brief and returns a pull request, end-to-end.

02primitive
LIFECYCLE
Plan → lab → build → test → PR.

Scopes the brief into a plan. Builds and tests on an isolated lab branch. Opens the PR.

03primitive
TRUST BOUNDARY
No automerge. Ever.

Apollo cannot merge and cannot grant itself merge rights. The boundary is enforced at the code-host permission layer, not by policy.

04primitive
RUNTIME
Your repo. Your IP.

No training on your code. Lab branches are ephemeral and isolated per engagement.

Apollo lifecycle film · 3 min · placeholder · captioned · no autoplay
01A · 017 · KLAIR-2026
VIDEO · 90 SEC · APOLLO LIFECYCLE FILM · 3 MIN · PLACEHOLDER · CAPTIONED · NO AUTOPLAY · PRESS PLAY
03Agency mode · the while-you-sleep hook

While you're not there.

Apollo runs continuously: at 03:00 on a Tuesday, at 14:00 on a Sunday, while you're in standup. You log off with a backlog. You log back in to an ordered summary in your PM tool and a queue of clean changes awaiting your signature.

tue · 18:0000:0006:00wed · 09:00+
YOU LOG OFF · TUE 18:42
brief drafted with Apollo · signed · 7 tickets in the backlog · labs idle
THE WORKSHOP RUNS · 24/7
3 plans drafted · 5 lab runs · 142 tests passed · 1 retry · 3 changes opened
nights · weekends · meetings
YOU SIGN · WED 09:14
summary in your PM tool · 3 changes awaiting your signature · 1 plan asks a clarifying question
010203
CONSERVATIVESTANDARDCONTINUOUS
agency · mode
MODE 01 · CONSERVATIVE (DEFAULT)

Plan → human signs → build.

  • Every plan paused for human sign-off
  • Every PR paused for human approval
  • Two human checkpoints per change
FOR: regulated work · early engagements · audit trail
INVARIANTS · TRUE IN ALL THREE MODES
  • 01A named human on your team merges every PR.
  • 02Lab branches never read prod data.
  • 03Every event lands in the activity feed.
  • 04You can downgrade mode at any time.
04Lifecycle · in detail

Six steps. One signature gate.

Plan → lab → build → test → PR → merge. The same shape every change takes, named in primitives.

01·plan

Brief in. Plan out.

Apollo turns a brief into a milestone plan: scope, acceptance criteria, test requirements, estimated cost. The plan is reviewable, signable, and version-controlled. Nothing builds before the signature.

01 / 06
05Observability · live surfaces

Three surfaces. One source of truth.

A live activity feed for the timeline, a project board for the milestone, and a dashboard for the rates. All three updated in real time. Pick whichever fits how your team reads the work.

PROJECT STATUSPHASE · BETA
PROJ-142 · adapter backlog
MILESTONES4 / 6
NEXT
modbus adapter v2 · due 2026-04-30
3
open PRs
142 / 142
tests today
2
active labs
DASHBOARDrates · last 7 days
build success
98.2%+0.4
avg PR cycle
3h 12m−18m
retries today
4−2
lab compute
12.4 / 4031%
ACTIVITY FEED · acme-robotics / adapter-backlog · LIVE0 ev/hrLIVE
events · today01234567890123456789012345678901234567890123456789
    streams to your team's tool
    LinearJiraAzure BoardsGitHub ProjectsAsana
    · click to filter
    08Apollo FAQ · technical

    What teams ask about Apollo.

    Permissions, CI behaviour, retry semantics, drift mitigation: the precise questions engineering leads bring to the intro call.

    Apollo reads your repo conventions and works on the languages your team already ships in: TypeScript / JavaScript, Python, Go, Ruby, Java, and the framework families on top of those. The runtime is language-agnostic; the lab branch and your CI do the work.
    private beta · invited cohort

    Apply for the Apollo beta.

    A human reads every application within 72 hours and replies with a yes or a no. No drip funnel, no auto-scoring.

    klair · workshop · open