Prove your EUDI wallet works with real issuers and verifiers.

Device clouds check that your app opens on a phone. Credimi sends a live credential from a real issuer to your wallet, presents it to a real verifier, and checks every step against FCAF and OpenID4VC.

Explore the Hub Start a new test

Live issuer sends a fresh credential offer

openid-credential-offer://
Your wallet accepts the credential on a real phone

SD-JWT VC · mDoc
Live verifier requests and checks a presentation

OpenID4VP 1.0
Judged against FCAF and protocol test cases, with evidence

Tests: Wallets, credential issuers, verifiers
Frameworks: EUDI FCAF, OpenID4VCI, OpenID4VP
Runs on: Android devices, emulators, iOS simulators
Deployment: credimi.io or self-hosted, AGPL-3.0

A device cloud asks:

Does my app work on this device?

Credimi asks:

Does my wallet, issuer or verifier conform, and does it work with the rest of the EUDI ecosystem?

A European Digital Identity Wallet is never tested alone. It succeeds only when a credential issuer, a wallet and a verifier complete a flow together, under OpenID4VCI, OpenID4VP, SD-JWT VC, mDoc and the EUDI ARF, with evidence an assessor can trust.

One pipeline tests the flow between components

Most testing platforms see one system under test. Credimi drives every party of the flow, in order, and keeps the record.

Credimi pipeline

orchestrated and timestamped by Temporal

1 / 5

Issuer

Ask a live issuer for a fresh credential offer (StepCI).
2 / 5

Wallet

Open the deeplink in a wallet on a phone, emulator or iOS simulator, and accept the credential (Maestro).
3 / 5

Verifier

Ask a verifier for a presentation request and complete it in the same wallet.
4 / 5

Validate

Judge what happened against FCAF and protocol test cases.
5 / 5

Evidence

Store every input, output and artifact as reviewable evidence.

A device cloud can run one step of an EUDI flow. Credimi runs the whole journey and judges it.

Each tool is good at its own job

Credimi works alongside these products. Each one answers its own question well; none was built to test EUDI wallets, issuers and verifiers together.

Device clouds

For EUDIW testing:

Tests one app at a time. The issuer, the verifier, the deeplink plumbing and the protocol assertions are yours to build and host.

BrowserStack

Best at: Breadth of real iOS and Android devices for manual and automated app testing (Appium, Espresso, XCUITest), with visual testing on top.
Sauce Labs

Best at: Enterprise-scale web and mobile test execution on real devices, emulators and simulators, with test analytics and error reporting.
LambdaTest

Best at: Fast, parallel cross-browser and mobile app runs, with HyperExecute orchestration for large suites.

Maestro clouds

For EUDIW testing:

Drives one app's UI. No issuer or verifier side, no OpenID4VCI or OpenID4VP conformance, no FCAF test cases.

Maestro Cloud

Best at: Running Maestro flows in parallel on managed emulators and simulators. Flows are short, readable YAML; Credimi drives wallets with Maestro too.

Google and AWS labs

For EUDIW testing:

Device and test-framework coverage, not identity flows: no protocol conformance, no issuer to wallet to verifier journey, no assessment evidence.

Firebase Test Lab

Best at: Robo and instrumentation tests on Google-hosted devices, built into the Firebase and Android Studio toolchain.
AWS Device Farm

Best at: Real phones and tablets inside AWS, with automated test runs and remote access sessions in your AWS account.

Conformance suites

For EUDIW testing:

One component at a time, against a simulated counterpart. No real wallet on a real device and no end-to-end journey. Credimi runs these suites for you, side by side.

OpenID Foundation conformance suite

Best at: The reference tests for OpenID4VCI and OpenID4VP, and the route to OpenID certification.
EC Interoperability Test Bed

Best at: Conformance testing of messages and data against EU specifications.

Credimi

Built for the EUDI question. It runs the suites above for you and adds real wallets on real devices.

Best at: Proving an EUDI wallet, issuer or verifier conforms and interoperates, with evidence.
Best at: Gating releases on wallet × issuer × verifier flows in CI.
Best at: Preparing for FCAF assessment and EUDI ARF readiness.

Compare capabilities:

Grouped by product category. Each column names the products it covers.

At a glance:

Capability	Credimi EUDI conformance and interoperability	BrowserStack Sauce Labs LambdaTest Device clouds	Maestro Cloud DeviceCloud Maestro clouds	Firebase Test Lab AWS Device Farm Google and AWS labs	OpenID Foundation EC Interoperability Test Bed Conformance suites
Built for EUDI and eIDAS 2
Tests issuer, wallet and verifier in one run
Mobile wallet UI automation (Maestro)
Backend protocol conformance (OpenID4VCI, OpenID4VP)
EUDI FCAF test cases built in
Several conformance suites behind one interface
Public hub of live issuers, verifiers and wallets
Audit-grade evidence (timeline, hashes, video, logs)
Runs on your own devices, emulators and network
Open source (AGPL-3.0)

Who you can test, and against whom:

