Most platforms use 'sovereign' as a marketing word. Here is what it means structurally on UBetOn — and why it matters for an operator who has to answer to a regulator.
Bare-metal servers per operator. No co-tenancy. No shared databases. No 'noisy neighbor' performance risks. If we provision you a cluster, it's yours alone.
A sovereign, non-US cloud. Your data lives beyond the reach of the CLOUD Act and FISA 702. Your regulator can inspect the actual jurisdiction your data sits in, disclosed to your DPO.
Sovereign AI means your machine-learning models train on your data, period. Not yours-plus-everyone-else's. Not a base model fine-tuned on you. Yours.
Where your own obligations require data to stay in a particular country, we deploy there with local replication. The residency model is configurable per deployment — you tell us what your regulator expects.
We publish the list of every third-party service in the hosting chain. No hidden subprocessors. Your DPO and your regulator can verify it independently.
When you leave, you get a full export of your data, your trained ML weights, and your CMS content in open formats. Sovereign means yours to take with you.
No mystery boxes. The list below is exhaustive and audit-ready.
Dedicated bare-metal servers, dedicated managed databases, dedicated object storage. Fully non-US, with redundancy across two sovereign datacenters. Exact locations disclosed to your DPO and regulator.
DNS, TLS termination, and edge caching from the same provider, same jurisdiction. No Cloudflare. No Fastly. No US-parented edge in the chain.
Transactional and marketing email via a sovereign, non-US provider. SMS via local in-jurisdiction providers wherever supported; an external gateway only as a last-resort fallback with player consent.
Logs and metrics never leave the operator's dedicated environment. No third-party SaaS observability in the chain.
DPIA, hosting-chain CSV, processor list, and the architecture diagram your regulator will ask for — in one PDF.