01
You don’t know how far behind you are.
What your team is doing feels modern. Compared to what’s actually possible today, it’s stone age. You can’t close a gap you can’t see.
Any business · Any domain · Any technology
From fully manual to fully autonomous.
Two products take you there.
HeadGateA GitHub app that prepares your repository for agentic software development.
FlumePlans with you, then flows fully autonomously — issue in, merged PR out.
One engineer ships more pull requests in a day. A small team ships the output of a much bigger one.
Free until January for the first 100 signups.
AssessA working session on your codebase, fit first
PrepareHeadGate readies your repository
FlowFlume plans with you — then flows fully autonomously
01 — The problem
Three things every engineering team already feels.
02
You’re overwhelmed.
New tools, new models, new best practices every week. Staying current is a full-time job. Your team can’t keep up.
03
You don’t know where to start.
Without clarity on your position or a path forward, people tackle AI adoption separately, inconsistently, or in secret. Everyone’s improvising.
Why this matters. The hardest part — knowing how far behind you are and where to start — is exactly what you can’t see from inside. That’s what assessment is for.
02 — Who we are
ACME.
Any business.
Any domain.
Any technology.
We are not a vertical shop. If software is how your work gets done — even if your “engineering team” is one overloaded developer and a spreadsheet — the path is the same: prepare the repository, plan the work, flow it.
The name is the pointThe team that can’t hire fast enough
The roadmap outruns headcount every quarter. Flows are the engineers you haven’t hired.
The company that runs on spreadsheets
The work is software-shaped but there’s no software team. The tools you rent become software you own.
The team stuck at manual
Real engineers, modern stack, stone-age loop: every diff hand-reviewed, every deploy an event. The dial goes up.
The team already pairing with AI
An assistant in the editor, an agent in the CLI — and a human still reads every diff and babysits every commit. Assisted isn’t autonomous; the dial has more notches.
03 — How it works
Assess. Prepare. Flow.
A fit conversation, a prepared repository, then delivery that runs on its own.
Assess
A session on your codebase
Your issues, your concerns, and whether the beta is a fit — you leave knowing where you stand.
Prepare
Install HeadGate
Our GitHub app prepares your repository for agentic software development, so your first flow starts on solid ground.
Flow
Plan, then flow with Flume
Talk it through — 15–30 minutes of your time — agree on the summary, and the pipeline turns it into a decomposed issue on its own. Then flow: issue in, merged PR out, 2–3 hours with nobody watching.
04 — HeadGate
HeadGate readies the repository.
A GitHub app you install on your repo. It prepares the codebase for agentic software development — so when your first flow runs, it runs on solid ground. Included with early access.
05 — Flume
Semi-autonomous planning, fully autonomous flows.
Autonomy doesn’t come from a bigger model — it comes from a better plan, executed behind guardrails. Flume, the native Mac app, runs both: planning produces a decomposed issue accurate enough to build without a human in the loop, and a flow builds it — proven on real work.
Planning — five stagesYouFully autonomous
DiscussTalk the feature through — 15–30 minutes of your time.
SummaryAgree on what you’re building.
BlueprintThe settled decisions, frozen.
Pipeline1–2 autonomous hours: decompose, draft, review.
IssueA decomposed issue, ready to flow.
Flowing — six gated phases
StartPrepare an isolated, green workspace.
CodeBuild task by task, tests first.
ReviewFour fresh agents inspect the change.
TriageResolve findings and fix confirmed issues.
LearnReview findings become lessons future plans apply — no mistake twice.
CompleteAuto-merge or wait for approval.
Your repo, your rules
Everything ships through your repository.
Flows open normal pull requests in the repos you already own — the work is inspectable exactly the way your team inspects work today.
Normal commits and PRs
Work is inspectable through your existing source-control workflow.
Rules live with the code
Tests, CI gates, and repository instructions remain where your team can audit them.
Control is explicit
Choose approval-gated or automatic merge independently for each project.
FAQ
Before you claim your slot.
Claim a slot with your repository in hand. The first 100 are free until January.
What is HeadGate?
A GitHub app you install on your repository. It prepares the codebase for agentic software development, so flows run on solid ground. It’s included with early access.
How is Flume different from a coding agent?
Agents generate code. Flume governs delivery: semi-autonomous planning that produces a decomposed issue, then six gated phases — isolated worktrees, CI-gated commits, four fresh review agents, triage, learn — ending in a merged pull request.
What do we need to get started?
A GitHub repository and a real backlog. Claim an early-access slot and we’ll take it from there.
What does it cost?
Early access is free until January for the first 100 signups — no card required.
Who decides when work merges?
You choose per project: auto-merge after every gate passes, or require approval at the final step.
What remains in our repository?
The commits, tests, CI, pull requests, repository rules, and operating playbook stay in your repositories.
Do you offer consulting?
Yes, focused on one thing: culture adoption — helping your team change how it works so autonomous software development sticks. Book a call to talk it through.
Early access
Claim one of the first 100 slots.
Free until January, no card required. Assess the fit, install HeadGate, plan your first feature — then watch it flow.