Adminyra EUDI is in active development. We are looking for software platforms and relying parties that want to test a concrete wallet verification workflow in the sandbox before production rollout.
We are prioritising real multi-tenant software use cases. Share the workflow, the type of customers you serve and roughly how many organisations could use it.
The strongest pilot candidates are software companies with an existing customer base and a clear verification moment inside their product. That gives us a real tenant model and real integration constraints to design against.
The purpose is to validate API ergonomics, relying-party configuration, policy modelling and the end-user flow. It is not a claim that the current sandbox is already a certified production identity service.
That distinction lets both sides learn quickly without weakening the production security bar.
Describe your product, the type of businesses you serve, the verification step you want to improve and roughly how many customer organisations could eventually use it.
That is enough to determine whether the multi-tenant EUDI model fits your platform.
Commercial terms for production service are not published yet. Early conversations are focused first on technical fit and a useful sandbox pilot.
No. The point of the API layer is to keep wallet protocol complexity out of normal application development.
Yes. In fact, vertical software platforms with many smaller business customers are a primary target architecture for Adminyra EUDI.
Model the relying party, define the minimum data request and integrate the application flow before production trust infrastructure is required.