We believe engineering should stay yours.
An open-source engine for your workflows, reviews, releases, and infrastructure — where humans and agents play by the same rules. Self-hosted. Yours.
Three things we believe. Three things we're building.
We're not fighting anything. We're building what we wish already existed.
Engineers shouldn't do by hand what a machine can do. Routine is a quiet tax on the craft.
Workflows.
One engine for releases, reviews, QA gates, and agent pipelines. The scripts you keep rewriting — expressed once, observed fully.
See Workflows →Internal platforms should be open. The tools that make engineering teams strong don't need to live behind closed doors.
Open-source core and plugin system.
Everything is a plugin. Every plugin is code you can read, fork, and extend. No black boxes.
See Plugins →Your stack should stay yours. Switching a broker, a database, or an LLM shouldn't mean touching every service you own.
Gateway and adapters.
25+ contract interfaces between your code and your infrastructure. Swap what's behind the contract. The code stays still.
See Gateway →Same rails. Humans, agents, whatever comes next.
A platform is a set of rules and a runtime that enforces them. KB Labs applies the same rails to everyone who runs inside it — you, your teammates, internal plugin-agents, external agents like Claude or Codex, CI bots, future MCP connections. One permissions model, one observability surface, one extension contract.
One permissions model.
Everyone who runs declares what they're allowed to do. The runtime enforces it the same way for everyone.
One observability surface.
Every run is traced — who started it, what it touched, what came out. Humans and agents show up in the same log.
One extension contract.
Humans write plugins. Agents write plugins. Anyone extends the platform through the same interfaces, with the same governance.
A person plus agents is a team. KB Labs treats them that way from day one. MCP is on the roadmap — as a protocol-level extension of the same model, not a bolt-on.
Start beside your current stack. Not instead of it.
You don't have to migrate anything. Install KB Labs next to what you already use, connect one workflow, and see how it fits. Keep everything else exactly where it is.
Install.
One command, no cloud dependency, no sign-up.
Connect one workflow.
Point it at a repo you already own.
Watch it run.
Full traces, step by step, on your own machine.
Sound familiar?
Six scenarios where teams replaced duct-tape automation with a single controlled platform.
Frequently asked questions
We already have a full stack. Do we need to migrate?
No. KB Labs is designed to sit beside what you already run. Install it, connect one workflow, and keep everything else untouched. You grow the surface area when it makes sense for your team — never because the tool asked you to.
Is it free? Will it stay free?
The OSS core is free and will stay free. It's the engine, and the engine doesn't close. A commercial support layer is on the roadmap for teams that need guarantees — SLA, dedicated support, advanced governance — but it's additive, never a gate in front of the core.
I work alone, or with a tiny team. Is this still for me?
Especially for you. KB Labs is built on the idea that a person plus agents is a team. A plugin-agent can run your reviews. An external agent like Claude or Codex can drive your workflows through the same contracts. You stay in control of what they're allowed to do. Solo builders with agents get the most value from this from day one.
How does KB Labs treat humans, agents, and bots?
The same way. KB Labs is a runtime with one permissions model, one observability surface, and one extension contract — applied equally to any kind of runner. A human running a workflow, an internal plugin-agent, an external agent, a CI bot — they all declare what they're allowed to do and the runtime enforces it. No one gets privileges. No one escapes the rails. MCP is on the roadmap as the next protocol-level extension of this.
How long does on-prem setup actually take?
One command installs the launcher. A working environment with your first workflow is typically ready within an hour. No cloud dependency, no provisioning ceremony.
We already have CI/CD. Why not just extend that?
CI/CD is great at build and deploy. KB Labs is for everything around it — commit policy, AI review gates, QA trend tracking, release coordination, agent workflows. Things that don't belong in a pipeline YAML and don't scale as config.
What does building a plugin look like?
A plugin is a TypeScript package with a manifest. You declare capabilities, write handlers, and the runtime enforces what the plugin is allowed to do. Most teams ship a working plugin in a day.
How do you handle security and permissions?
Every plugin — and every runner — declares what it's allowed to do. The runtime enforces those boundaries: nothing runs outside its declared capabilities. Every run is traced end-to-end. Full details on /security.
The project is early. The code is open. Come watch it get built.
We're showing our work as it happens. Nothing is hidden. Nothing is marketing-first. If you want to see how an open-source engineering platform actually gets made, everything is public.
Run it on one real workflow.
Install KB Labs on your own machine, point it at one process you actually own, and see how the engine fits. No sign-up, no trial gate, no usage limits.