The Zerg AI platform
Zerg is not one chat box. It is an autonomous engineering runtime with a hosted workspace, a control room, a terminal, and a project layer — built to run as a single system across human and agent workflows.
Architecture
Each surface owns a piece of the loop. The runtime executes. The control room observes. The terminal commands. The cloud hosts. The project layer keeps score. Together, they make autonomous work reviewable, interruptible, and operable.
Layer 01
Runtime
The agent engine. Maps the environment, generates code, validates against live signals, and keeps watching for drift. Specs, tests, manifests, modules, and runtime feedback are first-class inputs to a single continuous loop.
Connects to
Layer 02
Control room
The web-based environment for observing live agents. Agent state, file workspace, logs, terminal, and deployment controls in one view. Turns autonomous work into reviewable artifacts instead of opaque transcripts.
Connects to
Layer 03
Terminal
The agent terminal for serious engineering teams. Runs Zerg from the command line with chat, plans, file diffs, autocomplete, sessions, and voice. Browser mirror enables shared debugging across the team.
Connects to
Layer 04
Hosted workspace
The self-serve hosted path. A live workspace with web preview, chat, files, ZTC mirror, and terminal in a single browser session. Launch from a template, share a public app, or keep work workspace-gated.
Connects to
The loop in motion
Watch how a Zergboard ticket flows through the platform. Every artifact is reviewable. Every transition is auditable. Nothing disappears into an opaque agent transcript.
Zergboard
A new card lands on the board — manually, via webhook from a CVE scanner, or autonomously from a Zerg drift detector watching production.
Zerg + ZTC
A Zerg session is launched against the ticket — from ZTC for engineers who want to drive, or autonomously when the ticket has clear acceptance criteria.
ZDE
ZDE shows live agent state, file edits, command output, and intermediate artifacts. Reviewers approve at checkpoints; the agent pauses and resumes.
Zergboard
Merged PR, test evidence, and runtime traces attach to the ticket as the agent moves it to Done. Drift monitoring stays on after closure.
Composition principles
A platform exists when its surfaces share state, identity, and intent. Zerg's products are designed around a single agent runtime — not bolted together after the fact.
Shared state
Sessions are runtime objects, not per-app instances. A Zerg session you start in ZTC is the same one ZDE observes and Zergboard tracks — no copy-paste between tools, no state divergence.
Shared identity
Authentication, permissions, and audit logs are platform-wide. Who triggered what action across which surface is one query, not a stitch job across four log streams.
Shared intent
A spec written in Zergboard becomes the manifest the runtime executes against, the artifact ZDE displays, and the closure evidence the ticket carries when it lands. Intent is preserved end-to-end.
Start with the platform