Lissi

Name: Lissi
Brand: Lissi Designs

AI Native

We enable issuers and verifiers to interact with all 🇪🇺 📲 EU Identity Wallets according to eIDAS 2.0.

Est 2023|12 Ref Customers

LinkedIn 5K|Web traffic 3K|FTEs 17|HQ Frankfurt, Germany

Published Oct 15, 2026

01Common complaints

- If a fully managed SaaS with minimal operational overhead is required - Lissi’s customer-hosted deployment model shifts operational responsibility to the customer. - If engineering or IAM capacity is limited - Organizations that cannot support OAuth2 server integration, database operations, secrets/HSM integration, and ongoing upgrades should consider a more managed platform. - If procurement requires publicly available third-party certifications and audit artifacts - Organizations that require SOC 2/ISO certificates to be publicly downloadable without an NDA or vendor security review may not find sufficient public artifacts. - If abundant third-party review validation is a requirement - With limited presence on TrustRadius, G2, and other review platforms, organizations seeking broad peer validation may choose alternative vendors with larger review footprints. - If default vendor marketing/PR usage of customer name/logo is unacceptable - Lissi’s cloud terms include permission for marketing usage of customer names/logos; organizations with strict controls on such usage should plan to negotiate terms. - Current limitations acknowledged by vendor (explicit) - Lissi wallet documentation notes that an older variant (FUNKE version) is no longer supported, indicating historical product iteration and deprecation. - Ecosystem risks (not Lissi-specific but impacting product value) - Public discourse highlights concerns about privacy properties, security of reference implementations, and platform dependencies (e.g., device integrity checks by major platform vendors). These factors may increase stakeholder resistance and lengthen procurement cycles. - Roadmap/feature availability - No detailed public roadmap with delivery dates was located in accessible materials. - Integration constraints - Requires an external OAuth 2.0 authorization server, integrates with PostgreSQL, and relies on customer-managed infrastructure.

Deal disqualifiers (what makes a poor fit)

Requirement for abundant third-party reviews, transparent pricing, or self-serve adoption.
Inability to operate customer-hosted software and preference for pure SaaS with minimal operational responsibilities.
Requirement for publicly available certifications and audit artifacts without engaging the vendor security review process.

02Why they buy

- Validated by available evidence (with caveats) - Deployment model: containerized, customer-perimeter execution (vendor-asserted) supports customers that require on-prem or private-cloud deployments. - Ecosystem participation: Lissi components appear in EWC deliverables and pilot documentation, indicating involvement in interoperability testing. - Vendor-asserted claims that require validation - Contractual claims of eIDAS 2.0 compliance should be validated with contractual and certification artifacts. - Vendor assertion of a single API to multiple certified EUDI wallets should be validated with an interoperability matrix and test evidence. - Vendor performance claims (e.g., high issuance/verification throughput) should be validated with independent benchmarks. - Areas where competitors have explicit advantages - Validated ID: public compliance/certification claims are more visible in public materials. - iGrant.io: more extensive public documentation and demonstrable pilot narratives in publicly available materials.

03Field reports

Review platform coverage reality check

- TrustRadius: product page present but no third-party reviews visible. - Gartner Peer Insights: no listing or reviews located in accessible search results (access may be gated). - G2: no product reviews found in accessible search results. - Capterra: no listing surfaced in accessible search results. - Practical consequence - There is insufficient third-party review volume on standard B2B review sites to form a reliable independent voice-of-customer summary.

Available vendor-published testimonials (treated as vendor-provided marketing evidence)

- Lissi’s website includes customer/partner quotes. Example: - Philipp Ottlinger (Sign8): “The fact that the whole thing works within a few hours speaks volumes for the excellent solution, documentation and support.” - Additional vendor-published statements reference partnerships and integrations with Ping Identity and ServiceNow and include brief statements from individuals at ADACOM, Intesa, and Mastercard regarding collaboration. - Critical note - These items are vendor-published and were not independently verified; context such as scope, success criteria, and contractual relationships is not fully disclosed in the sources reviewed.

Community / social signals (limited product-specific feedback)

