Service · Software development

Custom CIAM platform development.

A Customer Identity & Access Management platform that fits your customer flows, your brand and your integrations. For B2C brands, B2B SaaS, banks and insurers who want to go beyond what Auth0 or Microsoft Entra External ID offer out of the box.

CIAMKeycloakNL Wallet & EUDIiDIN & DigiDOpenID Connect

CIAM is not IAM.

IAM (Identity & Access Management) manages identities within your organisation: employees, Active Directory, SSO to Microsoft 365 and Salesforce. CIAM manages identities outside it: customers, citizens, partners. The numbers are many times larger, the UX requirements far stricter, the regulations work differently, and your brand is part of the picture. A customer who forgets their password is a lost conversion, not an internal helpdesk ticket. A 401 error during checkout costs you revenue; a 401 on the employee VPN costs you a Slack message.

Today the term Customer Identity covers very different worlds: a loyalty account for a retailer, a customer portal for an insurer with BSN integration, a SaaS product that lets enterprise customers federate via SAML, a media service with a paywall and subscriptions, a fintech app with strong customer authentication. What they have in common: identity is not an internal department, it is a product feature with a direct impact on conversion, retention and compliance.

Since 2015 we have been building custom CIAM platforms for organisations where standard SaaS CIAM (Auth0, ForgeRock, Microsoft Entra External ID, Amazon Cognito, FusionAuth, Ping Identity) doesn't go far enough. Often based on Keycloak with a custom UX layer, sometimes entirely from scratch. Always integrated into your existing architecture and, where relevant, connected to Dutch identities such as iDIN, DigiD, eHerkenning or the NL Wallet.

Three types of CIAM project.

The scope of a CIAM project depends on the type of identity, the number of connected systems and the regulatory framework. These are three patterns we work within; in an initial conversation we determine which one fits your situation.

Compact project · Keycloak foundation with custom UX

B2C CIAM for brands and retailers

A customer account for your brand: registration, login (password, social login, magic link, passkey/WebAuthn), self-service profile and order history. Integrated with your CDP, e-commerce platform and marketing tooling. Customers see your brand, not a generic Auth0 popup. Progressive profiling spreads data collection over multiple visits so you don't ask for everything at registration, which is better for conversion and better for compliance.

Social loginPasskey/WebAuthnProgressive profilingLoyalty integration
Mid-sized project · multi-tenant architecture

B2B SaaS CIAM with federated identity

Organisation accounts with multiple users, roles and permissions. Customers bring their own identity provider (Azure AD, Okta, Google Workspace) via SAML or OIDC. Self-service onboarding for new tenants, automatic provisioning via SCIM, and an admin console where your customer success team can resolve tenant issues without developer involvement. Suitable for SaaS vendors growing towards enterprise customers, comparable to our vendor portal builds, but for your end customers.

Multi-tenantSAML/OIDC federationSCIM provisioningRBAC + ABAC
Larger project · regulated industries

CIAM for banks, insurers and healthcare

High-assurance identity for customer portals in regulated sectors. iDIN, DigiD and eHerkenning for strong verification, BSN integration where legally permitted, KYC integration, and audit logging compliant with DNB/AFM requirements and NEN 7510. Prepared for the EUDI Wallet and eIDAS 2.0 with OpenID for Verifiable Presentations (OpenID4VP) and SD-JWT credentials. Step-up authentication for high-risk transactions: a customer signs in with a light login to view information, but must re-identify via iDIN to make a change.

iDIN & DigiDEUDI WalletKYC/AMLRisk-based auth

The features that make up a CIAM platform.

A complete CIAM platform combines authentication, authorisation, account management, consent and risk detection. We don't implement them all blindly: for each project we choose which are needed now and which can wait.

Authentication

Login methods

Password, social login (Google, Apple, Facebook, LinkedIn, Microsoft), email magic link, SMS OTP, passkey/WebAuthn, hardware keys (YubiKey, FIDO2), iDIN, DigiD, eHerkenning. We select which methods to offer for each user segment.

MFA

Multi-factor authentication

TOTP via authenticator apps, SMS OTP, push notifications, biometrics via mobile SDK, hardware keys. Risk-based: MFA is enforced when signals look suspicious, not on every login, as that hurts conversion without improving security.

Account management

Self-service for your customers

Profile editing, password reset, MFA settings, linked devices, revoking sessions, deleting an account (GDPR right), exporting data (data portability). All in your branding, without your customer service team handling every request manually.

Authorisation

RBAC, ABAC and relationships

Role-based access control for simple role models. Attribute-based for situations where context decides (location, time, transaction amount). Relationship-based for B2B tenants where permissions follow organisation membership. Built on Open Policy Agent or your own policy engine.

