Yameveo designs and implements Customer Identity and Access Management (CIAM) systems for enterprises across Europe: single sign-on (SSO), OAuth2, OIDC, and multi-tenant identity architectures. We cover both the protocol layer and the UX work that makes identity usable at scale. Our founder has worked extensively on CIAM implementations and platform architecture for enterprise clients, including seven years with SAP Customer Data Cloud across Gigya, SAP, KPS and Roche. We also lead a work package on the EU VANTAGE project, and that AI and cybersecurity background lets us extend standard CIAM deployments with identity threat detection and assess how ready they are for newer standards such as EUDI wallet credentials.
What does a CIAM implementation from Yameveo include?
A Yameveo CIAM implementation covers the full identity stack: single sign-on (SSO), OAuth2 and OIDC flows, and multi-tenant identity architecture, plus the login and registration UX that decides whether users actually adopt the system. We work at the protocol layer (authorization flows, token handling, session management, federation between identity providers) and on the experience layer, because an identity system that is technically correct but frustrates users at sign-up quietly costs you conversions. We build on the platform that fits your stack and do not resell a single vendor. If you already run a CIAM platform such as SAP Customer Data Cloud, Auth0, or Okta, we integrate with it and extend it instead of forcing a rebuild.
Can you add threat detection to an existing CIAM platform like Auth0, Okta or SAP Customer Data Cloud?
Yes. CIAM platforms generally ship without native anomaly detection. Yameveo can add a passive, webhook-based monitoring layer that spots impossible travel, credential stuffing, and account-takeover patterns without touching the critical login path. The monitoring runs alongside authentication, not inline, so it adds no latency or risk to the flow your users depend on to sign in. This comes straight from our cybersecurity work: on the VANTAGE project we lead the work package covering AI-driven vulnerability assessment and incident investigation, and the same detection thinking applies to identity signals.
How ready is your CIAM for EUDI wallet credentials?
Under eIDAS 2.0 (Regulation (EU) 2024/1183), every member state must offer at least one European Digital Identity (EUDI) wallet by the end of 2026. By the end of 2027, private companies in regulated sectors such as banking, telecommunications, transport and health must also accept the wallet when a user chooses it, wherever they are required to use strong user authentication for online identification. Micro and small enterprises are exempt.
Our EUDI wallet readiness assessment starts from the CIAM you already run, whether that is SAP Customer Data Cloud, Auth0, Okta or another platform. We look at what changes in your registration and login flows when they have to accept a wallet credential, and where the verification step fits: the wallet answers an OpenID for Verifiable Presentations (OpenID4VP) request, and the identity data arrives as an SD-JWT VC or ISO mdoc credential, with W3C Verifiable Credentials as an optional format in the EU reference framework.
Your IdP keeps sessions and user records, and the wallet supplies the proof of identity. The assessment ends with what to do now to be ready for 2027: which user journeys need a wallet option, how a wallet identity links to an existing account, and what to test once your member state’s wallet is available.
How do you work with our existing identity provider and engineering team?
We integrate with the identity provider and codebase you already run and work alongside your engineering team, without replacing your stack. Our founder spent years as a technical lead with distributed international teams, on architecture reviews and critical production issues. That is the experience we bring when we join an existing team, review an existing CIAM setup, and either own the identity workstream or advise on it. Engagements range from full CIAM implementation to fractional CTO and architecture advisory, depending on what your team needs.
If you run SAP Customer Data Cloud and need visibility into identity activity, see Yameveo Analytics for CIAM, our analytics layer for SAP CDC.
Frequently asked questions
Do you resell a CIAM product, or are you independent?
We are independent. We design and implement CIAM on the platform that fits your requirements and stack, working at the protocol layer (SSO, OAuth2, OIDC) instead of pushing a single vendor. Where you already run a CIAM platform, we integrate with it and extend it.
Do you work with companies outside Bulgaria?
Yes. Yameveo is based in Burgas, Bulgaria, and our founder has worked on CIAM for enterprise clients across Europe. We work with distributed teams and are set up to engage remotely across the EU.
Do you handle both single sign-on and multi-tenant setups?
Yes. Our CIAM service covers SSO, OAuth2 and OIDC flows as well as multi-tenant identity architectures, so we can support a single application or a platform serving many separate customer organisations from one identity layer.
Can you help us prepare for EUDI wallet and eIDAS 2.0?
Yes, with an EUDI wallet readiness assessment of your current identity provider. It covers what changes in your registration and login flows, where wallet verification fits (OpenID4VP), what stays with your IdP, and what to do now to be ready for the 2027 acceptance deadline.
Planning a CIAM implementation, adding threat detection to your existing identity platform, or checking your EUDI wallet readiness? Discuss your CIAM project →