FINES
The fine starts where the evidence ends.
Supervisors fine what you cannot show. Reltime produces the evidence as the work happens, so the answer exists before the question.
One layer under your existing systems that answers three questions for every critical action. Who acted. Under which rule. What changed. It has run in production since November 2021.
Check before access.
Every request proves who is asking, in which role and with what authority. Checked on every call.
You configure which identity sources count and which roles may act, per action.
Recheck when anything changes.
A revoked credential, a changed status or an access outside pattern triggers a new decision and a real-time alert.
You choose the signals that matter, from issuer status to access patterns, and who gets the alert.
Governed trust
Responsibility made explicit.
Who sets the rules, who approves exceptions, which version applied. All of it on record.
You name the rule owners and exception approvers, and every rule version is kept on record.
Illustrative workflow
Step 1 of 6
Dr. Lind · Clinician
Request arrives. Identity ✓, role ✓. Receipt anchored.
Identity as evidence
BankID, the EU Digital Identity Wallet and KYC providers perform the check. Reltime anchors the result, ties it to an identifier the customer controls and answers the next party with a proof.
Illustrative workflow
Step 1 of 4
Issuer
- · BankID
- · EU Digital Identity Wallet
- · KYC provider
Performs the check and is responsible for the identity.
Verification result
Reltime verification layer
1
Verification
Result received from the issuer
2
Anchoring
Fingerprint, timestamp, signature
3
Attestation
Tied to the customer's own identifier
4
Proof
Checkable answer to the next party
Continuous monitoring
Status changeAnomalous transactionAccess outside pattern
Proof · Real-time alert
Relying party
- · Bank
- · Insurer
- · Broker, dealer, authority
Receives the proof and makes its own risk assessment.
Attestation to the wallet
Consent and proof
The customer
Holds their own identity (DID) and chooses what is shown to whom.
✓ Verified by BankID, level high✓ Over 18✓ PEP status checked
Beyond identity
- Beneficial ownership
- Registrar attestation ties a company to its owners
- PEP status
- Attestation from an identity or risk provider, checked at onboarding and renewal
- Source of funds
- Attestation from the originating bank, checkable against the issuer's signature
- Staff access
- Every action signed with the employee's identifier, deviations alerted to management and compliance
Alerts and intervention
Illustrative workflow
Step 1 of 6
01
Signal received
02
Rule evaluated
Suspected03
Alert assigned
Confirmed04
Authorised review
05
Decision anchored
Anchored06
Workflow resumed or refused
Resolved
Verification demo
Sample delivery acceptance. Change anything and verify.
Fingerprint · SHA-256
Sealed fingerprint
—
Live demonstration in your browser. On Reltime the fingerprint is anchored to the network instead of this page.
Continuous trust
Illustrative workflow
Step 1 of 4
Today's process
⚠ Event occurs · month 9⚠ Found at the next review · month 36
With Reltime
- Status change at the issuer · month 9
- Anomalous transaction · month 19
- Access outside pattern · month 29
Illustrative workflow
Step 1 of 5
01
Condition changes
02
Exception detected
Suspected03
Reviewer assigned
Confirmed04
Decision documented
05
Action held or denied
Integrated control point
The action stops where a control point is connected and someone holds the authority to act.
THE BUSINESS CASE
CONSULTANT HOURS
Stop paying to rebuild the same proof.
Every new regulation restarts the same project. Reltime builds the rail once and keeps it running, rule after rule.
LEGAL FEES
The evidence pack is already written.
When a payment, a product or a decision is challenged, your counsel starts with a verified record instead of weeks of reconstruction.
AUDIT TIME
Audit the receipt. Move on.
Every event carries its own proof. The audit verifies the record and moves on.
MANAGEMENT LIABILITY
Sleep better in the boardroom.
Under NIS2, management can be held personally liable. A signed trail of who decided what, and when, protects the people at the top.
FASTER SALES
Answer the security questionnaire with proof.
Your enterprise customers audit their suppliers. Send them verifiable evidence instead of a forty-page self-declaration.
What compliance costs today
- EUR 2 to 5 million
- per financial entity for DORA, planned by 64% of entities surveyed
- Source · Deloitte European DORA survey, 2025
- EUR 2.3 billion
- Every year. What NIS2 adds for German businesses alone.
- Source · German Bundestag, Drucksache 21/2783
- EUR 193,000 to 330,000
- to set up a quality management system for high-risk AI
- Source · CEPS study for the European Commission
Most of that money is spent collecting evidence by hand. Reltime builds it once and keeps it running.
Find your starting pointWhere Reltime sits
Most of this field is distribution for Reltime. Every platform they sell can carry Reltime's proof underneath.
Where Reltime fits
| Category | What it does well | Where Reltime fits |
|---|---|---|
| Compliance automation and GRC | Automates control checks, audits and policy workflows | Channel. Reltime proves what they organise. |
| AI regulatory agents | Reads regulation and assesses compliance | Reltime adds identity-bound, independent proof. |
| Qualified trust services | Legally recognised signatures and seals | Partner. Each signature becomes an event in the trail. |
| Cloud ledgers | Tamper-evident records inside one provider's cloud | Reltime adds independence across parties and providers. |
| Integrity chains | Independent timestamps | Reltime adds accountable operators, identity binding and the regulatory layer. |
| Identity providers | Verify who a person or company is | Partner. Reltime anchors their checks and monitors them over time. |
Architecture
Illustrative workflow
Your environment
- ERP
- Core banking
- Case management
- Identity provider
- Source records
DocumentsPersonal dataRecord content
Cryptographic commitments and verification metadata
Reltime
- Identity and policy check
- Event anchoring
- Alerts
- 300+ APIs
Authorised reviewer
- Auditor
- Supervisor
- Counterparty
Receives a receipt and verifies it against the anchor.
Does our data move to Reltime?
No. Your data stays home. Only fingerprints go to the network.
What does a fingerprint prove?
That this is the exact record, sealed at that second, by that identity. Change one character and it fails.
Who can verify?
Anyone you authorise. Auditor, supervisor, counterparty. No access to your systems needed.
What if a sealed record is changed or deleted?
The fingerprint breaks and your team gets the alert in real time. Nobody cleans up quietly.
Who runs the network?
Known, approved operators on a governed network that has run without pause since November 2021.
How long does implementation take?
Four weeks to a live pilot on one workflow. Then rail by rail.
Under the hood
Reltime runs a governed, proprietary blockchain built for regulated use. Known, approved operators. Deterministic finality. Personal data stays off the network.
Mainnet explorer →Network parameters confirmed by Reltime
- In production since November 2021
- Up to 37,500 transactions per second
- Two-second deterministic finality, IBFT 2.0 consensus
- Permissioned proof-of-authority network
- EVM compatible
- 300+ documented APIs, including wallet and KYC
- Real-time alert when sealed logs or documents are altered or deleted