PRODUCT — WHAT'S IN THE BOX, THE LONG VERSION

Four layers. One governed write path.

Everything you get when you buy Artifi, layer by layer — and the one mechanical rule that holds it together: nothing writes to the ledger except through the governed gateway, whether the actor is a person or an agent.

LAYER 02 — FOUNDATION
A real accounting engine, born AI-legible.

Not a cache, not a copy of your ERP screens — a governed double-entry ledger the AI natively understands. The AI never has to learn your accidental schema, which is why workflows ship in weeks.

Governed double-entry ledger
Immutable rows; agents write through it, never around it.
46 transaction types
Proposals are typed documents, not free-form JSON.
Multi-entity · multi-currency
Intercompany balanced by the core before posting.
Master data & reporting
Vendors, customers, tax codes, dimensions — one truth.
THE MECHANIC THAT MAKES IT TRUSTABLE

Anatomy of a write.

Every change to the ledger — from any agent, any workflow, any person — travels the same five stations. There is no side door.

S1
Propose
An agent or person drafts a typed transaction — one of the 46, never free-form.
S2
Dry-run
Checked against real ledger state: balances, periods, tax, policy. Nothing has posted.
S3
Lane
Risk routes it: auto-post, controller, or CFO. Thresholds are finance-owned config.
S4
Post
On approval, the core writes it — balanced, typed, entity-scoped.
S5
Audit row
Immutable record of who proposed, who approved, what the dry-run said.
PROPOSE → DRY-RUN → LANE → POST → AUDIT ROW · THE RUNTIME IS EVENT-DRIVEN: EVERY STATION EMITS AN EVENT YOU CAN SUBSCRIBE TO
HOW AGENTS RUN

Three execution modes, one gateway.

The mode is chosen per task, not per vendor pitch: deterministic where determinism is cheap, judgment where judgment is needed.

CODE
Deterministic
Scheduled billing runs, payment batching, recurring postings. Same input, same output, every time — auditors like this word.
LLM
Judgment
Reading a messy invoice, resolving a counterparty, drafting master data. The model proposes; the proposal still walks the five stations.
HYBRID
Judgment inside rails
Most volume work: code drives the pipeline, the model handles the ambiguous middle — extraction, matching, classification.
6
OS modules, finance-owned
46
governed transaction types in the core
17+10
core agents + country agents (EE, UK) — catalog →
1
write path — no side doors, ever
WHERE IT RUNS

Deployment that matches your risk posture.

Same platform, same governance, same audit trail — the only thing that changes is whose infrastructure it lives on.

MANAGED CLOUD
We run it
EU-hosted, tenant-isolated, encrypted at rest and in transit. The default for teams that want the fastest path to value — connected and preparing real work in days.
DESIGN PARTNERS
Your infrastructure, deployed by us
For early partners: a source-available agreement with escrow. We deploy the platform on your infrastructure and ship every update — you keep the control without running the project.
SOURCE ACCESS
Code you can read
Commercial source-available terms with escrow, for strategic resilience: the code your finance function runs on is code your team can read and audit.
EVERY OPTION SHIPS THE SAME FIVE-STATION WRITE PATH · SECURITY DETAILS → /SECURITY

See the box opened.

A working session: your stack, one workflow — every layer of this page live against your documents on day one.

Book a working session