Documentation

Reference architecture: a company on intentic

Zoom out from a single specialized agent and the same shape repeats at every level — a co-piloted sandbox per role and per team, each connecting to a small set of shared services. Every block below maps to a shipping primitive; it's a topology you assemble, not a template you click.

The pattern

One specialized agent is a sandbox with tools, system access, and curated context (the autonomous-employee recipe). A whole company is that recipe applied org-wide: give every role and every team its own co-piloted sandbox, and connect them all to a small set of shared services — code, chat, docs, secrets. Nothing here is a new feature — it's the primitives you already have, wired together.

intentic app

one browser UI · every sandbox · watch and steer

Human in the loop — how you supervise the fleet

Agent Governance Sandbox

Human-in-the-loop reviewSandbox rulesAI oversight

Role sandboxes — one per function

Operations Sandbox

StrategyProductsFinance summariesLegal constraintsPriorities

Governance Sandbox

HRLegalFinanceContractsPayroll & approvals

Customer & Market Sandbox

Market analysisPromotionContent writingSales

Team sandboxes — one per team, per product, per customer

Product Team A Sandbox

DevelopmentDev testingQASecurity

Product Team B Sandbox

DevelopmentQA

Per-customer Sandbox

A private, dedicated sandbox per customer

each sandbox connects out over its own tunnel · scoped via capabilities & members, never an ambient bus

Shared services

GitHub · codeDiscord · collaborationOutline · docsInfisical · secrets

Tools & outputs the agents drive

Email managementDocuments · OutlineData visualizationsInfra visualization

How it maps to shipping features

Role & team sandboxes. One sandbox per function or team — Operations, Governance, Customer & Market, each product team, each customer. Automations (cron, webhooks, listeners) wake them, and one agent's run can fire the webhook that wakes the next, so work moves through specialized hands.
Human in the loop. Autonomy is co-piloted, so you drive and watch every sandbox from one browser UI. A dedicated Agent Governance sandbox carries the rules the other agents operate under and the restricted secrets they're granted; members scope who can reach which box. Supervision is a sandbox pointed at the rest, not a privileged control plane.
Shared services. A small set of services the whole fleet leans on — GitHub for code, Discord for collaboration, Outline for docs, Infisical for secrets. They're plain services the agents connect to, not a control plane the fleet provisions. Each sandbox reaches them over its own Cloudflare tunnel, credentials staying per-box.
Tools & outputs. Email, documents (Outline), and dashboards are capabilities the agents operate; every credential stays inside the sandbox that uses it.

Honest about the seams

A company-sized fleet means many sandboxes — that's Pro (free is one sandbox).
No ambient cross-sandbox access. A sandbox reaches shared services and each other only through capabilities and members — each over its own tunnel, credentials staying per-box. The "shared services" band is a handful of connected services, not a shared filesystem or an ambient bus.
Oversight and governance are patterns you build, not built-in roles. And an agent "evaluating humans" is framing we deliberately avoid — these sandboxes assist HR, Legal, and Finance; a person stays accountable.
Chaining is composition of real primitives — one automation firing another's webhook — not a drag-and-drop graph builder.

Start with one sandbox and one role. The org chart above isn't a switch you flip — it's what a company looks like once you've specialized enough agents and connected them to shared services, one primitive at a time. See Quickstart to bring the first one up.

Previous ← Autonomous employees