Wallet-native
No Alentra identity enrollment. The holder presents a ledger-approved credential through its provider flow; pre-launch validation uses approved reference environments.
About
The composition layer
for digital identity.
Alentra is a small API surface for four things: identify, age_verify, light_sign, and sign. One bound user completes those steps through one server-validated country, credential, and provider route.
Alentra is a brand operated by Komplete10 LTD, a company registered in the United Kingdom and operating from Sweden.
Why it exists
Identity is
stuck.
On the consumer web, identity is still passwords, one-time codes, and form-filling — patterns that haven't fundamentally changed since the 1990s. On the regulated side, it's national schemes like BankID, controlled by a handful of banks, priced accordingly, and largely unusable outside their home jurisdiction.
There should be a smaller integration surface between relying-party applications and government wallet credentials. Alentra keeps that surface stable while country and wallet coverage expands behind a canonical route ledger.
Principles
Three things
non-negotiable.
01 / PORTABLE
Use the credential already issued
Alentra does not create a new identity credential. It requests a supported government credential already held in the user's wallet.
02 / VERIFIED
Anchored to real identity
Every credential is a government-issued document held in the holder's device wallet, cryptographically presented and verified against the issuing authority. Cryptographic, not self-reported.
03 / OPEN
Small, explicit API surface
Four primitives and ordered steps keep integrations inspectable. Production wallet access still requires the applicable provider approvals and credentials.
How it works
Built on small,
stable primitives.
Government-verified
Alentra verifies the wallet response and records immutable evidence. Legal effect is not automatic: consent, attribution, record access, transaction type, jurisdiction, and implementation all matter.
Orchestration, not policy
Alentra unifies wallet routes behind four composable primitives, ordered steps, signed at-least-once webhooks, and durable audit IDs. Your application still owns every business decision.
Where it started
An open
substrate.
Alentra came out of a mundane frustration: managing dozens of passwords across dozens of identity silos, while the only serious alternative in the region — BankID — was locked behind a few banks, priced for enterprise, and inaccessible to most independent developers or small businesses.
The product thesis is simple: relying parties should integrate a small set of stable verbs instead of rebuilding wallet plumbing for every workflow. Alentra keeps the credential with its issuer and holder while standardizing the application-facing session flow.
Alentra Research
Primary sources,
clearly dated.
Alentra Research is the company’s editorial desk, not a fictional individual. Field notes are checked against primary legislation, published standards, official wallet-provider documentation, and issuer or government sources before publication.
We date claims that can change, distinguish confirmed capability from inference or roadmap, link the controlling source where practical, and update the article when the underlying program changes. Product coverage remains governed by Alentra’s canonical route ledger, not by marketing copy.
Field notes explain technical and regulatory developments; they are not legal advice. Corrections can be submitted through the contact form.
Government credentials, one workflow API.
Test with the EUDI reference wallet, then complete the applicable provider, issuer, and Alentra production requirements.