Choose a solution
Identify records, responsibilities and delivery model.
Preserve finalized records and maintain existence/integrity evidence over years. Connect source systems, data storage and trust infrastructure under clear responsibilities.
SaaS · On-premises · API integration
| Input | Service action | Output |
|---|---|---|
| Finalized bytes, components and source metadata. | Check rights, dataset and profile; record the transaction. | Receipt, archiveId/jobId and reconciliation errors. |
| Agreed TSA sources, policy and custody. | Generate/maintain scoped evidence under a risk schedule. | Versioned evidence and contextual verification reports. |
| Authorized export/transfer request. | Freeze scope, package and reconcile recipient handover. | Manifest, authorized data/evidence and transfer acknowledgement. |
| Component | Purpose | How it fits |
|---|---|---|
| Backup | Recover copies after incidents; backup schedule and recovery points. | Combine for recovery; a copy alone does not establish cryptographic evidence history. |
| Object storage | Store objects, versions and storage policies. | Storage layer; storage immutability does not replace evidence-chain verification. |
| DMS / ECM | Manage records, workflows and access. | Finalize source revisions, submit record sets to LTANS and retain mappings. |
| Signing / timestamping | Create signatures or bind a digest to time under a trust source. | Supply inputs; material and evidence still need maintenance over time. |
| Trusted LTANS | Receive, maintain, verify, renew and transfer evidence. | Coordinate source systems, storage and PKI under agreed responsibilities. |
Identify records, responsibilities and delivery model.
Inspect architecture, run examples and reconcile contract results.
Inspect controls, source records and recovery procedures.
Link exact files, attachments and revisions to their source system.
Track verification and risk-based renewal beyond retaining a copy.
Carry data, evidence and context for the recipient to inspect.
Check data and issue tracking references.
Bind data to timestamp evidence.
Read outcomes with evaluation context.
Sustain history through cryptographic change.
Export and acknowledge receipt.
Check retention, holds and approvals.
Bring finalized records from source systems into preservation with an acknowledgement and tracking reference.
View service mechanics →Bind data to hash trees, timestamps and preservation history using the selected ERS or XMLERS model.
View service mechanics →Evaluate data/evidence binding under a specified time, policy and trust context.
View service mechanics →Assess risks and select timestamp or hash-tree renewal before required protection conditions are lost.
View service mechanics →Apply date- or event-based periods, retaining change history and checking holds before end-of-period actions.
View service mechanics →Block disposition of case-scoped records until an authorized hold-release decision.
View service mechanics →Evaluate eligibility, authorize and reconcile stores/copies before concluding disposition.
View service mechanics →Package data, evidence and context for recipient verification and acknowledgement of the custody handover point.
View service mechanics →Package instruments, attachments and supporting documents by case ID with authorized retrieval and holds.
View industry workflow →Preserve credentials and transcripts with issue decisions and linked corrections without exposing full student records.
View industry workflow →Preserve finalized treatment records with linked results and consents while restricting access to health information.
View industry workflow →Reconcile subscriber-record revisions, contracts and service changes between CRM/BSS/OSS and the evidence repository.
View industry workflow →Reconcile transaction documents with approvals and export the exact record set for an audit period.
View industry workflow →Preserve claim-submission rounds to establish which documents supported each decision.
View industry workflow →Use APIs and portals within the operations scope agreed with Mobile-ID.
View managed service →Place preservation on customer infrastructure with explicit storage, key and operations ownership.
View on-premises deployment →Organizational ISO/IEC 27001 and module assessments are presented with scope, source documents and verification status.
Certification recordsDistinguish LTANS requirements, ERS/XMLERS structures, timestamping and PKI infrastructure.
Standards & InteroperabilityReview responsibilities, support, recovery and deployment-specific SLA conditions.
Service assurance modelOrganizations, permissions, policies and approvals.
View tasks and permissions →Jobs, alerts, renewals and recovery.
View tasks and permissions →Deposit, track, search and export records.
View tasks and permissions →Configure applications, credentials and events.
View tasks and permissions →Inspect evidence packages and explain outcomes.
View tasks and permissions →POST /v1/archives
202 Accepted
{ "archiveId": "arc-test-001", "jobId": "job-test-001" }Quick Start, API contracts, events and test cases support integration preparation. Evaluation environments are provisioned on request; this package demo is offline simulation.
Quick Start · SandboxFollow a simulated workflow with exception branches, using no production data or backend calls.
View details →Reconcile a synthetic package with SHA-256 and distinguish integrity checking from ERS evidence.
View details →Discuss deployment, integration, evaluation or support directly with Mobile-ID.
View details →GoPaperless SSO connects user journeys; RAR/C06 SSO/ShareInfo and RS-HUB support provisioned identity, consent and signing. Trusted LTANS preserves authorized transaction outputs and evidence.
Business applications · Five portals
WSO2 API Manager · HTTPS + OAuth2
Keycloak IAM · Token / claims
Archive · Evidence
Kafka · Outbox / Inbox
MariaDB / metadata · Object / evidence stores
TSA / RFC 3161 · CA / OCSP / CRL
Java / WildFly · Observability