Get Started
DocsTrack 1editions
/llms.txt
Architecture & Editions4 min readbrevio-core v0.11.1

Open Core CLI (brevio-core) vs. the Brevio Harness

Plain-English Summary (For Anyone)

Choose between free local checks and a self-hosted engineering runtime

brevio-core is open source (Apache-2.0) and runs in your terminal, your agent's edit loop and CI. The Brevio Harness is a separate commercial product that runs autonomous delivery on your own server. See the pricing page for the Harness plans.

Why this matters:
brevio-core is complete on its own: scan, check, hooks, the MCP server and the GitHub Action are all in the package.
The Harness adds scheduled operation, approvals and production checks on top of one-task-at-a-time work.
Nothing brevio-core writes locks you in: its outputs are plain files in your repository.
When to use:When deciding whether your team needs local checks for agent mistakes or an autonomous background engineering runtime.
Technical Contract (For Engineers)
Line-level rules
CLI Invocation Signature:
brevio-core scan --diff (open core) | Brevio Harness (self-hosted, see pricing)
Latency / Execution
Not measured for 0.11.1
Token Cost
brevio-core: no model call. Harness: a model client you sign in to on your server.
Exit Codes
brevio-core: 0 = nothing found; 1 = findings; 2 = usage error
Artifacts & Files Generated:
.brevio/task_plan.json.brevio/PR_BODY.md.brevio/baseline.json
Visual Execution Pipeline
5-Stage Progressive Flow
01Open vs Harness
Choose
Select the open core CLI or the Brevio Harness
02Self-hosted
Setup
Install brevio-core with pip or uvx, or deploy the Harness on your server
03Your choice
Execution
Run checks locally and in CI, or run roadmap items in the background
04PR checks
Deliver
Merge with checked pull requests

brevio-core (Apache-2.0 Open Core CLI)

In Plain English:Free to use, for individuals and commercial teams. The rules make no model call and need no API key.
`brevio-core` is licensed under Apache-2.0. It includes the 129 documented rules (14 scanned, 9 more with `--surface`), `brevio-core check` (the pre-PR flight check), the Personalized PageRank repository map (`brevio-core map`), `brevio-core heal`, learned guards (`learn`), starter guard packs (`add`), hooks for Claude Code and Cursor, an MCP server with 4 tools and the GitHub Action. `scan`, the agent hook and the MCP server use no network and send nothing. `brevio-core ai` calls a model only when you connect one and answer yes.

Brevio Harness (Self-Hosted Autonomous Runtime)

In Plain English:Works from your roadmap on a schedule and asks for approvals in Discord.
The Harness is a separate product that runs on your own Linux server, with a model client signed in there. According to this site's own product description it works from a roadmap on a schedule, selects a model per role, relays commands and approvals through Discord with protected-path approvals, runs browser QA in a headless Playwright container and checks production every 15 minutes (a merge that breaks production is reverted). Some newer safety checks start in a report mode that records what they would do. See the pricing page for plans.

Where the Two Differ

In Plain English:Everything brevio-core does is listed above. This table shows only where the Harness goes further.
| Topic | brevio-core (Apache-2.0) | Brevio Harness | | :--- | :--- | :--- | | **Task execution** | One task at a time, started by you (`brevio-core task`) | Background operation from a roadmap | | **Where it runs** | Your machine and CI | Your own Linux server with a model client signed in (Docker is used for QA and the stores, not for model work) | | **Models** | None for the rules; `brevio-core ai` only if you connect one | A model client you sign in to on your server | | **Browser checks** | Not included | Headless Playwright QA container | | **Approvals** | Not included | Discord command relay with protected-path approvals; a plan you asked to review waits for your answer, and asks are capped at ten a week outside merges and emergencies | | **Production checks** | Not included | 15-minute production checks; a merge that breaks production is reverted | | **Spending limit** | Not applicable | EUR 15 an hour and EUR 50 a day over all projects stops model calls; each task also has time, token and cost caps (for runs on a flat subscription the cost is an estimate from run time) | | **Backups** | Not applicable | Nightly backups with a restore check of the newest set per project; encrypted when you give a key, off-server copy when you configure one | | **Report-first settings** | Not applicable | New safety checks start in a report mode that changes nothing; 274 such settings sit in four switch-on groups (records, security, release and QA gates, growth and learning) | | **Self-update** | Not applicable | Hourly update from git with a backup first and a smoke check; the old code is put back if a step fails; commit signature checks and the doctor gate start in report mode | | **Export and erase** | Not applicable | Export a project as an archive, or erase it and keep an erasure record | | **Licence** | Apache-2.0 | Commercial, see pricing |

Starting Small

In Plain English:Start with brevio-core on your laptop today. Its outputs are plain files that stay yours either way.
brevio-core's own files are `.brevio/baseline.json`, `.brevio/guards.json`, `brevio-core.toml`, `CONSTITUTION.md`, `CLAUDE.md` and `roadmap.json`. They are committed to your repository like any other file. `brevio-core init --undo` removes what init wrote and what you have not changed since.

Interactive Rule Explorer

Explore the brevio-core rules and load their examples into the panel on the right.

129 / 129 rules