Most service providers think they’re dealing with two unrelated problems right now. One is regulatory: the sovereignty question, CADA, the CLOUD Act, the growing list of contracts you can no longer bid for on a US-parented platform.
The other is commercial: how do you actually innovate fast enough to keep up with what your customers are asking for, and more importantly, how do you turn that innovation into revenue instead of cost.
Treated as two problems, each one gets its own vendor, its own integration project, its own line item. Solved that way, both get slower and more expensive, and neither pays for itself quickly.
But if you treat these problems as one issue, the story could be completely different.
This part is hopefully familiar by now. CADA’s four assurance levels don’t test where your infrastructure sits, they test who owns and controls it. Level 3 and Level 4, the tiers an increasing number of requests for proposals are now written around, structurally exclude any platform with a US parent. That’s not a technical gap you close with a new feature. It’s an ownership question, decided before the product was ever built.
If you’d like the full regulatory picture, the four CADA levels, the CLOUD Act conflict, and what regulated-sector customers are already asking, we cover it in our EU Data Sovereignty guide.
This part gets talked about less, and it’s arguably the more expensive problem. Most service providers need a fast, affordable path from idea to shipped feature to paid feature. Every new capability, like an AI layer, a new model, a compliance add-on, could mean another vendor, another integration, another contract. And even once it’s built, there’s a second problem waiting: billing for it. A feature nobody can invoice for isn’t revenue. It’s a cost centre with good PR.
Put together, that’s an innovation-to-revenue gap. You can build, you can ship. But often times you still can’t get paid for what you shipped, at the speed the market is moving.
Here’s where the two problems turn out to be the same problem in disguise. A service provider stitching together a sovereignty answer from one vendor, an AI layer from another, and a billing and provisioning system from a third isn’t just a slow path forward. Every one of those seams is a place where control, and therefore sovereignty, leaks back out.
The service providers furthest ahead on this aren’t choosing between a sovereignty story and an innovation story. They’re asking a different question: can one vendor hold both, end to end, provisioning through to billing, without a handoff in the middle where ownership gets murky and revenue gets lost.
That’s a narrower list of vendors than these two problems alone suggests. The overlap between them, vendors that are structurally sovereign and can ship and bill for innovation at a reasonable pace, is a genuinely small group.
Sovereignty decisions aren’t annual contract renewals. They’re closer to a ten-year infrastructure bet. No service provider commits to that bet on the strength of a compliance answer alone, and no service provider commits to it on the strength of an AI roadmap alone either. The vendors winning the conversations happening in procurement right now are the ones who can answer both questions in the same meeting, with the same platform.
That’s the real strategic question for the next few years. Not sovereignty on its own, and not innovation on its own, but whether your vendor can hold both without the seams showing.
Want to know more about how Dstny is a sovereign platform provider? Let’s have a a chat.