Consent & privacy

Consent management under GDPR

Granular consent per processing purpose, version control of privacy statements (who accepted what and when), cookie consent integration, channel preferences. APIs for access, rectification and erasure requests so your DPO doesn't have to look them up manually in databases.

Risk detection

Fraud signals and suspicious login

Impossible-travel detection, device fingerprinting, velocity checks, IP reputation, behaviour analysis. Can be linked to your existing fraud engine or to providers such as Sift, Castle or Auth0 Adaptive MFA. Signals lead to step-up or blocking, not automatically to lockout.

What you get at the end.

A production-ready CIAM platform that connects to your applications, plus the operational foundation to manage it yourself or have us manage it.

  • The CIAM platform itselfProduction and staging environments, running in your cloud (GCP/AWS/Azure) or with us. Containerised via Docker, monitored and auto-scaling where needed.
  • Branded login and account UXLogin, registration, MFA setup, account management and password reset in your branding, with no generic vendor pop-ups.
  • SDKs and integration librariesClient libraries for your web, mobile and backend applications. OAuth2/OIDC-compatible so external tools connect easily.
  • Admin console and documentationFor your IT team: manage roles, export user data (GDPR requests), review the audit log, configure federation.
  • Pen test report and security baselineExternal pen test in the final sprint, plus a baseline configuration for rate limiting, bot protection and suspicious-login detection.
  • Support contract (optional)Monitoring, security patches, ongoing development. Fixed monthly price, with four response-time levels matched to how critical your login flow is.
Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

When custom CIAM makes sense.

We actively recommend standard CIAM platforms (Auth0, Microsoft Entra External ID, Amazon Cognito, FusionAuth, Ping Identity) ourselves where they fit. Custom makes sense in these patterns.

Dutch identity

iDIN, DigiD, eHerkenning, NL Wallet

You need strong customer verification with Dutch identity sources. Standard SaaS CIAM often doesn't support these, or only superficially. Custom lets you integrate iDIN or DigiD onboarding deeply into your flow.

EUDI & eIDAS 2.0

Ready for the EU Digital Identity Wallet

With eIDAS 2.0 (mandatory for member states from 2026), the EUDI Wallet is on its way. Verifiable credentials, OpenID4VP and SD-JWT are standards that most off-the-shelf CIAM platforms aren't ready for yet.

Sector-specific flows

Banking, insurance, healthcare

Risk-based authentication connected to your fraud engine, BSN (citizen service number) processing under a legal basis, AFM/DNB audit requirements, NEN 7510 for healthcare. Standard CIAM covers 80%, and the last 20% costs more than a custom solution. Often combined with KYC and AML compliance software in the same stack.

Deep integration with your core systems

Core banking, EHR, ERP, CDP

The identity layer has to talk bi-directionally with your core systems: profile changes, consent updates, segmentation. With standard CIAM you pay per API call and remain exposed to rate limits.

White-label CIAM

Identity-as-a-service for your partners

You provide a platform of your own, and your partners want to be able to bring their customers onto it. Multi-tenant and white-label, with each tenant getting its own branding, its own federation config and its own consent regime. Related to our work on an employee portal and the broader vendor portal work, but focused on customer identities.

Scale or vendor lock-in

Costs rise, control declines

You grow to millions of identities and the vendor's pricing scales with you, often faster than your revenue. Or you no longer want to depend on a single supplier for such a critical component. Custom Keycloak or a from-scratch build gives that control back.

How a CIAM project works.

A CIAM build isn't a feature you slot in alongside existing work. It touches every application that talks to customers. We work in five phases: first we understand, then we scope, then we build, then we migrate, then we manage.

1

Introduction and architecture scan

A conversation in which we map your current identity situation: which applications need to connect, which identity providers are in use, where customer data lives today, and which compliance requirements apply. No sales pitch, just sharp questions.

2

Scope and threat model

A workshop with your team plus interviews with security and compliance. We deliver a threat model, a data flow diagram and a concrete scope: which flows go into the MVP, which come later, and which a standard CIAM product can handle better after all. We often cut things here that don't need to be built.

3

Building in sprints

A working build on staging every two weeks. We usually start with the most painful flow (registration + login + MFA), so you can test for real early on. An external pen test runs in parallel during the final sprints, not as a finishing step.

4

Migration and rollout

Your existing user base is migrated with zero disruption: hashes are carried over, and password rotation happens at the next login rather than as a bulk reset. We roll out in phases per segment or brand.

5

Management and further development

Ongoing management after go-live: security patches, monitoring, dependency updates, audit log review. Plus continued development: adding new identity sources (NL Wallet is on its way), extending MFA methods, onboarding B2B tenants.

