Skip to content
Reltime

Who acted. Under which rule. What changed. Answered for every critical action.

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.

Checked at the door, rechecked when anything changes, accountable all the way through.

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.

Approved
Scope follows the systems and signals you connect.
Identity as evidence

Provable everywhere. The issuer checks, Reltime anchors, the customer carries the proof.

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. 1

    Verification

    Result received from the issuer

  2. 2

    Anchoring

    Fingerprint, timestamp, signature

  3. 3

    Attestation

    Tied to the customer's own identifier

  4. 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
Reltime issues no identity and stores no ID copies. The relying party keeps its own due diligence duty.

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

When conditions change, alerts fire and intervention follows the rule that applies.

Illustrative workflow
Step 1 of 6

  1. 01

    Signal received

  2. 02

    Rule evaluated

    Suspected

  3. 03

    Alert assigned

    Confirmed

  4. 04

    Authorised review

  5. 05

    Decision anchored

    Anchored

  6. 06

    Workflow resumed or refused

    Resolved
An alert stops an action only where an enforcement point is connected and someone holds the authority to act.
Verification demo

Seal a document, change one character and see the fingerprint fail.

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

Due diligence becomes a state you can prove at any second.

Illustrative workflow
Step 1 of 4

Today's process

No picture of the customer between checksOnboardingPeriodic reviewMonth 0122436
⚠ Event occurs · month 9⚠ Found at the next review · month 36

With Reltime

Onboarding⚠ Real-time alert⚠ Real-time alert⚠ Real-time alertMonth 0122436
  • Status change at the issuer · month 9
  • Anomalous transaction · month 19
  • Access outside pattern · month 29
Every event is anchored as it occurs. Supports the ongoing monitoring duty in AMLR Article 26.
Illustrative workflow
Step 1 of 5

  1. 01

    Condition changes

  2. 02

    Exception detected

    Suspected

  3. 03

    Reviewer assigned

    Confirmed

  4. 04

    Decision documented

  5. 05

    Action held or denied

    Integrated control point

The action stops where a control point is connected and someone holds the authority to act.

Where Reltime sits

Compliance tools organise. AI agents interpret. Ledgers timestamp. Reltime joins regulation, identity and independent proof in one layer.

How regulation becomes controlsBy handGenerated by AIWho holds the proofThe company under reviewAn independent networkCompliance automationand GRCAI regulatoryagentsCloud ledgersQualified trustservicesIntegrity chainsIdentityprovidersReltime withAI Brain
Concept illustrationCategory positions reflect Reltime's assessment.

Most of this field is distribution for Reltime. Every platform they sell can carry Reltime's proof underneath.

Where Reltime fits

CategoryWhat it does wellWhere Reltime fits
Compliance automation and GRCAutomates control checks, audits and policy workflowsChannel. Reltime proves what they organise.
AI regulatory agentsReads regulation and assesses complianceReltime adds identity-bound, independent proof.
Qualified trust servicesLegally recognised signatures and sealsPartner. Each signature becomes an event in the trail.
Cloud ledgersTamper-evident records inside one provider's cloudReltime adds independence across parties and providers.
Integrity chainsIndependent timestampsReltime adds accountable operators, identity binding and the regulatory layer.
Identity providersVerify who a person or company isPartner. Reltime anchors their checks and monitors them over time.
Architecture

Add the proof. Reltime runs inside them through APIs.

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.

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

We bring the API catalogue.

Talk to Reltime