Interesting that the reasoning is reportedly about control and exit costs, not just price. That matches what I keep hearing from people who run large deployments: the lock-in tax shows up years later, when you discover your workflows, integrations, and data shapes have all quietly molded themselves around one vendor’s APIs. A tax authority is one of the few orgs with the patience and staff to actually pull off a sovereign-stack migration, so this will be a useful data point either way. Hope someone documents the migration honestly, because the failure modes would be more instructive than the press release.
Interesting that the reasoning is reportedly about control and exit costs, not just price. That matches what I keep hearing from people who run large deployments: the lock-in tax shows up years later, when you discover your workflows, integrations, and data shapes have all quietly molded themselves around one vendor’s APIs. A tax authority is one of the few orgs with the patience and staff to actually pull off a sovereign-stack migration, so this will be a useful data point either way. Hope someone documents the migration honestly, because the failure modes would be more instructive than the press release.