Documents and records
Every change creates a new version, and each file is encrypted with its own key.
[ System of record ] for regulated industriesThe agentic
The agentic
system of record.
AI agents do the work and named people stay accountable. Every record, signature, and decision can be verified offline.
00 What it is
Tabellion manages official records, including documents, approvals, signatures, retention requirements, and a tamper-evident history of every change.
Software vendors integrate Tabellion into their products instead of building their own record-keeping infrastructure. It works behind the scenes, giving people and AI agents secure access, consistent permissions, and a verifiable audit trail.
01
02
Signatures and workflows
Review and approval workflows with electronic signatures, each bound to its meaning and to the exact version signed.
03
Retention and holds
Retention schedules, legal holds, and approved disposition for every record type.
04
Audit trail
A hash-chained history of every change, and of access at the level you configure, with signed checkpoints that can be verified offline.
Tabellion is named for the public scribes of Roman and medieval Europe who drafted and kept legal deeds.
01 Agentic by design
Agents act. People answer for it.
AI agents can use every staff capability over MCP, under the authority of the person they act for. You decide how far each agent can go, from drafting to signing, and the audit trail always shows who did what. Under the regulated preset, only named people approve and sign, as the draft EU GMP Annex 22 expects for generative AI.
01
Never above the person
An agent acts for one person and gets only what that person may do and your agent policy allows.
02
People confirm what matters
High-risk actions wait for the person to confirm them out of band, with a fresh sign-in. The agent cannot approve its own request.
03
Prompt injection defense in the server
When an agent reads untrusted content, the server lowers its trust level and restricts what it can write. The model does not have to behave for this to work.
04
Every call recorded
Each tool call is recorded in the audit trail with the person and the agent session behind it.
- agentcallcreate_record type=deviation "Temperature excursion, cold room 2"
- policyallowwithin the person's own permissions · trust: high
- ledgersealentry 48,213 · shard 17 · sha256 9f3a…c21e
- agentcalltransition deviation/DV-0193 event=approve
- policydenyregulated preset: approval requires a person's signature
- agentcallrequest_confirmation command sha256 4be1…07aa
- personsignQA lead confirmed · fresh sign-in 42 s ago · meaning "approved"
- ledgersealentry 48,214 · signature bound to version digest
- ledgerproofcheckpoint signed · RFC 3161 timestamp · verifiable offline
02 Extreme control
You set the rules. All of them.
Tabellion is configured at four levels, from the deployment down to individual agent permissions. Changes below the deployment ship as configuration releases that are reviewed as a diff, approved by distinct people, and recorded on every audit entry.
L1
DeploymentSet at installation and recorded at every startup
Access logging modeSignature re-authentication windowStorage lock modeMinimum retentionEarly destructionBreak-glassAgent presetIdentity providersBranding
L2
Object typePer document, record, or case type
Lifecycle and guardsFields and capture rulesRetention policiesPeriodic reviewAccepted media typesEncrypted contentCase access attributes
L3
ReleaseApproved by distinct people, applied in seconds
Roles, grants, and denialsAgent allow, confirm, or denySignature meaningsWorkflowsTriggersRedaction codes
L4
Agent presetA regulated baseline, or each permission set individually
Signing, by meaningDestruction approvalSharingHold releaseRelease activationBreak-glass
01
Policy as code
Every access decision is evaluated by policy, denied by default, and recorded with its reasons. An explicit denial always overrides a grant.
02
Existence stays hidden
Users who may not see a record cannot tell that it exists. Search results, lists, and counts treat hidden and missing records the same way.
03
Authorization in the query
Access rules are applied inside the database query, so results contain only what the user may read and reveal nothing through counts or timing.
04
Signatures with meaning
Each electronic signature records its meaning, is bound to the exact version signed, and requires a fresh sign-in.
05
Break-glass, reviewed
Emergency access is time-limited, requires a justification, triggers an alert, and is always reviewed afterward.
06
Scoped external access
Inspectors, auditors, and counterparties get scoped, expiring, watermarked access without a user seat, with a report of everything they accessed.
03 Auditability
Don't trust us. Verify.
Every change is written to a hash-chained ledger in the same transaction. Checkpoints are signed with a key the database cannot use and timestamped by an independent authority. Auditors can verify records, disclosures, and evidence offline, on their own laptop, without access to our systems.
#48210createdprev 00a1…
#48211reviewedprev 9f3a…
#48212signedprev 4be1…
#48213effectiveprev c21e…
#48214disclosedprev 7d0f…
checkpointsignedRFC 3161
✓ verified offline
0failure modes specified, each with defined behavior
0operations available to agents, each governed by policy
0product controls tied to tests and runtime checks
0installation checks that qualify each deployment
Catalog figures from the current release line.
Controls map to
- 21 CFR Part 11
- EU GMP Annex 11
- GDPR
- EU AI Act
- ISO 13485
- SOC 2
- ISO/IEC 27001
- HIPAA
Product controls map to these regulations and standards and provide evidence for your own validation and audits.
Agent oversight built for
- EU GMP Annex 22 (draft)
The draft EU GMP Annex 22 keeps generative AI out of critical GMP applications and expects qualified people to stay responsible for AI outputs. Under the regulated agent preset, only named people approve and sign.
04 Privacy and retention
Keep what the law requires. Forget what it allows.
Regulations require you to keep records for years, and privacy laws such as the GDPR require you to erase personal data. Tabellion supports both without breaking the audit trail.
[ Privacy ]
- A key per person. Each person's data is encrypted with its own key. Erasure destroys the key, and the audit trail still verifies.
- Pseudonymous attribution. The audit trail identifies users by stable pseudonymous IDs, so erasure keeps the record of who did what.
- A key per file. Every stored file is encrypted with its own key, and its integrity is checked on every read.
- Access is logged. Views and downloads are logged before any content is served, at the level you configure. Access to personal data is always logged.
[ Retention ]
- Longest period wins. Retention is set per record type, including permanent retention, above a minimum the deployment enforces. When rules overlap, the longest period applies.
- Holds stop the clock. A legal hold blocks disposition and destruction, regardless of the retention schedule.
- People approve disposal. The system proposes disposition, and records administrators approve it.
- Lawful early destruction. Records can be crypto-shredded early under a legal order with two approvers, and the audit trail still verifies.
05 Industries
Built for the ones who get audited.
One core serves every industry. Each vertical is configured with its own record types, lifecycles, policies, and retention rules, without changing the code.
01Life sciences and pharmaControlled documents, deviations, CAPA, and training records, designed for 21 CFR Part 11 and EU GMP Annex 11, with the human oversight of AI agents that the draft EU GMP Annex 22 expects.02Medical devices and healthcareDesign history, complaints, and access records with controls that map to ISO 13485 and HIPAA.03Banking and financial servicesSystems of record where every decision, approval, and change remains verifiable for its full retention period.04InsuranceClaims files and underwriting records with long-term retention and lawful, verifiable destruction.05Government and public recordsRecords management for state, county, and city agencies, including records requests and disclosure tracking.06LegalMatter files with strict access controls, legal holds, and a verifiable chain of custody.07Law enforcement and courtsEvidence and case records with sealing and a tamper-evident history.08Energy, oil and gasProcedures, inspections, and incident records across sites, contractors, and regulators.09Defense and aerospaceControlled technical data, time-limited access for outside parties, and air-gapped deployments.10Support and case managementTickets and cases that retain their evidence long after they close.
06 For software vendors
The record layer inside your product.
Built for vendors of QMS, banking, case management, ticketing, public records, legal, and court software. Embed Tabellion as your record-keeping infrastructure and ship it under your own brand.
01
White label
Your product name, set in configuration, appears on every customer-facing screen, document, agent session, and error message.
02
One API for records
Records, documents, signatures, workflows, retention, and the audit trail are available through one API. You build the user experience, and each vertical is configuration.
03
Every capability through MCP
One contract served over gRPC, REST, and MCP. Agents use every staff capability under the same policies as people.
04
Validation evidence, generated
Requirements, traceability, and IQ/OQ protocols are generated from the same traces as the code, with checks that qualify each installation.
05
Any cloud, or air-gapped
Tabellion runs on Kubernetes with no dependency on a cloud provider. Licenses and releases are verified offline, and the software never calls home.
06
Isolation per company
Each company is provisioned with its own database, encryption keys, storage, and audit trail.
07 Tabellion Cloud early access
The same proof, hosted.
A hosted service for regulated teams that need document and records management with a verifiable audit trail, and for developers whose agents need a system of record. It is an alternative to legacy ECM suites and file-sharing services, with evidence you can verify yourself.
- EU and US regions
- A dedicated database, encryption keys, storage, and audit trail for each company
- Signed, verifiable export to your own deployment at any time
[ FAQ ]
Common questions.
What Tabellion is, how it works with AI agents, and how it supports regulated record-keeping.
01What is Tabellion?
Tabellion is an agentic system of record for regulated industries. It manages official records, including documents, approvals, electronic signatures, retention requirements, and a tamper-evident audit trail of every change.
02Who is Tabellion for?
Software vendors that build regulated products, such as QMS, banking, case management, ticketing, public records, legal, and court software. They embed Tabellion and ship it under their own brand. Tabellion Cloud, a hosted service, is in early access for regulated teams and for developers whose agents need a system of record.
03How do AI agents work with Tabellion?
Agents reach every staff capability over MCP (Model Context Protocol), under the authority of the person they act for and never beyond that person's permissions. High-risk actions wait for a named person to confirm them out of band with a fresh sign-in, and every tool call is recorded in the audit trail.
04Which regulations and standards does Tabellion map to?
Product controls map to 21 CFR Part 11, EU GMP Annex 11, GDPR, the EU AI Act, ISO 13485, SOC 2, ISO/IEC 27001, and HIPAA. They provide evidence for validation and audits. Tabellion holds no certification, and compliance depends on how each organization configures, runs, and validates its systems.
05Does Tabellion support the draft EU GMP Annex 22 on AI?
The draft excludes generative AI and large language models from critical GMP applications and expects qualified people to stay responsible for AI outputs. Under the regulated agent preset, agents draft and named people review, approve, and sign, with every agent action recorded in the audit trail. Tabellion can also hold AI test data and validation evidence under access control, access logging, and retention. Validating an AI model remains the regulated user's responsibility.
06How can an auditor verify the records?
Every change is written to a hash-chained ledger. Checkpoints are signed and timestamped (RFC 3161) by an independent authority, so an auditor can verify records, disclosures, and evidence offline, without access to the vendor's systems.
07Are records immutable?
Records are tamper-evident: every change creates a new version and an entry in the hash-chained ledger. Where the storage supports object lock, content can also be written in WORM mode until its retention ends. This is a per-deployment setting.
08How does Tabellion balance GDPR erasure with record retention?
Personal data about each person is encrypted with its own key, so erasure destroys the key while the audit trail still verifies. Retention schedules, legal holds, and approved disposition keep what the law requires.
09Where does Tabellion run?
On Kubernetes, in any cloud or on premises, including air-gapped networks. Licenses and releases are verified offline, and the software never calls home.
10Can Tabellion be white-labeled?
Yes. The product name on every customer-facing screen, document, agent session, and error message comes from configuration.
[ Contact ]
Build your product on proof.
Tell us what you build and who audits it. We'll show you how Tabellion fits into your product and how it answers your auditors' most common questions.