Multi-agent AI. Local control.

Orchestration and parallel execution The orchestrator plans and dispatches tasks through a Linear queue. Claude Code and Codex accounts work in building, operating and reviewing lanes, with automatic handover to another available account when a quota is exhausted. Parallel execution reduces waiting time between requests.

Review and the Done gate Review by another model, such as Codex, is part of the CI, merge and deployment workflow. The Done gate requires evidence of integration, publication and passing checks and reopens tasks closed without delivery. Each completion represents a verifiable result.

Second brain and recipe library The knowledge graph, compiled wiki and visual map preserve decisions and connect lessons. The library injects relevant recipes into task dispatch to reduce repeated work and maintain continuity across projects.

Multi-project management One panel brings sites and businesses together, with BI per project and integrations for Google Search Console, GA4, Clarity, Meta and CRM. Each integration follows the configuration of the business, providing a consolidated view for decisions.

SEO and field performance SEOmator auditing provides weekly coverage per section, while Clarity and RUM track real browsing experience. The system monitors rankings and visibility across ChatGPT, Claude, Gemini and Perplexity and routes eligible findings to automatic fixes with review and verification.

Monitoring and operational efficiency Watchers and the debugger identify failures and route repairs. Model selection considers the task, and CI, review and deployment waits can resume without another AI call, reducing operational consumption.

The path of a task Each step below is a module of the repository, with its real file name. Whoever writes a change does not review it, and nothing stays Done without a receipt. The plain-text summary is in docs/ARQUITETURA.md.

Where each number comes from Krohnos has no search index of its own. It combines sources the site owner can already use, pays per use where it needs market data, and keeps everything in a per-site store.

Features and cost, not quality Prices and limits were read from the official pages on 2026-10-20, in US dollars, and change without notice: check the link before deciding. Semrush shows the monthly equivalent of the annual plan and the monthly-billing price; the table shows both.

What they do and Krohnos does not Krohnos does not crawl the web and has no backlink index of its own: it queries DataForSEO's. It does not estimate traffic of third-party sites, only measures yours through Search Console and GA4. Its history starts at installation, while Ahrefs states 6 months, 2 years or 5 years of history depending on the plan. It also has no ready-made keyword research interface: research runs through the API and the agent.

What Krohnos does and these tools do not advertise It is not only SEO: it creates the issue, writes the fix, sends it through review by another model, deploys and checks the receipt. The data stays on your server, and the code is AGPL-3.0, open to audit.

In practice Two US$ 20 agent subscriptions, a small server and cents of DataForSEO per site come in under Ahrefs' cheapest plan (US$ 129) and Semrush's SEO plan (US$ 139), but they deliver different things: there you buy data and reports, here you run the delivery. The author's own operation uses Max accounts, with a larger usage limit.

Accounts and monthly cost Sources and date are in the cost table above (2026-10-20). Krohnos itself is free (AGPL-3.0); what you pay for are the services it uses.

Six businesses in operation Krohnos has operated six businesses for at least one week, with execution history since October 8, 2026 and a project registry verified on October 17, 2026.

1,038 successful executions On October 16, 2026, the usage log recorded 1,038 agent and routine executions completed successfully without interruption. Measurement source and methodology.

Two measured days On 2026-10-15 the usage log has 1,342 runs, 1,316 completed successfully and without interruption; on 2026-10-16, 1,043 and 1,038. They count agents and routines, including resumptions, and are not the same as Done issues. The logs are private. Methodology.

Requirements Linux with Docker 24+ and Docker Compose v2, 2 GB of free RAM and about 4 GB of disk. Secrets live in Docker volumes, never in the image.

# 1. Get the code
git clone https://github.com/BRK13/krohnos.git krohnos && cd krohnos
# 2. Build the image (one image serves the 4 services)
docker compose build painel
# 3. Configure: creates krohnos.toml, the master key, the vault and your owner user
docker compose run --rm --no-deps --entrypoint krohnos painel init
# 4. Start the 4 services (panel, scheduler, webhook, MCP)
docker compose up -d
# 5. Check: it should answer ok
curl -fsS http://127.0.0.1:8787/saude

Then open the panel, sign in with the owner e-mail and password, and follow the setup assistant in the panel. Full guide: docs/INSTALAR.md.

Server A Linux machine (VPS or PC) with Docker 24+ and the Docker Compose v2 plugin, 2 GB of free RAM and about 4 GB of disk. A domain pointed at the server is optional, only needed to open the panel over the internet with TLS.

Check Both commands must answer with a version. Secrets never enter the image: they live in Docker volumes.

docker --version
docker compose version

krohnos.toml krohnos init creates it in the config volume (/etc/krohnos/krohnos.toml inside the containers). Any key can be overridden by KROHNOS_<SECTION>_<KEY>. Ports, for example, change like this:

KROHNOS_PAINEL_PORTA=9000 docker compose up -d

[painel]
dominio = "krohnos.example.test"
porta = 8787

[agentes]
contas = ["1", "2"]

Secrets Passwords, tokens and API keys never go in krohnos.toml: a key with those names is refused. They live in the vault (cofre volume). The owner password is generated once by init, or read from an environment variable, never from the command line:

docker compose run --rm --no-deps --entrypoint krohnos painel init --dono-senha-env NAME_OF_VARIABLE

One login per account Each agent account (Claude Code, Codex) has its own login, kept in the home volume so it survives recreating containers. List the accounts under [agentes] in krohnos.toml, then sign in to each one once. Replace N with the account number.

docker compose exec painel sh -c 'CLAUDE_CONFIG_DIR="$HOME/.claude-N" claude login'

The panel also does this on the Agents screen. An account without a login stays idle until you sign in.

Pull, rebuild, restart Data, vault and logins live in volumes, so an update keeps them. Check the release notes first.

git pull
docker compose build painel
docker compose up -d
curl -fsS http://127.0.0.1:8787/saude

Stop This stops the four services and keeps your data, vault and logins.

docker compose down

Remove everything This also deletes the volumes: data, vault, master key and panel logins. There is no undo. Back up the master key first.

docker compose down -v