See it work. Prove its worth. Carry it forward.

Launch period. €0.

1. 01
   Use the public products

   Explore browser-local product records, the Web Wallet, test credentials, developer contracts and open-source protocol libraries.

2. 02
   No card. No paid conversion.

   Launch access does not ask for payment details and does not become chargeable merely because time passes or a test succeeds.

3. 03
   Paid use begins by acceptance

   Future pricing is published before it applies. A person or organisation explicitly accepts the paid terms before charges begin.

The current offer in exact terms.

• Current product price€0 during the launch period.
• Payment card requiredNo.
• Automatic paid conversionNo.
• Future price basisNot fixed. Published before charges begin; paid terms require explicit acceptance.
• Paid-use export pathRequired before paid terms can be accepted.
• Retained-data export formatStructured, commonly used and machine-readable, with formats, interfaces and known limits documented.

Know how to take your records with you.

Paid use will not begin without a documented path out. Retained records, evidence and the metadata needed to understand them must be exportable in structured, commonly used and machine-readable formats. The formats, interfaces, known limits and switching path must be visible before paid terms can be accepted.

1. 01
   Take the useful record

   Export retained product, Wallet and operation records together with their available evidence and structured data.

2. 02
   Take the meaning with it

   Carry identifiers, provenance, schema versions and receipts so another system can inspect what a record means and where it came from.

3. 03
   Keep protected data protected

   Portability does not make private data public. Access controls, personal data, security boundaries and protected third-party rights continue to apply.

For data-processing services within its scope, this product direction also reflects the EU Data Act's requirements for switching, open interfaces and machine-readable export. Exact scope and protected-data boundaries still depend on the service and data involved. Read the official regulation ↗

Begin with one result people can use.

• Source-bound product data Map existing information into one governed product record, show the right recipient view, validate what is known and carry the evidence forward.
• Wallet exchange and authority Run an issuer → Wallet → verifier interaction and keep the exact build, protocol profile, requested and disclosed attributes, result and failure boundary together.
• Accountable action and receipt Give a person or agent bounded authority, preview consequential work, keep responsible people in the decision and preserve a receipt that can support acceptance and invoicing.
• Facts and possible futures Bring facts, proposals and alternatives into one explainable exploration, then see what a decision would change before carrying it into action.

Measure first. Price with evidence.

Our pricing path starts by measuring product operations at zero price. The planned billing experience uses explicit charge types, links charges to action records and shows expected spend before a commitment. Those screens are not a current public capability. Durable plan names and usage units will follow real product use.

Before any paid product use begins, the organisation will see what is charged, which actions drive it and how the expected amount is calculated. Until then, the public launch price is €0.