ITL SOFTWARE · TIME-TO-MARKET & MAKE-OR-BUY

TI-M Headless Client: assess time-to-market potential. Make a grounded make-or-buy decision.

Could an existing TI-M Headless technology foundation shorten the path to production? Compare remaining development, integration and approval work without pre-judging the outcome. For the agreed non-production scope, software licence fees are €0 until the defined go-live.

Received a personal invitation? Simply reply to that email — no additional form required.

Technology architecture · subject to validation
Modular TI 2.0 technology foundationJava/Quarkus and Native · defined local interfaces · separate product profiles
JAVA / QUARKUS Enterprise host · Panama/FFM · local ABI Integration fully supported View integration architecture
iOSNative mobile / iOS
ANDNative mobile / Android

Identity and cryptographic key material remain in the appropriate product and device trust boundaries. A shared codebase does not imply shared keys or cross-profile approval.

Native enterprise-host integration also remains available. Specific SDK artefacts, host compatibility and release qualification remain separately verifiable.

Available technology · bounded first version

Assess time-to-market potential before committing to further in-house investment.

Without questioning existing architecture decisions, compare the actual work remaining on each feasible path to a usable, compliant and operational release. Review scope, integration fit, outstanding approvals and broader TI 2.0 reuse before choosing in-house development, ITL or a hybrid.

01

Independently developed technology foundation

Review the bounded Headless feature set, local integration contracts and disclosed verification gaps. Technical implementation details and stack choices remain part of the later source review, not a prerequisite for the initial strategic discussion.

02

Software licence fees: €0 until go-live

Under a written agreement, non-production evaluation, testing and integration of the agreed first-version scope incur no software licence fees until the defined go-live. Contractually agreed source-code access is included; ordered services may be billed separately.

03

An outcome-neutral decision

Continuing internal development, evaluating ITL, staged integration or declining the offer all remain valid outcomes. No customer-specific assessment or superiority claim is made in advance.

TIME-TO-MARKET · COMPARABLE EVALUATION

What must be compared to estimate time to production?

For the agreed use case, establish a common baseline and assess the remaining critical path for each option. The evaluation may identify time savings — but does not assume them.

  1. Remaining development

    Missing functions, quality gates and actual engineering backlog.

  2. Integration effort

    Host adapters, E2EE boundaries, migration and required integration tests.

  3. Approval and release

    Applicable gematik requirements, security evidence and outstanding Zulassung work.

  4. Time to production

    Critical-path milestones, operational readiness, dependencies and schedule risks.

No production date, percentage time reduction or faster certification is promised before comparative evidence exists.

Before agreed go-live

€0 software licence fees for the agreed evaluation, test and non-production integration scope. Optional professional services are separate.

After productive go-live

Instance-based commercial use under a separately agreed rate card, measurement unit, billing term and rights. No surprise production charge.

Commercial boundary: Before go-live: software licence fee €0 for the agreed non-production scope. After the defined productive go-live: transparent instance-based licensing under separately agreed prices, units and billing periods. Scope, source rights, third-party licences, liability, services and the productive licence must be signed before the respective use.

Explore the Open Platform evaluation View technology demonstrations

Existing source-bound development foundation. Product scope, source-code access and evaluation rights are agreed in writing; no public open-source licence is implied.

TI 2.0 · strategic added value

One technology foundation. Several potential application paths.

The Headless Client is the starting point for evaluation. Potential reuse across TI 2.0 use cases may avoid duplicate work, but is assessed separately for each product profile and normative version.

TI-M Headless Client Pro

Local integration interfaces, server-side E2EE trust boundaries and reusable Headless components for defined Enterprise contexts.

TI-M Pro and Matrix integration

Homeserver architectures, V-Bucket scaling concepts and auditable, high-throughput integration boundaries as potential building blocks.

Future app for insured users

Potential reuse of technology components in the context of the Draft_App_26_1 gematik specification. Native device identity, ZETA and TI-M product requirements remain separately assessed.

TI-Flow and TI-Flow Fachdienst

BPMN Core Execution as a technology basis for process orchestration and high-throughput, auditable integration; normative fit must be reviewed per applicable release.

Technology reuse requires separate identity, key management and security designs for each product profile.

OPEN PLATFORM · INDEPENDENTLY VERIFIABLE TECHNOLOGY

Open Platform instead of a black box. Inspect, verify, decide.

Open Platform does not mean an unrestricted public open-source licence. Within an agreed written evaluation, ITL offers access to the complete source code of the contractually agreed components, their documented integration boundaries and available build and test evidence. This allows enterprise customers to assess architecture, risks and long-term options independently.

