One structured state for the whole company.
Orbit ingests what your company already produces, resolves it into canonical entities, and keeps an append only record of every decision taken from it. The result is a knowledge graph an agent can traverse, rather than a document store it has to search.
Omniscient context
Most tools that connect a model to your company work by retrieval. You ask a question, the system finds passages that look relevant, and the model answers from those passages. It works well when the answer lives in one document. It fails when the answer is the relationship between four documents nobody has read together.
Orbit inverts that. Before anything is asked, the content is parsed into entities and the relationships between them: this supplier, that contract, this decision, that invoice, the person who approved it.
The model does not search your company. It reads it.
A static representation of resolved entities and edges.
Ingestion
| Source | Mechanism | Status |
|---|---|---|
| PDF documents, invoices, contracts | /capture parser | Working |
| Email, via mailbox export or IMAP | /capture connector | Working |
| Slack and WhatsApp exports | /capture parser | Working |
| Website copy and component trees | Sites patch stream | Working |
| Live chat platform connectors | Connector | In build |
| Accounting and CRM systems | Connector | Planned |
Scattered sources
"ACME Corp" "Acme Corporation Ltd." "acme-supplier" "ACME" "Acme Corp" "ACME LTD"
Resolved node
entity:supplier/acme
Canonical entity resolution collapses variants to a single node in the graph.
Append-only decisions
Entries are appended, never edited. If an agent produced a brief on a Tuesday from forty one entities, you can reconstruct exactly which forty one, in what state, six months later.
2026-03-04T09:14:22Z capture invoice/ACME-0912.pdf -> entity:supplier/acme 2026-03-04T09:14:23Z resolve "ACME Ltd", "Acme Limited" -> entity:supplier/acme 2026-03-04T09:20:01Z session agent:chief-of-staff reads 41 entities 2026-03-04T09:20:44Z decision renewal/acme-2026 status: flagged 2026-03-04T09:20:44Z output brief/acme-renewal.md author: agent 2026-03-04T11:02:10Z review brief/acme-renewal.md approved: j.doe
Agents work from state
Agents operate over the structured state under strict system prompts held in AGENTS.md, which is a file in the repository, readable and editable by you.
Because the graph holds the whole picture, agents can produce synthesis and strategy unprompted when new information arrives.
Illustrative unprompted output
Trigger: contract/acme-renewal uploaded Agent: procurement-analyst Action: read 14 invoices, 2 previous contracts Output: draft/acme-renewal-brief.md (requires human review)
Where it runs
Private cloud
For organisations running Orbit as internal infrastructure on private cloud.
Managed
We run Orbit for you on infrastructure we operate. Managed by Cadelic.
Sites feeds the core
Sites is not a second product line. It is a node that produces structured context and pipes it back into Orbit. Every site you build writes structured context back into Orbit: the copy, the components, the commit history, the person, the decision.
{
"entity": "site/marketing-2026",
"patch": "commit/a1b2c3d4",
"actor": "agent:copywriter",
"decision": "updated hero copy for sovereignty focus"
}Status
Last updated 4 March 2026