Prove who approved a payment.
Approval, identity and rule version sealed at the moment of release.
Start hereProof wins.
Check before actionMonitor for changeProve what happened
- NIS2
- DORA
- CRA
- AI ACT
- AMLR
- eIDAS 2
- PLD
- CCD2
Compliant within 4 weeks
AI can write anything.
Forge anything.
Fake anything.
Reltime proves who recorded it, when, and whether it changed.
Real problems, already here
Different industries. One missing piece. Proof of who did what, under which rule, and whether it changed.
How it works
Illustrative workflow
Step 1 of 5
Payment release · INV-2291
Gate 1 · Identity
Finance approver · verified
Gate 2 · Rule
Release policy v3.2
ApprovedHeld for reviewDenied
Evidence receipt
who: finance.approver.07 · rule: release-policy v3.2 · time: 10:42:07.118 · fingerprint: 9f3a…c41e · anchored ✓Evidence feed
- 10:42:07 · finance.approver.07 · approved · anchored ✓
- 10:41:52 · treasury.lead.02 · held for review · anchored ✓
- 10:41:30 · ops.clerk.14 · denied · anchored ✓
Reltime verification receipt
Illustrative1 · Action
What happened, as recorded by your own system.
2 · Identity
Who acted, verified at that moment, in that role.
3 ·
The exact policy that allowed it.
4 · Time
Anchored on the network and final within two seconds.
5 · Integrity
Any change breaks the match the moment the record is verified. Connected monitoring alerts the responsible team when a mismatch is detected.
Zero trust
Check before access.
Every request proves who is asking, in which role and with what authority. Checked on every call.
Continuous trust
Recheck when anything changes.
A revoked credential, a changed status or an access outside pattern triggers a new decision and a real-time alert.
Governed trust
Responsibility made explicit.
Who sets the rules, who approves exceptions, which version applied. All of it on record.
Always on monitoring →Verified once. Provable everywhere. →Eight rails. One engine. →
Live console
Demo environment · sample data · no real customers
Choose your problem
Control access to sensitive information.
Each request checked before data leaves, alerts on denied access.
Start hereBuild a verifiable incident timeline.
Every step from first signal to notification, signed and in order.
Start hereTrack supplier changes and exceptions.
Supplier evidence per version, alerts when it changes or is withdrawn.
Start hereProve which AI model and policy supported a decision.
Model version and approval bound to every decision.
Start hereProven in the field
Project 01European Defence Fund · GA 101121403
Illustrative imageNEWSROOM
Verified in defence.
Consortium member- Reltime's role
- Consortium member in its own name. Verification layer for shared information.
- Status
- Active European Defence Fund project
- Evidence
- Official EDF factsheet ↗
- Last updated
- October 2026
Reltime has delivered the Governed Verification Layer to NEWSROOM.
NEWSROOM is funded by the European Union under the European Defence Fund, grant agreement 101121403. Views expressed are those of Reltime AS only.
Project 02Horizon Europe · GA 101137301
COMFORTage project imageCOMFORTage
Health data, kept intact.
Deployed infrastructureTRL 7 · COMFORTage- Reltime's role
- Data integrity system built in partnership with NTNU, running live on Reltime Mainnet
- Status
- Project validated in 13 pilots across 8 EU member states. Reltime's integrity system serves the project platform.
- Evidence
- Public deliverable D3.6 · Project site ↗
- Last updated
- October 2026
Reltime has delivered the Governed Verification Layer to COMFORTage.
COMFORTage is funded by the European Union under Horizon Europe, grant agreement 101137301. Views expressed are those of Reltime AS only.
Project 03Regulated finance
Product interface · AXY MarketsAXY Markets
Assets, proven.
Operational on Reltime- Reltime's role
- Platform built and owned by Reltime. Identity, document anchoring and conditional release of funds.
- Status
- Platform operational since August 2026. First issuance in preparation.
- Evidence
- Available on request under NDA
- Last updated
- October 2026
Consortium participation is not an endorsement by other participants.
THE OLD ERA IS OVER
Evidence
Dug out of inboxes when the supervisor calls
Evidence
Ready before anyone asks
Monitoring
A sample once a year and hope
Monitoring
Every connected event watched. The right team alerted the moment it matters.
Audit trail
Your own logs, your own word
Audit trail
Independent proof anyone authorised can check
Identity
The same passport photographed five times
Identity
Verified once, proven everywhere
New regulation
Another consultant, another project
New regulation
One rule update, everyone moves
Start
A year-long programme
Start
Live pilot on one workflow in about four weeks
The first in line sets the standard. Everyone after follows it.
Find your starting pointTRY THIS ON MONDAY
Five questions your current setup cannot answer.
Who approved this, under which rule version, at what second?
Can an outsider verify that this log has not changed since?
Which customer changed risk status yesterday, and who was told?
If the supervisor asked for your incident timeline now, how long would it take?
When the rules change next month, how many systems do you rebuild?
Start with one.
- Week 1
Map the obligation and connect the first system
- Week 2
Configure the workflow, roles and alerts
- Week 3
Test and review with your counsel or auditor
- Week 4
Run and deliver the first evidence pack
Questions
Proven in European Defence Fund and Horizon Europe programmes
Built for Europe's rules →