ITL Software · TI-M Pro

One TI-M Pro. Six target platforms.

A common communication and E2EE architecture for macOS, Windows, Linux, iOS, Android and Web — with explicit device ownership and a separate Headless integration profile.

Optional application / business layer Functional account · Automation · BPMN · Approval tim-fa: staff-managed · tim-bot: automated
Two parallel product profiles
User client profile TI-M Client Pro
DesktopmacOS · Windows · Linux
MobileiOS · Android
WebBrowser
Independent headless profile Headless Clientmodul Pro Local module API · external interface belongs to the integrating system
Shared technology layer ITL Unified Core Matrix · E2EE · Sessions · Rooms · Events
Normative foundation TI-M Basis Applicable gematik requirements, not a standalone runtime service
Product scope

Six platforms, one behavioral contract.

Select a platform to inspect the target adapter and acceptance focus. All cards remain readable if JavaScript is unavailable.

Desktop

macOS

Platform adapter · design target

System Keychain, native notifications and foreground / background ownership.

Acceptance and risk

Key protection, per-device identity, permission prompts, sleep and resume, signed updates.

User experience

Professional desktop conversation, room context, document hand-off.

Desktop

Windows

Platform adapter · design target

OS-protected credentials, notifications, per-user storage and application lifecycle.

Acceptance and risk

Lock/unlock, local encryption, multi-user separation, update rollback.

User experience

Enterprise workstations and managed distribution.

Desktop

Linux

Platform adapter · design target

Desktop secret store or an explicitly approved fallback; background lifecycle.

Acceptance and risk

Secret-service availability, least privilege, packaging and desktop environment.

User experience

Technical teams and enterprise desktops.

Mobile

iOS

Platform adapter · design target

Keychain, protected local storage, app lifecycle and push notification adapter.

Acceptance and risk

Background limits, device recovery, lock state and push data minimization.

User experience

Secure mobile communication with native interaction patterns.

Mobile

Android

Platform adapter · design target

Android Keystore, app lifecycle, storage and notification permissions.

Acceptance and risk

Key restore limits, battery policies, backup exclusions and device integrity.

User experience

Managed and personal Android devices under an agreed policy.

Browser

Web

Platform adapter · design target

Browser-native cryptography and storage with an explicit session and data retention policy.

Acceptance and risk

Storage eviction, tab concurrency, CSP, XSS protection and logout behavior.

User experience

Browser-based access without claiming native device guarantees.

Select a platform and carry only its fixed label into your evaluation request. No device or simulation data is sent. Request platform evaluation →

Platform adapters are architectural options, not a verified six-platform release or a claim that the same crypto store can be shared across devices.

Ownership and trust

What is shared — and what must remain separate?

01

TI-M Core

State machines, message semantics, Matrix interoperability and E2EE contracts.

02

Platform adapters

OS vaults, notifications, lifecycle and per-device crypto persistence.

03

Experience layer

Desktop, mobile and browser flows; accessibility and identity transparency.

04

Headless integration

A separate local-only Headless Client API and authorized host orchestration.

Funktionsaccount · BPMN

From personal messages to managed organizational communication.

A functional account is an organizational identity, not an independent messenger. ITL designs delegated handling, BPMN case routing and controlled outward release as a separate business layer.

FunktionsaccountBPMN Core ExecutionApprovalTI-M Pro
Enterprise use case · target model

TI-M Automat for health insurers

One service address, two separate E2EE rooms and controlled forwarding. An example of what can be composed from Headless Clientmodul Pro and an optional orchestration layer.

01

External encrypted room

An insured person contacts the published organizational identity. Automated contacts must be recognisable as such.

02

Authorized automation

The host application pairs room contexts, routes events and attachments under an agreed purpose, and checks invitations and staff access.

03

Internal encrypted room

Employees work in a separate room. Outward replies are released under a documented policy with clear reviewer responsibility.

Important E2EE boundary

The automation component may decrypt and re-encrypt inside a trusted, authorized host. This does not create continuous E2EE between the member and a named employee; legal and provider integration boundaries must be checked.

Explore TI-M Automat & demo →
Integration scope · evaluation

From architecture to an independently testable pilot

Included in the browser model

Two room contexts, invitation states, inward routing, message revisions, explicit release, uncertain send and safe failure paths.

Host-owned integration

Room pairing, BPMN/case orchestration, user permissions, durable outbox and auditable incident response require a defined operating host.

Evidence before go-live

Actual Matrix/Fachdienst test, security assessment, approved service login, allowed forwarding, retention, restart and provider/qualification decisions.

Two separately encrypted Matrix room contexts with an integrating host. The Headless module API stays local; any network interface belongs to the host.

One product architecture · explicit ownership

What belongs to each component?

Client and Headless are parallel product profiles; Native and Java are two paths inside Headless, not additional clients. Business orchestration and normative services remain separate scopes.

TI-M Client Pro

Purpose: User-facing messaging and device-local E2EE

Boundary: Own client identity, keys and platform adapter; no Headless host semantics

Current claim: Six target adapters, not one qualified six-platform release

Inspect boundary →

Headless Clientmodul Pro

Purpose: Embeddable TI-M communication component

Boundary: Local module API only; host owns its UI and any separately designed network gateway

Current claim: Existing development foundation; current release gate open

Inspect boundary →

Shared Rust Core

Purpose: Matrix transport, E2EE, SSSS and session lifecycle

Boundary: Single runtime and crypto owner in the ITL design; native handles do not enter business APIs

Current claim: Existing source-bound foundation; product-specific testing required

Inspect boundary →

Java / Quarkus · Track B

Purpose: Fully supported Java/Quarkus integration for PVS/KIS

Boundary: Java/Quarkus host → existing FFM bridge → local Flat C ABI → Rust; no second Matrix owner

Current claim: Java/Quarkus integration fully supported; SDK artefacts and host release evidence scoped separately

Inspect boundary →

TI-M Automat

Purpose: Organizational handling, room pairing and controlled replies

Boundary: Trusted host owns authorization, forwarding policy, outbox, audits and incident handling

Current claim: Browser scenario; live E2EE and integration not qualified

Inspect boundary →

BPMN Core / TI-Flow

Purpose: Internal business workflow and separate normative Fachdienst scope

Boundary: BPMN does not own Matrix keys or authoritative TI-Flow FHIR Task state

Current claim: BPMN foundation described; complete TI-Flow FD not implied

Inspect boundary →

TI-M Basis

Purpose: Applicable external normative requirements

Boundary: Compliance reference for product profiles; not a deployable ITL runtime layer

Current claim: gematik release reference, not ITL product readiness

Inspect boundary →
Regulatory boundaries

Product-specific requirements, evidence and responsibilities.

Client Pro

Own product-type PTV and platform-specific acceptance must be assessed for each target release.

Headless Clientmodul Pro

Local-only module API; any host network interface remains outside the Headless API boundary (A_28651).

Provider & operations

ATV obligations, controlled integration approval, operating context and independent evidence are separate from code quality.

Reference: TI-Messenger_26_2, gemSpec_TI-M_Pro 1.2.0. Applicability and legally relevant versions must be confirmed for each product and submission. Official source ↗

Headless integration · dual-track architecture

One Headless core. Two integration paths.

ITL fully supports Native and Java/Quarkus integration on the same Rust technology foundation. Host-specific release gates and evidence remain separate.

These are Headless implementation tracks, not two more TI-M Client Pro product profiles.

Inspect Headless integration architecture →

Plan a platform-specific evaluation.

Define supported profiles, project scope, operating model and measurable acceptance before commitments.

Discuss evaluation →

Separate Headless scope → · Evidence and product status →