A Drop-In 'Sign In With Your EU Wallet' For Indie And Self-Hosted Apps, Because The eIDAS 2.0 Deadline Is Here And The Only Options Are Heavy Enterprise Stacks
eIDAS 2.0 forces EU relying parties to accept EU Digital Identity Wallet logins (OID4VP) by January 2027, and developers are now asking for it in the tools they actually run. Keycloak, the default self-hosted identity server, has no native support, and the alternatives are enterprise identity platforms. The opening is a Clerk/Auth0-style, low-friction 'accept an EU wallet credential' drop-in for small teams.
Do not try to out-walt.id on the full credential lifecycle. The wedge is purely the verifier/relying-party side ('accept an EU wallet login') packaged for people who currently use Clerk/Auth0/Keycloak, with the regulatory deadline as your built-in urgency.
landscape (3 existing solutions)
The protocol layer exists and the big vendors sell it, but everything is pitched at banks and governments. The gap is a cheap, maintained, indie-friendly verifier (especially a first-class Keycloak path) so a two-person EU SaaS can become wallet-ready before the 2027 deadline without buying an identity platform.