Capability	Credimi EUDI conformance and interoperability	BrowserStack Sauce Labs LambdaTest Device clouds	Maestro Cloud DeviceCloud Maestro clouds	OpenID Foundation EC Interoperability Test Bed Conformance suites
Wallet (Android, iOS): UI flows
Wallet: protocol conformance
Credential issuer: protocol conformance
Verifier / relying party: protocol conformance
Wallet with third-party issuers
Wallet with third-party verifiers
Issuer to wallet to verifier, end to end
Same scenario against many wallets

Partial on device and Maestro clouds means you can script it yourself, but you also build and host the issuer and verifier side, the deeplink plumbing and the assertions.

Evidence kept for every run:

Capability	Credimi EUDI conformance and interoperability	BrowserStack Sauce Labs LambdaTest Device clouds	Maestro Cloud DeviceCloud Maestro clouds
Device video
Screenshots and last frame
Device logs (Logcat / console)
Timestamped history of every step input and output	Temporal
Protocol messages (offers, requests, responses)
Hashed evidence index per test case
FCAF / conformance report attached to the run
Public scoreboard of pipeline results

Automation and CI:

Capability	Credimi EUDI conformance and interoperability	BrowserStack Sauce Labs LambdaTest Device clouds	Maestro Cloud DeviceCloud Maestro clouds
Run from a pull request (GitHub Action)
Upload a fresh wallet APK per commit
Test a temporary issuer or verifier deployment per commit
Scheduled runs
Device queueing across teams
Live view of the device during a run
Results by API callback or email

CI endpoints exist for each role: run-wallet-apk, run-issuer and run-verifier. Wallet, issuer and verifier teams can each gate their own releases on the same shared scenarios.

Standards and conformance coverage:

Credimi does not replace the reference suites. It runs them for you, side by side, and adds what they lack: real wallets on real devices.

BrowserStack, Sauce Labs, LambdaTest and Maestro Cloud, DeviceCloud cover none of these.

EUDI FCAF: wallet solution, relying party role

617 test cases

in 184 scenarios

OpenID4VCI 1.0 Issuer and wallet
OpenID4VP 1.0, Draft 23, Draft 24 Verifier and wallet
OpenID Foundation conformance suite Integrated
WE BUILD / EWC conformance Integrated
EUDIW verifier tests Integrated
SD-JWT VC and ISO mDoc PID Credential formats
DCQL and Digital Credentials API Scenarios
vLEI Organizational identity

Counts reflect the catalog shipped in Credimi on 20/10/2026. New suites plug into the same pipelines, results pages and evidence model.

FCAF test cases that come with their evidence

The EUDI Functional Conformance Assessment Framework (FCAF) describes what an EUDI wallet solution must do. Credimi runs FCAF test cases inside its pipelines:

every scenario produces named evidence: credential offers, presentation requests, responses, screenshots;
one final validation step judges all catalog test cases against that evidence;
the full report is stored with the run, and each evidence item gets a SHA-256 hash and a pointer into the run's Temporal history.

Sample FCAF report: each test case links to hashed evidence in the run history

Hand the report to an assessor: every claim in it points back to what actually happened.

Keep your devices, network and data

Identity test data is sensitive, and many issuers and verifiers live behind VPNs or in pre-production networks.

Credimi runners connect your own Android phones, emulators, Redroid instances or iOS simulators to the platform.
Runners can be private to your organization or published for others to use.
Each organization runs in its own isolated Temporal namespace.
Credimi is open source (AGPL-3.0), so you can inspect it or host it yourself.

Your own devices, emulators and simulators connect to Credimi through a credimi-runner

Device clouds run on their hardware, in their regions. That suits generic apps. It is a harder conversation when the payload is a Person Identification Data credential.

Test against the real ecosystem, not mocks

Every issuer, verifier, wallet and credential published on the Credimi Hub comes with a live integration. The Hub is an interoperability network, not a test lab.

Open a credential page and get a fresh credential offer as a QR code or deeplink.
Open a verification use case and get a fresh presentation request.
Reuse the same entry, without changes, as a step in your automated pipelines.

The Credimi Hub connects published issuers, wallets and verifiers

Publish on the Hub, and every wallet team in the ecosystem can test against you.

Choose Credimi when:

Start a new test Talk to us

You build an EUDI wallet and need proof it works with real issuers and verifiers, not only on many phones.
You run a credential issuer or verifier and want to know which wallets actually complete your flows.
You prepare for eIDAS 2 / EUDI ARF conformance and need FCAF-aligned evidence.
You are tired of keeping three tools, two scripts and a spreadsheet in sync to answer “does it interoperate?”

Related resources:

Guide EUDI wallet interoperability testing Read guide ↗Guide Test your EUDI wallet against real issuers and verifiers Read guide ↗Guide FCAF conformance testing for EUDI wallets Read guide ↗Atlas EUDI Trust & Conformance Atlas: the Wallet rulebook, mapped Open the atlas ↗Article What is conformance automation Read article ↗Docs Build and run wallet × issuer × verifier pipelines Read docs ↗

Competitor capabilities are summarized from public product pages as of 20/10/2026 and grouped by product category. Product names are trademarks of their owners.