intentic
Create your workspace
Agent Orchestration

Reference architecture: a company on intentic

Zoom out 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. 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 explicitly · scoped via capabilities & members, never an ambient bus
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. A reviewed sandbox definition can stamp out their shared repo, connection and environment shape without copying credentials; each new owner completes the trust decisions locally. Automations wake them, and one 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. A dedicated Agent Governance sandbox carries the rules the others operate under and the restricted secrets they are granted. Supervision is a sandbox pointed at the rest, not a privileged control plane.
  • Shared services. A small set of services the fleet leans on: GitHub for code, Discord for collaboration, Outline for docs, Infisical for secrets. They are plain services the agents connect to through explicit capabilities, not a control plane the fleet provisions. Credentials stay per-box.
  • Tools & outputs. Email, documents (Outline), and dashboards are capabilities the agents operate; every credential stays inside the sandbox that uses it.

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.

More in Agent Orchestration

Type to search every page, in the docs and the API reference.