Direct community discussions specifically about the Lissi Connector are not prominent on Reddit or Hacker News.
Hacker News contains broader discussion threads about the EU Digital Identity Wallet concept (privacy, platform integrity concerns), which indirectly affect buyer risk perception.

Representative community concerns affecting the market

Privacy and platform dependency concerns recur in public discussions about EUDI wallets (e.g., tracking concerns, device-integrity dependencies). These criticisms primarily target the broader EUDI program and reference implementations rather than Lissi specifically, but they influence procurement scrutiny and public-sector acceptance.

Public case studies for Lissi

Lissi’s site primarily provides testimonials and partnership claims. Detailed, independently validated case studies with methodology, SLAs, and incident histories were not found in the reviewed sources.

Ecosystem pilot documentation mentioning Lissi (pilot and consortium artifacts)

- EWC (European Wallet Consortium) publications list Lissi components in deliverables and interoperability reports, indicating participation in pilot contexts. - For example, an EWC interoperability report excerpt documents wallet solutions (including Lissi ID) receiving and storing PID credentials and accepting SD-JWT VC and ISO mdoc formats in specific test scenarios. - Critical view - Pilot participation provides interoperability evidence but does not equate to production rollouts with commercial SLAs and long-term maintenance commitments.

Methodology gaps

Vendor performance and compliance claims are not accompanied by public third-party audits, certification artifacts, or transparent test-suite outputs.

04Best fit

Company sizes

Likely fit: mid-market to enterprise organizations with:
- Dedicated security and compliance teams
- DevOps maturity to run containerized software in regulated environments
- Identity/IAM architecture capacity
Indicative: organizations ranging from mid-market to very large enterprises (inferred from regulated enterprise/public-sector focus rather than explicit vendor constraints).

Industries and verticals where adoption is strongest

Financial services (banks, insurance)
Public sector / authorities
Identity providers (IDV), IAM vendors, QTSP ecosystem partners

Roles and personas

Decision makers
- CIO / CISO
- Head of Identity / IAM director
- Digital channels / onboarding leadership in banking
- Compliance / risk leadership (eIDAS, PSD2)
Implementers
- IAM engineers / solution architects
- Backend platform engineers
- Security engineering / PKI teams

Pain points and challenges the product addresses

Need to support EUDI wallet flows without maintaining an internal team to track ARF/implementing acts, protocol profiles (OIDC4VP/OID4VCI), credential formats, and trust models.
Desire to keep keys and credential data within the customer perimeter to limit third-party processing exposure.

Qualification criteria (what makes a good fit)

Organization must accept EUDI wallets under eIDAS 2.0 and require a connector layer.
Organization prefers on-prem/private cloud deployment and can operate containerized software.
Organization is prepared to engage in pilot testing and iterative standards updates.

05The pitch

What the product does (core value proposition in objective terms)

- Lissi is a German B2B software provider focused on enabling organizations (banks, public authorities, identity vendors, QTSPs, integrators) to interact with European Digital Identity Wallets (EUDI Wallets) under eIDAS 2.0. - Primary product: Lissi EUDI Wallet Connector (also called “Lissi Connector”), an API/software component that supports: - User identification via PID (Person Identification Data) - Issuance & verification of EAAs/QEAAs (electronic attestations) - Strong Customer Authentication (SCA) flows aligned with PSD2/PSD3 - Qualified Electronic Signature (QES) authorization flows (operates with QTSP partners) - Interoperability across certified EUDI wallets via a single integration layer (vendor-asserted) - Additional offering: Lissi maintains a Lissi ID-Wallet (holder wallet app) with public documentation and a paid/professional Lissi Wallet Pro variant.

Target market and market positioning

- Target users - Regulated enterprises and public sector entities that must accept and use EUDI Wallets for identity, onboarding, authentication, and signing use cases. - Intermediaries (system integrators, IDV platforms, QTSPs) that need multi-tenant connector infrastructure to serve many downstream clients. - Positioning themes (vendor-asserted) - Vendor describes the product as production-ready rather than a prototype. - Emphasis on on-prem/containerized deployment and a deployment model intended to reduce certain data-processing exposure because Lissi positions itself as a software provider rather than a processor of end-user personal data.

Get a comprehensive analysis of Lissi including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →