KB Labs turns engineering operations into versioned, observable workflows. Run the
same process from a terminal, CI, Studio, a schedule, or an agent — with the same
permissions, approvals, logs, and artifacts.
Why KB Labs
Most automation tools connect generic steps. Your team still has to define what a
correct release looks like, how commits should be structured, which checks matter,
and where a human must make the final call.
KB Labs puts those decisions into plugins. A release plugin knows how to plan
versions, build, check, generate changelogs, and publish. A commit plugin knows how
your changes should be grouped and named. Workflows connect these capabilities into
the way your team operates:
prepare → inspect artifacts → approve → commit and tag → publish → notify product
Implement the rule once, improve it in one place, and every workflow gets the same
behavior.
We run KB Labs on KB Labs
task-to-pr: issue or ClickUp task → plan
approval → implementation → review and QA loops → CI → final approval → merge.release-prepare: preview → checks and
build → approval → changelog and versions → commit and tag → CI publish.
These are the workflows used to build and release this repository. People make the
decisions; the workflow executes and records the repeatable work.
Quick start
curl -fsSL https://kblabs.ru/install.sh | sh
kb-create --help
kb-create is a deterministic launcher: a release supplies a sealed index,
then a wizard, CI request or agent resolves and applies one compatible plan.
It has no --demo or positional-project install path. See the guide for the
human and non-interactive flows.
→ Installation guide
How the pieces fit
| Responsibility |
|---|
| Plugins | Package complete engineering capabilities: release, commit, review, QA, integrations, and agent tools. |
| Workflows | Compose capabilities with conditions, retries, approval gates, schedules, and artifacts. |
| Adapters | Keep LLMs, storage, cache, databases, and logging behind typed contracts so providers can change without rewriting plugins. |
| Studio | Shows runs, decisions, logs, artifacts, analytics, and configuration in one place. |
Plugins declare their environment, network, shell, and resource access. Agents get
only the commands exposed by a plugin — not raw credentials or unrestricted vendor
APIs.
→ Workflows ·
Plugins ·
Adapters ·
Architecture
See it in action
→ Product demo ·
Documentation
Project status
Operational signals stay separate from the product header:
| Signal | Status |
|---|
| Production and documentation | |
| Node.js | The platform supports one major, declared by root package.json engines.node. |
→ CI/CD reference
Security
Found a vulnerability? Please do not open a public issue. Follow the
Security Policy for scope, reporting instructions, and disclosure.
Contributing
pnpm install
pnpm build
pnpm check
kb-dev start
Start with open issues. Repository
conventions are in AGENTS.md; architecture decisions are in
docs/adr.
License
| Code | License |
|---|
core/, sdk/, tools/ | MIT — free for commercial use |
plugins/, cli/, adapters/, studio/ | KB-Public v1 — free for personal and internal use |
For hosted resale or commercial licensing, get in touch.