Frequently asked questions.

What clients usually want to know before we start.

What is the difference between CIAM and IAM?
IAM (Identity & Access Management) is about employees within your organisation, such as Active Directory, Okta Workforce, Microsoft Entra ID and SSO to internal SaaS tools. CIAM (Customer Identity & Access Management) is about identities outside your organisation: customers, citizens, partners. The volumes are larger, the UX requirements stricter, your brand comes into play, and regulation (GDPR, sector-specific rules) works differently. Tools that excel at IAM (Okta Workforce, Microsoft Entra ID) aren't automatically suited to CIAM, and vice versa.
Do you replace Auth0, Okta or Microsoft Entra External ID?
For standard B2C or B2B flows we often recommend those platforms. Auth0, ForgeRock, Microsoft Entra External ID, Amazon Cognito, Ping Identity, FusionAuth and SuperTokens are mature products. We come in once you hit their limits: industry-specific flows (banking, healthcare with BSN), Dutch identities (iDIN, DigiD), EUDI Wallet, white-label CIAM for partners, or deep integration with core systems that standard CIAM rate limits can't handle.
Do you work with Keycloak?
Yes, often. Keycloak is open source, OpenID Connect-compatible, scalable, and gives you full control over the data layer. We usually build a custom UX layer on top of Keycloak instead of using the bundled theme, which rarely meets modern CIAM requirements. For B2B multi-tenant we configure Keycloak realms strategically; for B2C we often build a dedicated account front end that talks to Keycloak via OIDC. We only build fully from scratch if Keycloak really doesn't fit.
How do you handle NL Wallet, iDIN and EUDI?
We integrate iDIN via the Currence integration, with the right step-up flow so you don't force a bank login on every sign-in. DigiD and eHerkenning require a Logius connection via a routing provider. We handle the technical part; your organisation must apply for the legal connection itself. For EUDI and the NL Wallet we build on OpenID for Verifiable Presentations (OpenID4VP) and SD-JWT credentials. The ecosystem moves quickly; we build architecture that moves with it.
What about GDPR, consent and data sovereignty?
A CIAM platform is a GDPR focal point: you process personal data, receive access, rectification and erasure requests, and must keep a consent register. We build consent management in as standard, including version control of privacy statements, granular consent per purpose, and APIs for data portability. We handle EU/NL data residency through the cloud choice (GCP europe-west, AWS eu-central, Azure West Europe or a Dutch hosting provider). A DPIA is included in the scoping phase.
What determines the cost?
The heaviest factors are: the number and type of identity providers (social login is light, iDIN or DigiD takes more work), the number of connecting applications (every SDK integration takes time), the regulatory framework (banking and healthcare require audit trails and pen tests that aren't needed elsewhere), migration of an existing user base, and the branding and UX requirements. After the architecture scan we give you a well-founded range, not a round figure over the phone.
Can you connect to our existing architecture?
Almost always. A CIAM platform communicates through standards: OIDC, OAuth2, SAML, SCIM, webhooks. We have experience connecting to core banking systems, EHRs, ERPs (SAP, Microsoft Dynamics), CDPs (Segment, Tealium, mParticle), e-commerce platforms (Magento, Shopify Plus, commercetools) and customer service tooling. For specific integration questions we often work together with our smart API integrations page.
What if we want to switch later?
Standards are your safety net. We build on OIDC, OAuth2 and SCIM so that applications connected to your CIAM can move to another platform without a rebuild. You can export your user data at any time via the admin console. With Keycloak builds, you receive the configuration as infrastructure as code. No lock-in on our code is an explicit design goal.
How do you handle migrating an existing user base?
We carry over password hashes in their original algorithm (bcrypt, argon2, scrypt, even legacy variants) and upgrade them lazily: on the next successful login, the hash is automatically recalculated in the newer algorithm. This avoids the painful "everyone must reset their password" email that typically sends 20–40% of your user base dormant. For social identities, we create account-linking records so customers can keep logging in with their existing method.
Do you only do B2C, or B2B CIAM as well?
Both. B2C CIAM (customer accounts, social login, paywall) and B2B CIAM (organisation tenants, federated identity via SAML, SCIM provisioning) share overlapping foundations but raise separate challenges. We often build platforms that need to support both: a retailer with a loyalty brand and a business-to-business arm; an insurer with private customers and authorised brokers; a media service with consumer subscribers and licensing customers. We handle the multi-tenant architecture in the foundation.

Talk to us about your CIAM platform.

A no-obligation introductory call of half an hour. We listen to your customer flow and the identity sources you're tied to, and give concrete direction, even if the outcome is that a standard CIAM platform suits you better.

Edit content