CONTRACTUALLY AGREED EVALUATION SCOPE

Source & interfaces of agreed components

Defined components, revision and verification rights

Source & dependencies
Local interfaces & trust boundaries
Available builds & tests
Your independent decision basis

Integration fit · security questions · evidence gaps · make-or-buy options

Three concrete forms of independence

01

Understand what you integrate

Inspect agreed component source, local API/ABI contracts, E2EE trust boundaries, declared dependencies and known gaps.

02

Verify instead of taking claims on trust

Examine versioned build instructions and available test artefacts; repeat supported checks within the agreed scope and record deviations and missing evidence.

03

Preserve real decision options

Compare an in-house build, an ITL integration or a hybrid approach on evidence. Change, OEM, escrow and continuity rights may be negotiated separately; none are presumed granted.

How a verifiable evaluation can work

A proposed process, not a blanket promise that every artefact or test is already available. Scope and available evidence are confirmed before review.

  1. Agree the review scope

    Specify components, release version, access, permitted checks and exclusions in writing.

  2. Inspect the technology

    Review source, integration contracts, dependencies, trust boundaries and known limitations.

  3. Reproduce available evidence

    Run the supported build and test steps, assess integration points and record gaps.

  4. Record a decision

    Document findings, remaining work, risks and the viable make-or-buy paths.

Does Open Platform mean Open Source — and what rights are actually included?

Evaluation — subject to written agreement

Inspection of the complete source of agreed components and agreed audit, build and test activities within the defined non-production scope.

Additional rights — separately negotiable

Productive use, own modifications, redistribution, sublicensing, OEM, maintenance, source escrow and continuity or exit arrangements.

The openness is technical verifiability and negotiated freedom of action — not an automatic transfer of IP or an unrestricted source licence.

Contractual boundaries: Component and release scope, repository access, inspection and build rights, confidentiality, third-party licences and IP are defined in writing. Source access is not a public open-source licence, a conformity claim or automatic permission for production, changes, redistribution or sublicensing.

Technology & intellectual property

Three European patent applications complement the technology portfolio.

The managing director has filed three European patent applications personally. They concern technology directions relevant to a potential longer-term cooperation. Applications are not granted patents; scope, ownership and usage rights remain subject to contractual agreement.

Local Headless integration

Local, decoupled integration interfaces for Headless Client architectures.

Resilient event delivery

Fault-tolerant, asynchronous and encrypted event transmission.

Structured FHIR / ISiK processing

Transactional, archive-oriented handling of structured healthcare data.

POTENTIAL FUTURE SCENARIO · PATENT EXAMINATION PENDING

Strategic outlook: patent-backed differentiation

If the three European applications result in granted patents with commercially meaningful claims, protected technology components could contribute to additional differentiation in the TI 2.0 market. Subject to separately agreed licensing rights, technology partners could consider these components in their own product strategies.

No competitive advantage is assured. It depends on grant, final claim scope, territorial coverage, enforceability and the agreed licensing rights. Exclusive rights are not part of this public offer.

Technology investment decision

Compare alternatives on facts — not language preferences.

The question is whether a specialised Matrix/E2EE core needs to be built again, not whether the host must abandon Java. Both Native and Java/Quarkus integration are fully supported by ITL; no customer implementation is judged without evidence.

Build option

Continue an in-house Java build

Preserves internal control and Java skills. Remaining implementation, normative delta, testing, operation and maintenance costs must still be budgeted. We do not assume the maturity or defects of any customer project.

Existing development foundation

Evaluate ITL Native Headless integration

Evaluate the bounded Rust-based Headless core and local integration contract. Source access and non-production licensing are set out in written terms.

Discuss this integration path →
Java/Quarkus fully supported

Evaluate Rust Core + Java/Quarkus integration

Keep the host application in Java/Quarkus while Rust owns Matrix and E2EE via local Panama/FFM. ITL fully supports this integration; specific SDK artefacts, host compatibility and release qualification are evaluated separately.

Discuss this integration path →

Decision criterion: Compare requirement fit, source and build evidence, remaining development, integration, approval and operational work, time-to-production and migration risk. No measured time saving or superiority over a customer implementation is claimed in advance.

ITL fully supports Java/Quarkus integration. Specific SDK artefacts, host compatibility and release evidence remain separately verifiable. See evidence boundaries →

Trust boundaries · product types

A network API does not move the E2EE endpoint to the iPhone.

Select an architecture context to see where identities, keys and plaintext are handled. These are product-type distinctions, not statements about any customer implementation.

