Every system talks. atrium listens.
The promise
Dock on, do not replace.
Your existing systems stay where they are and stay in charge. atrium sits next to them and takes over the handwork that falls between them.
Most organisations do not have too few systems but too many. atrium replaces none of them. It sits alongside: receives what comes in, sorts it, proposes what follows — and only writes back once a human has approved.
Andocken statt abbilden
Bestehende Systeme bleiben führend. atrium legt sich daneben, nicht darüber.
Agenten für Belegarbeit
Rechnung, Spesenbeleg, Vertragsprüfung, Protokoll: jeder Agent liefert strukturierte Daten, nicht nur Prosa.
Freigabe bleibt beim Menschen
Nichts verlässt den Hof ohne Sichtung. Wer freigibt, sieht vorher, worauf sich das Ergebnis stützt.
The life of a receipt
From inbox to filing.
- 01
Arrive
Mail, scan, a photo from the app, a file from the share. How it gets in does not matter; what matters is that nothing sits unnoticed.
- 02
Recognise
An agent reads the document and returns structured data rather than prose: invoice number, amount, tax rate, service period, counterparty. Anything illegible is reported as illegible.
- 03
Match
The document is matched to a customer, a project or a case. Where the match is not unambiguous, it comes back as an open item — nothing is guessed.
- 04
Approve
A human reviews: recognised values next to the original, differences highlighted. Only then does anything happen.
- 05
Write back
A note on the customer record, a task with a deadline, a file in the right place. Every connection into another system is an explicit action, never a background job.
Agents
Five jobs nobody enjoys.
Not an open chat but clearly bounded tasks with a defined output. What each agent expects and what comes out is stated on the agent itself.
Extract invoice
From a PDF or a photo to line items, amounts and tax rates — as a table and as machine-readable data.
Expense receipt
Meals, travel, accommodation: captured, categorised, matched to the trip.
Contract check
Deadlines, notice periods, liability clauses, unusual passages — each with its location in the document.
Meeting minutes
From the recording to decisions, open items and owners. People who said nothing appear nowhere.
Published post
A result becomes a publishable text in the tone stored in the voice profile — without the claims forbidden there.
And what is not there
Agents can be enabled individually. What your organisation does not need is not even visible.
Connections
What docks on today.
Connections have to be switched on deliberately and are off by default. Where a permission is missing or unclear, the answer is closed.
That is the reverse of the usual arrangement, and it is deliberate. For a core function, staying open protects the ability to work; for a connection into another system, staying shut protects the data.
- Microsoft 365 — mailbox, tasks, SharePoint libraries. Access through the permissions your organisation already grants.
- Odoo — customer records, notes, activities. Enabled in the admin area, no background job.
- File shares — network drives and cloud folders as a read-only source.
- Other systems — through a documented interface. What you run, we work out in the intro call.
The access key of a connected system never leaves the server. The interface only shows whether one is stored — not which. Not even to administrators.
atrium for iOS
The courtyard in your pocket.
Photograph a receipt, capture a task, triage the inbox — collected on the move, processed in the office.