I am Legion.
We are Legion.

Two developers, one executive, a legion of agents. We build the toolchain that runs them, governs them, routes them and gives them memory.

Claude CodeCodexCursorClaude DesktopYour own harness
The Legion stack
Three people.
A legion behind them.
working
RYL the harness
task ship pricing page · Stride · 17m 28s
rflectr the control plane
Claude Code · Observe · anthropic · 312ms · 18k tok
knectar the gateway
claude-sonnet-4 → success · $0.031 · cache hit
the apiary the memory
recall "how do we deploy" → 4 hits · 0.94
WHIPT the employee
comms · replied to 3 support threads
legioncode.cloud the compute
sandbox up · nyc3 · destroyed after run
Six layers. All Legion. All shipped together.
What it looks like
One task.
Every layer touched.
run 7
ryl · rflectr · knectar · apiary 17m 28s · $0.31
3
people
500K+
lines of code a week
1
of us does not write code
12
products, built with each other
01 How it composes

A developer is not one person anymore.

Everyone sells you the agent. Nobody built the rest.

01 Run

RYL, the harness.

Tasks, runs, tool calls, approvals. One lion that changes state as the run does.

02 Govern

rflectr and shrke, the control planes.

Every request your agents make, recorded. Off, Observe or Route, per harness. Never a credential.

03 Route

knectar, the gateway.

One endpoint, every provider. Fallback chains, virtual keys, cost per request.

04 Remember

The Apiary, the memory.

Learn something once. Every agent recalls it everywhere.

05 Employ

WHIPT, the employee.

Browser, comms, code, research, media. The harness works the code; WHIPT works the business.

06 Ship

OSPRY, MACSITNA, and what comes next.

Real products, built by two developers on the five layers above.

02 The family

Twelve products. One language.

Each on its own domain. Each speaks Legion. OSPRY leads.

Identity resolution, by Legion.

One snippet. Which companies, and which people, visited your site, what they did, and an AI sales brief on each, pushed to your CRM. Observe. Score. Profile. Reach. Yield.

Live →
RYL

The agentic development harness. Tasks, runs, tool calls, approvals. One lion that changes state as the run does.

Harness →
rflectr

A record of every request your coding agents make. Per harness: Off, Observe or Route. Your login stays yours.

Windows beta →
shrke

The control plane as a web app plus tray client. Provider, model, latency, tokens and cost on every request.

Web · tray →
knectar

The AI gateway. One endpoint, every provider, fallback chains, virtual keys, cost per request.

knectar.dev →
WHIPT

The company employee AI. Browser, comms, code, research and media, working the business while the harness works the code.

Private →
legioncode.cloud

Where every Legion product runs. Cloudflare at the edge, sandboxes for the agents, one tailnet for the humans.

Infrastructure →
MACSITNA

Anti-scam intelligence network. Anti-scam spelled backwards. Lawful. Transparent. Evidence-driven.

Live →
Owl's Roost

Indigo ground, gold for wins. Live now.

Live →
OnlyFacts

A research library where every claim carries its evidence class. Ask Susan.

Live →
Time Debt

Four minutes of questions, then the invoice: hours lost a week and a Time Debt Score from 300 to 850.

Live →
the apiary

One memory. A whole hive around it. Shared, lasting memory for your coding agents, on hardware you control. With Activeloop.

theapiary.sh →
03 Proof

We build every one of these with every one of these.

Harnesses left. Providers right. Legion in between. This is last week.

RYLharness · StrideClaude Code2.1.259 · RouteCodex CLIObserveCursorOff · untouchedshrke · rflectrOff / Observe / Routeknectargateway · fallbackAnthropicclaude-sonnet-4OpenAIgpt-5 · fallbackLocalyour hardwarethe apiarymemory · 1,284HarnessesGovernRouteProvidersRemember
Route · only committed traffic glowsObserve · metadata onlyOff · not in the path rflectr · Claude Code 2.1.259 · Routing via knectar · Verified 3 d ago

I am Legion.
We are Legion.

#vibewithlegion