01 · Enterprise contact centre — central Headless Pro
Cryptographic endpoint
In the server-side Headless Client module (Matrix E2EE).
Keys / identity
Matrix actor/device keys isolated within the Headless environment; remote frontend is not automatically a separately verified Matrix device.
Applicable normative context
TI-M Pro Headless Client · A_28651 / A_28710 / A_28715 / A_28734.
Evaluation consequence
An integrating backend may offer a protected network interface, but must preserve the local Headless API and account for plaintext exposure after decryption.
02 · Native TI-M client — mobile communication
Cryptographic endpoint
In the relevant TI-M Client on the endpoint device, depending on the applicable mobile product profile.
Keys / identity
Client-designated protected stores; specified Matrix SSSS mechanisms can be used for encrypted recovery, not as a substitute for on-device cryptographic operations.
Applicable normative context
TI-M Basis · A_25570 / A_26435-01; additional TI-M ePA/Connect product requirements must be checked.
Evaluation consequence
A server-side Headless Pro instance does not automatically satisfy a native insured-user TI-M product profile.
03 · App for insured users — mobile ZETA Client
Cryptographic endpoint
Mobile ZETA client registration and proof-of-possession on the device; ZETA is not a Matrix E2EE endpoint.
Keys / identity
Locally generated, protected against export; Apple/Android attestation and device-binding requirements apply.
Applicable normative context
ZETA 1.3.2 · A_25432-01 / A_25769 / A_25768; App/DiPag references are draft/version-bound.
Evaluation consequence
Backend proxy access does not by itself prove the required device-bound ZETA client identity.
Primary gematik specifications: TI-M Pro 1.2.0 TI-M Basis 1.3.0 ZETA 1.3.2
Existing ITL demonstrations

Three routes. One verifiable architecture discussion.

All links open existing parts of this website. The demonstrations have different maturity and evidence boundaries.

01 · Headless / OEM

TI-M Headless Client

Local ABI, native integration, host boundaries, R1001 source-bound product evidence and the separate calling design.

Source-bound implementation reviewView demonstration
02 · Mobile / insured user

HCSA / iPhone Duo

Interactive insured-user UI scenarios and an illustrative ZETA flow, with synthetic data and no live TI connection.

Synthetic frontend demonstratorView demonstration
03 · Enterprise integration

MEMM Architecture Explorer

Governance, execution, BPMN, Trace / Evidence and integration boundaries for multiple TI 2.0 application roles.

Conceptual architecture explorerView demonstration
Evidence & limitations

What is shown, what is source-bound and what remains open.

Source-bound evidence

R1001 cites 37/37 bounded Headless operations and 63/63 fixed Messenger domains. These denominators are not full specification coverage or an external interoperability result.

Public demonstration

iPhone Duo, ZETA walkthrough and Architecture Explorer are illustrative, synthetic demonstrations; they do not contact live gematik services.

Requires independent evaluation

Current core-build and native-device acceptance, release-specific AFO delta, mobile key lifecycle and external provider interoperability remain open. No assessment of a customer Java implementation is available.

Implementation stack for technical due diligence

The current ITL Headless implementation uses a Rust core with a local Flat C ABI / FFI boundary and host-language bindings. Source, build and interoperability evidence are evaluated for the agreed release and scope.

Public product status and evidence boundaries Download the executive decision brief (PDF · 2 pages)
Make-or-buy process

Assess the available ITL technology before committing to a new build.

  1. 0130-minute strategic discussion

    Determine whether a bounded make-or-buy evaluation is worthwhile, identify the use case and agree on an accountable decision sponsor.

  2. 02Inspect source and evidence

    Review the agreed source-code scope and what the ITL technology foundation actually implements, what is only demonstrated and what still requires engineering.

  3. 03Test the bounded first version

    Use synthetic data and written acceptance tests; verify integration, E2EE, isolation and error recovery within the agreed scope.

  4. 04Make-or-buy recommendation

    Compare feasible paths to a production-ready and approved solution, including critical-path time, remaining engineering, integration, licensing, operations and migration risks.

ARCHITECTURE FIT REVIEW

30 minutes. Three questions for a clear next step.

The first conversation is an opportunity to clarify whether a bounded technical evaluation is worth planning — without committing to a product decision.

Three questions for the initial discussion
  1. Is a bounded evaluation worthwhile?
  2. Which specific use case should be assessed first?
  3. Who would coordinate the next steps?
No patient records, sensitive user data, credentials or internal customer material should be sent through a public request.
Request a 30-minute discussion

Received a personal invitation? Simply reply to that email — no additional form required.

Technology recommendation ≠ approval claim. Product-type suitability, conformity, performance and commercial value are validated per scope and release.