keanu AI Engineering Autopilot · Runs on your machine

Client hits send. Keanu ships the verified PR.

The moment a client email lands, Keanu routes the issue, launches isolated agent work, verifies the fix, opens the PR, and drafts the reply — waiting for your sign-off before you’ve even read the thread.

"Hey Keanu, fix the broken mobile share flow."

Issue triaged, branch isolated, browser checked, PR ready before the next client follow-up.

All local. Your client’s code never leaves your hardware — no hosted sandbox, no cloud upload, NDA-safe by default.

Autopilot when you want it, approval gates when you don’t — you set how far each issue runs before it needs you. Nothing launches, commits, merges, or replies without your sign-off.

The problem
"

You're a solo developer or small agency. Email is your inbox and your bug tracker and your feature request system. Every "quick fix" is an interruption. By the time you actually code, half your day is gone to triage.

The engineering loop

From messy client request to merge-ready PR.

Keanu is not another chat window. It is the operational layer around issue intake, agent execution, verification, and client handoff.

01

Capture

Client email, screenshots, and GitHub comments become one issue record with project context.

02

Isolate

Each fix runs in a dedicated branch and worktree so main stays untouched until approval.

03

Execute

Claude, Codex, or another configured backend investigates, edits, tests, and records changed files.

04

Verify

Eyes-style browser checks, screenshots, and test output make the review evidence visible.

05

Handoff

Keanu prepares the PR, fix summary, and client reply. You approve, merge, or send it back.

Why teams trust it

Built for the work around the code.

Generic agents can write code. Keanu tracks the operational proof: where the work ran, what changed, and what was verified — whether the fix is headed to a client or back into your own roadmap.

Branch discipline

Wayfinder sessions run in issue-specific worktrees and refuse unsafe base-checkout execution.

Visual evidence

Require browser verification for UI work and keep the evidence attached to the issue.

Independent evaluator

Every fix is scored against the issue’s acceptance criteria by a separate evaluator pass — and must return PASS before it reaches your review.

Resumable flow

Reopen, relaunch, resume, discard, or retry PR publishing without losing issue context.

Client-ready replies

Draft the follow-up from the actual PR, changed files, and verification notes.

Built with Keanu

We run Keanu on our own products. Our roadmap — bugs and new features alike — moves through the same verified loop, from submitted issue to merged PR.

What is in the box

Engineering operations, not just code generation.

The product boundary is the full client issue lifecycle: intake, execution, verification, PR, and response.

Inbox triage

Messy client emails and GitHub comments get classified, deduped, and routed into structured issues — so you start from a clean queue, not a full inbox.

NDA-safe by default

Code never leaves your hardware. No hosted sandbox VM, no cloud upload, no SaaS code review. Runs against your repos, dev servers, keys, and GitHub from your own machine.

Approval gates & throttle

Analyze, launch, resume, approve, commit, merge, discard, and reply are explicit operator actions. Dial each issue from hands-off to fully supervised. No autonomous merges, no surprises.

Changed-file review

See what the agent touched before approving the commit or publishing the PR.

Model routing

Use Claude for high-stakes Wayfinder work, Codex/OpenAI for compatible flows, and fail over when limits hit.

Dev-server registry

Track issue-specific public/admin servers and recover crashed sessions from the dashboard.

Reply drafting

Turn the technical fix into a client-facing response grounded in the actual issue history.

GitHub-native

Opens real pull requests, links them to the issue, and works inside your existing GitHub flow — no parallel tracker to maintain.

Your backlog too

Not just client tickets. Point Keanu at your own bugs and feature ideas — submit an issue or email yourself — and it runs the same verified loop on your own product.

See it work

Real World Illustrated bug from email → autonomous resolution → PR.

Demo coming soon — 3 min walkthrough

Pricing paths

Try it yourself, or pilot it with us.

Technical operators can start with paid self-service. Teams that need Keanu mapped to real client workflows can run a configured engineering pilot.

Founding offer

Founding Developer

$99

/month, first 50 customers

  • 1 active project
  • Local install docs and starter setup
  • Core dashboard and starter Wayfinder flow
  • GitHub and model provider configuration guide
  • Basic self-service updates while subscribed
  • Best-effort setup notes for technical operators

Locked while your subscription remains active. Best for developers comfortable configuring local tools without concierge support.

Start monthly - $99/mo Start annual - $999/yr

Annual saves $189 versus monthly.

Best self-service fit

Pro self-service

Developer Pro

$299

/month for serious client work

  • 3-5 active projects
  • Premium Wayfinder recipes
  • Visual verification recipes
  • Model-routing presets
  • Email/GitHub automation templates
  • Priority async support

Configured rollout

Engineering Pilot

From $5k

Configured setup plus 30-day workflow tuning

  • Local Keanu dashboard setup
  • Email, GitHub, repo, and project mapping
  • Wayfinder flow configuration for client issue work
  • Claude/Codex model routing and failover setup
  • Visual verification and PR evidence workflow
  • 30 days of tuning around real client issues
Request pilot review
Agency plans start at $799/month for teams managing multiple client projects. Keanu works alongside Helm, Cursor, Copilot, Claude Code, Codex, and your existing GitHub workflow.
FAQ

Common questions

Who is this for first? +

Small agencies, studios, freelancers, and founder-led teams that maintain several client codebases and still receive important work through email or GitHub comments.

Is this autonomous? +

Keanu automates the loop around the work, but consequential steps stay approval-gated: launching work, committing, publishing PRs, merging, and sending client replies.

Where does the code run? +

Locally, against your own repos, API keys, dev servers, and GitHub account. The pilot configures Keanu around your real operating environment.

What is Founding Developer? +

It is a paid self-service subscription for experienced developers who want local install docs, the starter Wayfinder flow, and setup guidance without a concierge rollout. The founding price is locked while the subscription remains active.

What do I get with self-service? +

You get access to the licensed Keanu runtime, the starter Wayfinder workflow, setup documentation, GitHub/model provider configuration guidance, and product updates included with your active subscription.

Why is this priced above AI coding assistants? +

Keanu is not another editor assistant. It works alongside Helm, Cursor, Copilot, Claude Code, Codex, and GitHub to manage the client-issue-to-verified-PR workflow around those tools.

Which models does it use? +

The current high-stakes Wayfinder flow is strongest with Claude and OpenAI/Codex routing. The architecture can support other backends where they fit the risk level.

Should I choose self-service or the pilot? +

Choose self-service if you are comfortable setting up local developer tools, GitHub access, model providers, and repo-specific workflows. Choose the pilot if you want Keanu configured with you around real client projects, approval rules, verification requirements, and handoff expectations.

What happens after I subscribe? +

You receive the next steps for local setup, including access instructions, setup documentation, and the starting Wayfinder workflow for your first active project.