klair·moon

Apollo built it. Apollo stays on call.

STATUSBETA · indicative pricingGA1 SEPT 2026RANGE€1,200 → cluster · per month

Moon is the operate phase of a klair services engagement. When the build closes, you choose: take the runbook and self-host, or stay with us hosted, with Apollo on call. The code is yours either way. The door out is open either way.

  • Cancel any month
  • Code in your repo from day one
  • Runbook handed back at exit
TODAYMoon is open to klair services projects only. Apollo-direct rolls out post-GA.
the long shift

The engineer who built your software stays on call. Forever.

Apollo built the project, so Apollo knows the architecture, the trade-offs, the schemas, the test-coverage gaps. When something breaks at 03:00, the diagnosis is loaded the moment the page hits. The hotfix PR is drafted, tested in the lab, and waiting for your on-call human to approve before the ticket is forty minutes old.

the post-launch loop · perpetual
YOU LIVE
Your project ships. The same workshop that built it now watches it.
the brain that wrote the code is the brain on call
APOLLO WATCHES · 24/7
Recognises drift against patterns it knows. Drafts the change in the lab when something needs fixing.
ops events: handled · code changes: never alone
YOU SIGN THE FIX
A draft PR appears in your queue. Diff small, failing test attached, fix tested. You read, you sign, the fix ships.
MTTR collapses · trust boundary unmoved
//lunar log · sample dispatches · representative

What Apollo on Call recognises (today, honestly).

  • CORRELATED03:145xx spike on /api/checkout traced to PR #1284 (shipped 02:08). Diff in the diagnosis within 90 seconds. Draft revert PR opened with the failing case as a regression test.
  • RECOGNISED06:42Slow-query trend on orders.created_at flagged. Apollo proposed the covering index, knowing the M3 trade-off it set against write-path cost. Draft migration in the queue.
  • DRAFTED08:01OOM event on worker-pod-3. Reproduced in the lab branch with the exact memory profile. Hotfix PR opened with a passing regression test, waiting on one click.
  • FLAGGED09:18p99 latency on /search trending up release-over-release. Error budget burning 2.4× the trailing 7-day average. Draft change opened for human review before the alert fires.

Compute autoscaling, cert rotation, node rotation are commodity. We don't sell those. The differentiator is code-level pattern recognition on the codebase Apollo wrote.

the paperwork · audit-grade
  • SOC 2 · TYPE II
    in audit

    Continuous monitoring. Report shared under NDA before contract.

  • GDPR
    compliant

    EU regions by default. DPA signed at order. Subprocessor list public.

  • ISO/IEC 27001
    in scope

    Information security management aligned. Roadmap to certification published.

  • HIPAA-READY
    on request

    BAA available on the cluster tier. PHI segregation reviewed per project.

// data residency · EU-WEST · EU-CENTRAL · single-tenant available on cluster tier
Moon · how Apollo stays on call · 90 sec · placeholder · captioned · no autoplay
01A · 017 · KLAIR-2026
VIDEO · 90 SEC · MOON · HOW APOLLO STAYS ON CALL · 90 SEC · PLACEHOLDER · CAPTIONED · NO AUTOPLAY · PRESS PLAY
exit door · always openklair · moon · indicative · finalised at GA 1 sept 2026

No lock-in is a feature of Moon, not an exception to it.

Cancel any month. We hand you the runbook, the credentials, and the deploy pipeline. Code lives in your repo from day one and stays there at exit. The bet is that you stay because Apollo on Call is genuinely better than reading the codebase cold, not because the contract trapped you.

the engineer who built it · stays on call

Hand the keys back, or hand them to the moon.

Moon is opt-in. Cancel any month. The runbook is yours either way. Talk to us about the post-launch plan that fits the project we built together.

klair · moon · perpetual orbit
PARIS · 03:14 CET · the moon is up