Avrelia · V1

The operating layer for governed company work.

Two lanes, one substrate. A fast assistant for everyday questions, a governed work lane for evidence-rich operations — both drawing on the same compiled memory.

A claymation scene of the Avrelia operating layer: an open book with a brain and a sealed checklist, a server tied to a cloud, a small vault, a mailbox, a calendar and a notifications panel.
Event stream · live14:22:41Z
MSA · MeridianAuto-termination · flagged
Invoice · Q2-4411Net-60 · mismatch §3.1
Email · counsel@Action proposed
Board minutes · Mar 12Compiled to wiki
Self-hosted data
LLM-agnostic
BYO Agent
§ 01 — Why this matters

Every company has a memory problem.

Documents, chats, decisions, and approvals each sit behind their own authentication wall, modeled as events in isolation. The knowledge that ties them together — what you agreed, with whom, why, and what changed — isn't written down anywhere a machine can reason about.

A claymation ring of fragmented documents, charts and a checkmark — work scattered across systems.
01
Work happens
in fragments
Contracts in the DMS, decisions in chat, evidence in inboxes. No system remembers the whole picture.
A claymation chat bubble being erased by a red eraser, with a pin marker beside it — assistants forgetting context.
02
Assistants forget
on purpose
General chatbots re-derive context every run. Same questions, same answers, same blind spots.
A claymation wind-up car carrying chess-piece cargo with its key on the floor — autonomous agents running without audit.
03
Agents act
without audit
Autonomous systems propose business mutations with no before/after, no evidence, no rollback.
§ 02 — The core idea

Two lanes. One substrate.

The same compiled company memory powers both a quick-answer assistant and a bounded, auditable work plane.

Lane A
Fast assistant
Low-risk · conversational · no mutations
Answers against compiled knowledge. Cites source documents, paragraphs and dates. Does not write back to the business.
Ask the company anything
Cites evidence, not confidence
Routed semantic slots
Lane B
Governed work
Evidence-rich · approval-aware · auditable
Proposes typed business mutations. Every applied action carries before/after state, evidence, policy inputs, and approver identity.
Proposal → review → apply
Typed action families, deterministic validators
Full provenance spine, replay-safe
§ 03 — Architecture

Six planes, cleanly bounded.

Routing, compiled knowledge and action execution are three different layers — separated so each can be replaced without disturbing the others.

01
Governance & routing
Org topology, policies, semantic slots.
02
Canonical work objects
Sessions, documents, organizations, people, issues.
03
Compiled knowledge
Page indexes, citation packs, entity summaries, wiki.
04
Retrieval & evidence
Cross-object retrieval, excerpts, freshness rules.
05
Action & orchestration
Bounded graphs, proposal/apply, validators.
06
Execution
Hosted runner, executor profiles, connectors.
§ 04 — Lifecycle

Ingest, compile, retrieve, propose, apply.

Every output points back to its evidence — auditable, not aspirational.

01
Ingest
Candidate-first intake. Untrusted files quarantined.
02
Compile
Page indexes, citation packs, entity summaries.
03
Retrieve
One governed plane across documents and decisions.
04
Propose
Agents return typed, validated proposals.
05
Apply
Reviewed actions commit with full audit.
Action proposal · awaiting review
Extend Meridian MSA termination window from 30 days60 days
evidence · 4 cites
policy · msa.v3
proposer · agent
validator · ok
provenance · append-only
14:22:11proposal.createdagent/contract.review
14:22:18evidence.attached4 citations · doc-4421 §3.1
14:22:19validator.okdeterministic · policy.msa.v3
14:22:41approval.pendinglegal-ops@avrelia
§ 05 — Governed action

Agents propose. Humans approve. Everything is remembered.

Every mutation is a typed proposal. Validators run deterministically before review.

§ 06 — Deployment & security

Your data stays exactly where you put it.

Multi-tenant SaaS, EU residency, dedicated cloud, or fully self-hosted — same architecture, same audit plane.

Claymation deployment & security illustration
SOC 2 Type II
Current attestation, renewed annually.
EU data residency
Frankfurt primary · Dublin failover.
Self-hosted
Helm chart · air-gapped install supported.
BYOK encryption
Customer-managed KMS for document bodies.
Audit export
Streaming provenance to your SIEM.
Model sovereignty
On-prem model slots or private cloud.
§ 07 — Where it lands

Governed work, in context.

Horizontal by design. The substrate is the same — what changes is the task catalog and the action families each team will govern.

01
Legal operations
MSAs, amendments, redlines, clause libraries.
MSA, NDA
02
Finance & controllership
Invoice ↔ contract reconciliation.
AP, AR
03
Compliance & risk
Policy linting, evidence packs.
SOX, DORA
04
Corporate development
Due-diligence dossiers, obligations.
M&A
05
Procurement
Counterparty memory, renewal calendars.
Vendor mgmt
06
People operations
Policy retrieval, structured workflows.
ER, L&D
§ 08 — Pricing

Priced for the work, not the seat count.

Team
€2,400/month
Up to 25 seats. Shared tenant. Fast lane only.
Fast assistant
Compiled knowledge (read)
SOC 2 logs
Recommended
Company
€7,500/month
Up to 200 seats. Both lanes. Dedicated compute.
Fast + governed
Full compiled knowledge plane
Action families + approvals
SSO · SCIM · BYOK
Enterprise
Quote
Self-hosted or dedicated cloud. Unlimited seats.
Private cloud or on-prem
Custom action families
Dedicated success engineer
Contractual SLAs
§ 09 — Next

Bring us one messy workflow.

A two-week working session: we compile knowledge against a real slice of your company and hand you back a working evidence plane.

hello@avrelia.ai
Request a working session