DevCode Identity built its first wave of customers across the Nordics and the UK. There is a reason for that. Identity orchestration in regulated industries depends on deep local knowledge, which ID providers customers actually use, which government registries return what data, which AML lists matter in which jurisdiction, which regulator interprets which directive how. The Nordics and the UK were where DevCode Identity learned that craft.
Today, the platform serves customers operating in regions well beyond those two. As Olivia Englund put it recently: "We’ve gone from having a very strong solution position across the Nordics and UK to now offering a truly global value add to our end-customers and partners." That sentence reads cleanly. The work behind it took the better part of two years.
The hard part of going global is not technical. It is regulatory.
What it took
Identity orchestration is, technically, a runtime that talks to many providers and applies many rules. Adding a new country to that runtime is therefore a question of integrations and rules. In practice, the integrations are the easier part. The harder part is rules. Each jurisdiction defines who needs to be checked, against what, by when, and how the evidence has to be retained. The compliance frameworks across, say, Germany, Brazil, Singapore, and Mexico do not converge. The platform has to absorb all of them and present a coherent surface to the customer compliance team.
The other hard part is partners. No identity orchestration platform owns its own data. The platform routes to providers, ID verification, sanctions and PEP lists, document verification, biometrics. Going global means deepening relationships with new providers in every region, and integrating their APIs at a quality bar that does not embarrass the platform when a compliance officer audits a flagged case.
We have also changed our commercials. The platform now provides services with the most trusted partners in each region, with fallback solutions in place to maximize conversion. In plain language: lean on the best-in-class provider as the primary route, fall back to a secondary route if the primary fails or returns an inconclusive result. That keeps the funnel moving when it would otherwise stall, without giving anything up on the audit defensibility the compliance officer needs at the other end.
What it changes
The most concrete change is for customer compliance teams. A customer operating in twelve countries no longer needs twelve vendor relationships, twelve onboarding flows, and twelve audit trails. They run a single orchestration layer. The local depth lives in the layer. The customer compliance team designs the rules, sees the data, and owns the audit defensibility across every region they operate in, on a single platform.
The change for our partner network is similar in shape. Partners who used to bring us customers with a Nordic or UK footprint now bring us customers operating across regions where we have built coverage. The conversation has changed. The platform stopped being a regional choice and became a global one.
What comes next
More countries, deeper coverage, additional verticals adjacent to the ones we already serve. The compliance-conversion balance does not change, that is the structural thesis of the product. What changes is the geography across which the balance has to hold. The orchestration runtime is the same. The reach is wider every quarter.
— In conversation with Olivia Englund, CEO DevCode Identity