About
About IsoKron
Why we're building AI development orchestration on BYOK + BYO-fleet, and what the customer-review checkpoint costs us in throughput on purpose.
IsoKron is AI development orchestration. A team writes down what they want to build in plain English; the platform compiles that intent into a structured execution graph — Components, Decisions, Tickets, Acceptance Tests — that an AI agent fleet can execute against the team's real codebase.
Why this exists
The frontier of useful work for AI agents is no longer "can the model write a function?". It's "can a fleet of agents finish a real product without the team losing their grip on what got built?" The bottleneck is no longer generation — it's coordination, transparency, and review.
Hand-running a fleet of agents against a codebase requires you to invent the scaffolding for all of that yourself: ticket generation, capability matching, cycle detection, atomic commits, audit trails, security envelopes. Most teams don't want to. IsoKron builds that scaffolding once, and lets your agents do the work.
BYOK + BYO-fleet
IsoKron is a Bring-Your-Own-Key and Bring-Your-Own-Fleet platform. You provide your Anthropic or OpenAI API key; the customer-side stages of compilation invoke the vendor with your credentials. Your agent fleet runs on your infrastructure under your credentials, against your code. We host the MCP shim that mediates between the compiler and your fleet, and the operator-side defenses (notably the Layer 4 critic) that we pay for ourselves out of our own credentials.
The two trust paths share no code. Your BYOK vault is workspace-scoped, decrypted only into per-request memory, and zeroed on release. Operator credentials never leak into customer-side calls; customer keys never leak into operator-side calls. This is enforced at the import level by a custom ESLint rule that blocks cross-credential imports; it's the most security-critical rule in the codebase.
Customer review by design
Every compilation runs through a Stage 6 review checkpoint: we surface the Architect's Ledger — the per-stage trace of what the compiler did and why — and ask the customer to accept, edit, or reject before any commit. This isn't a courtesy step. It's the meaningful safety check between adversarial inputs to the compiler and your production environment, and we don't make it skippable.
Status
IsoKron is in research preview. We're wiring the compiler stages and the customer surface in public, against published architecture decisions; the full design lives in the repo's consolidated specs for anyone who wants to read them.