| SOV-1 Strategic Sovereignty | SEAL-2 | |
| SOV-2 Legal & Jurisdictional Sovereignty | SEAL-2 | |
| SOV-3 Data & AI Sovereignty | SEAL-1 | |
| SOV-4 Operational Sovereignty | SEAL-3 | |
| SOV-5 Supply Chain Sovereignty | SEAL-1 | |
| SOV-6 Technology Sovereignty | SEAL-3 | |
| SOV-7 Security & Compliance Sovereignty | SEAL-1 | |
| SOV-8 Environmental Sustainability | SEAL-1 |
| ID | Factor | Value | Score | SEAL | Conf. | Justification |
|---|---|---|---|---|---|---|
| SOV-1.1 | EU/EEA legal entity control | 4. Entirely within the EU | 125/125 | SEAL-4 | high | eu_entity: TransIP is incorporated in Leiden, Netherlands, part of the Belgian/Dutch team.blue group; the operating legal entity is entirely within the EU -> SOV-1.1 opt4. (src: https://hgcapital.com/insights/hg-invests-in-transip-to-join-forces-with-combell) |
| SOV-1.2 | Change of control risk | 3. Somewhat likely takeover/transfer to non-EU sovereign entity | 63/125 | SEAL-4 | medium | Parent team.blue is majority-controlled by UK PE firm Hg (>35%) with Canada's CPPIB at 20% (valued EUR 4.8bn); as a PE-held asset a sale to a non-EU buyer is somewhat likely -> opt3 (all-seal-4 factor, kept). |
| SOV-1.3 | Control over roadmap | 2. Through 'voice of the customer' public channels | 42/125 | SEAL-2 | low | Commercial provider with no published EU-actor governance body over its roadmap; customer influence only via standard support/feedback channels -> SOV-1.3 opt2. |
| SOV-1.4 | Financial independence from non-EU capital | 3. Balanced mix of EU and non-EU funding | 63/125 | SEAL-4 | medium | Controlling capital is a mix of EU and non-EU: UK PE firm Hg is largest investor and Canadian CPPIB holds 20%, while EU founders/Sofina remain cornerstone investors -> balanced mix opt3 (kept). |
| SOV-1.5 | EU economic contribution | 4. Majority in the EU | 94/125 | SEAL-4 | medium | TransIP operates entirely in the Netherlands with Dutch data centres, staff and customers; clear majority of economic activity in the EU -> opt4 (all-seal-4 factor, kept). |
| SOV-1.6 | Participation in EU strategic programs | 1. No clear participation | 0/125 | SEAL-4 | medium | No public evidence of participation in EU strategic programs (Gaia-X, IPCEI-CIS) by TransIP -> opt1 (all-seal-4 factor, kept). |
| SOV-1.7 | Alignment with EU industrial strategies | 2. Existing action plan | 42/125 | SEAL-4 | low | TransIP markets itself as a sovereign EU alternative to US hyperscalers (CLOUD Act messaging), indicating an action plan aligned with EU digital-sovereignty goals but no measured governance -> opt2 (all-seal-4 factor, kept). |
| SOV-1.8 | Resilience to cut-off | 5. Full autonomy and continuity | 125/125 | SEAL-4 | medium | own_stack: TransIP owns its three self-sufficient Dutch data centres and builds its own systems on an in-house OpenStack control plane; only residual non-EU dependency is commodity chips/hardware, so full autonomy & continuity -> SOV-1.8 opt5 (judgment call 1, own_stack). |
| ID | Factor | Value | Score | SEAL | Conf. | Justification |
|---|---|---|---|---|---|---|
| SOV-2.1 | Primary legal jurisdiction | 3. Exclusively EU law | 167/167 | SEAL-4 | high | TransIP operates exclusively under Dutch/EU law with contracts and data processing governed by Dutch jurisdiction; not a US entity -> exclusively EU law SOV-2.1 opt3. (src: https://www.transip.eu/legal-and-security/certifications/) |
| SOV-2.2 | Extraterritorial laws exposure | 4. Legal structures shielding from foreign law | 125/167 | SEAL-2 | medium | immunity not certified: wholly EU-incorporated with no US presence gives legal structures shielding from foreign law, but UK PE/Canadian-pension control and absence of SecNumCloud/EUCS-High means no verified immunity -> SOV-2.2 opt4 (seal 2 ceiling). |
| SOV-2.3 | Data access pathways for non-EU authorities | 5. Requests always rejected by the provider | 167/167 | SEAL-4 | medium | No foreign_parent in the CLOUD Act/FISA/PRC sense: no US or Chinese subsidiary or parent, so no compelled-access pathway; TransIP would reject foreign extraterritorial demands and respond only to lawful Dutch/EU process -> SOV-2.3 opt5. |
| SOV-2.4 | Export control restrictions | 3. Share of revenues >50% in the EU | 84/167 | SEAL-2 | low | EU offer earns essentially all revenue in the Dutch/EU market with no foreign export-control leverage, but no specifically documented shielding mechanism for the offer -> share of revenues >50% in EU, SOV-2.4 opt3. Normalised to match the other pure-EU Benelux providers (no documented export-control shielding). |
| SOV-2.5 | Origin of IP | 4. Mostly within the EU | 125/167 | SEAL-4 | low | TransIP develops its own control plane and software in-house in the Netherlands on open-source (OpenStack) foundations, so operator IP is mostly EU-originated -> opt4 (all-seal-4 factor, kept). |
| SOV-2.6 | IP holder jurisdiction | 5. Fully under EU law | 167/167 | SEAL-4 | low | IP created and held by TransIP/team.blue sits fully under EU (Dutch/Belgian) law -> SOV-2.6 opt5. |
| ID | Factor | Value | Score | SEAL | Conf. | Justification |
|---|---|---|---|---|---|---|
| SOV-3.1 | Customer control over encryption keys | 3. Shared - provider has override keys | 100/200 | SEAL-2 | low | Standard IaaS/VPS encryption is provider-operated but customers can add their own encryption on top, so key control is shared with provider override rather than provider-only; no customer-exclusive HSM/BYOK -> SOV-3.1 opt3 (shared). Normalised to the common OpenStack-IaaS key-control posture across the pure-EU Benelux providers. |
| SOV-3.2 | Transparent data flows & access logs | 3. Logs exist but not real-time / vendor-controlled | 100/200 | SEAL-2 | low | TransIP provides control-panel and OpenStack logging, but data-access logs are vendor-controlled and not real-time independently auditable -> SOV-3.2 opt3. |
| SOV-3.3 | Secure deletion & proof of erasure | 3. Internal validation per policy, no proof | 100/200 | SEAL-1 | low | Deletion follows internal ISO 27001 policy and replication teardown, but no independent cryptographic proof of erasure is published -> SOV-3.3 opt3. |
| SOV-3.4 | Data location strictly in EU/EEA | 5. Exclusively EU, no third-country fallback | 200/200 | SEAL-4 | high | eu_exclusive: data stored and processed exclusively in Dutch data centres (Amsterdam/Delft AZs), replicated three times across NL sites, no third-country fallback -> SOV-3.4 opt5. (src: https://www.transip.eu/knowledgebase/331-which-iso--certificates-datacenter-possess) |
| SOV-3.5 | AI services sovereignty | 4. EU-led AI, foreign accelerators | 150/200 | SEAL-3 | low | No in-scope first-party AI/GPU service, hence no foreign-AI dependency; per key 'no in-scope AI service' -> SOV-3.5 opt4 (seal 3). Normalised to Fuga/Greenhost (no in-scope AI). |
| ID | Factor | Value | Score | SEAL | Conf. | Justification |
|---|---|---|---|---|---|---|
| SOV-4.1 | Portability & interoperability | 3. Standard documented data export methods | 84/167 | SEAL-4 | medium | Built on OpenStack with S3/Swift-compatible object storage and standard documented export/API methods, enabling portability via widely supported standards -> SOV-4.1 opt3. |
| SOV-4.2 | Ability to operate without foreign dependencies | 5. Entire stack managed by fully EU-based team | 167/167 | SEAL-4 | medium | eu_ops: TransIP maintains and develops its platform in-house with a Netherlands-based team and self-hosts its email rather than relying on US providers; the entire stack is managed by a fully EU-based team -> SOV-4.2 opt5. |
| SOV-4.3 | Skill availability in the EU | 4. All EU staff | 125/167 | SEAL-3 | medium | Engineering and operations staff are all based in the Netherlands; no public evidence of formal security clearances -> all-EU staff SOV-4.3 opt4. |
| SOV-4.4 | Support channels | 4. All support staff in EU | 125/167 | SEAL-3 | medium | Support is delivered from the Netherlands by in-house Dutch teams; no documented security-clearance regime -> all support staff in EU SOV-4.4 opt4. |
| SOV-4.5 | Documentation & knowledge transfer | 3. EU primary with non-EU fallback | 84/167 | SEAL-4 | low | Documentation and knowledge bases are maintained in-house in the EU; some content/tooling may have non-EU fallback but primary repositories are EU -> EU primary with non-EU fallback SOV-4.5 opt3. |
| SOV-4.6 | Subcontractor & supplier jurisdiction | 4. Ability to source alternatives or internalise | 125/167 | SEAL-3 | low | own_stack: TransIP owns its infrastructure and keeps in-house expertise, so it could source alternatives or internalise key functions if a supplier withdrew (hardware vendors are non-EU but substitutable) -> SOV-4.6 opt4. |
| ID | Factor | Value | Score | SEAL | Conf. | Justification |
|---|---|---|---|---|---|---|
| SOV-5.1 | Origin of components (physical parts) | 2. Partial disclosure | 36/143 | SEAL-1 | low | Server components (Dell EMC PowerEdge, Intel/AMD) are sourced from foreign vendors with only partial public disclosure of provenance -> SOV-5.1 opt2. |
| SOV-5.2 | Manufacturing location | 2. Foreign origin, partial disclosure | 36/143 | SEAL-1 | low | Hardware is manufactured outside the EU on foreign designs; TransIP assembles/operates but does not design or build the chips -> SOV-5.2 opt2. |
| SOV-5.3 | Embedded code/firmware provenance | 2. Partial disclosure | 36/143 | SEAL-4 | low | Server firmware/BIOS and chip microcode come from non-EU vendors with at best partial disclosure -> opt2 (all-seal-4 factor, kept). |
| SOV-5.4 | Origin of software | 4. Large majority maintained by EU teams | 107/143 | SEAL-3 | medium | No foreign_core: TransIP's control plane and orchestration are developed/maintained in-house in the EU on open-source (OpenStack) foundations, so the large majority of operating software is EU-maintained -> SOV-5.4 opt4 (seal 3). |
| SOV-5.5 | Software build/release jurisdiction | 4. EU control & execution | 107/143 | SEAL-3 | low | Software build and release for TransIP's own platform are controlled and executed by its EU-based engineering team -> EU control & execution SOV-5.5 opt4. |
| SOV-5.6 | Single point of dependency | 3. Few non-EU in critical services / documented | 72/143 | SEAL-2 | low | Critical dependency on non-EU hardware/chip vendors remains but is documented and substitutable; few non-EU critical dependencies -> SOV-5.6 opt3. |
| SOV-5.7 | Supply chain transparency | 3. Critical suppliers auditable | 72/143 | SEAL-2 | low | Critical suppliers are subject to TransIP security review and contractual agreements, giving auditability of key suppliers but not the full chain -> SOV-5.7 opt3. |
| ID | Factor | Value | Score | SEAL | Conf. | Justification |
|---|---|---|---|---|---|---|
| SOV-6.1 | Interoperability & open interfaces | 4. Standards-based and broadly compatible | 150/200 | SEAL-3 | medium | Platform exposes standards-based, broadly compatible interfaces (OpenStack APIs, S3/Swift), making it interoperable and portable -> SOV-6.1 opt4. |
| SOV-6.2 | Open standards compliance | 4. Policy for most core services | 150/200 | SEAL-3 | medium | Core services adopt open standards (OpenStack, S3 API, standard DNS/email protocols) as a matter of platform design -> policy for most core services SOV-6.2 opt4. |
| SOV-6.3 | Open source availability | 3. Open source, centralised governance | 100/200 | SEAL-3 | medium | No foreign_core: the platform is built on the open-source OpenStack ecosystem (open source, centralised governance for TransIP's own control-plane code) -> SOV-6.3 opt3 (seal 3). |
| SOV-6.4 | Service architecture transparency | 3. Some public insight | 100/200 | SEAL-3 | low | TransIP publishes extensive knowledge-base and architecture documentation (availability zones, replication, network), giving meaningful public insight into its service architecture -> SOV-6.4 opt3. |
| SOV-6.5 | HPC sovereignty | 2. EU-hosted, foreign stack | 50/200 | SEAL-3 | low | No in-scope sovereign HPC; treat as EU-hosted with foreign stack rather than imported black-box -> SOV-6.5 opt2 (seal 3). |
| ID | Factor | Value | Score | SEAL | Conf. | Justification |
|---|---|---|---|---|---|---|
| SOV-7.1 | Security certification (EAL) | 2. EAL1 | 36/143 | SEAL-1 | high | certs: TransIP holds ISO 9001 + ISO 27001 + NEN 7510 only (no SOC2/SecNumCloud/EUCS/C5/ENS-High/Common Criteria EAL); per key ISO 27001 only (NEN 7510 is ISO-27001-derived, ISO 9001 is quality not security) -> EAL1, SOV-7.1 opt2 (seal 1). Normalised to Fuga (same ISO 27001 + NEN 7510 cert basis, no SOC2). (src: https://www.transip.eu/legal-and-security/certifications/) |
| SOV-7.2 | EU regulatory compliance (GDPR/NIS2/DORA) | 4. Partial compliance to most | 107/143 | SEAL-4 | medium | GDPR-compliant Dutch provider holding ISO 27001, ISO 9001 and NEN 7510, indicating partial compliance to most EU regulatory regimes -> opt4 (all-seal-4 factor, kept). |
| SOV-7.3 | EU-based SOC & incident handling | 4. Entire lifecycle by EU teams, EU threat intel | 107/143 | SEAL-3 | low | Security operations and incident handling are run by TransIP's Netherlands-based in-house teams across the lifecycle, though no public ENISA sharing -> entire lifecycle by EU teams SOV-7.3 opt4. |
| SOV-7.4 | Control over security monitoring/logging | 3. Basic monitoring portal | 72/143 | SEAL-1 | low | Customers get monitoring via the control panel/OpenStack but the provider retains primary control of underlying security logging -> basic monitoring portal SOV-7.4 opt3. |
| SOV-7.5 | Disclosure of incidents | 3. Moderate (GDPR/NIS2-aligned) | 72/143 | SEAL-2 | low | As a Dutch provider TransIP follows GDPR/NIS2-aligned breach-notification obligations without a published real-time CSIRT integration -> moderate SOV-7.5 opt3. |
| SOV-7.6 | Maintenance autonomy | 3. Moderate autonomy (notice + testing, except zero-day) | 72/143 | SEAL-4 | low | TransIP maintains in-house maintenance expertise and applies patches/maintenance windows with customer notice, giving moderate maintenance autonomy -> SOV-7.6 opt3 (seal 4). |
| SOV-7.7 | Auditability | 2. Limited independent access | 36/143 | SEAL-1 | low | No audit_rights: auditability is limited to certification-body audits (ISO 27001/NEN 7510) and contractual provisions; no SecNumCloud/sovereign-offer terms granting full independent audit -> SOV-7.7 opt2 (seal 1, sets the floor). (src: https://www.transip.eu/legal-and-security/certifications/) |
| ID | Factor | Value | Score | SEAL | Conf. | Justification |
|---|---|---|---|---|---|---|
| SOV-8.1 | Energy efficiency (PUE) | 3. PUE < 1.5 + roadmap | 125/250 | SEAL-4 | low | TransIP uses modern Dutch data centres (ISO 14001-certified facilities; Amsterdam metro enforces low PUE for new builds), supporting PUE < 1.5 with an efficiency roadmap but no provider-specific verified figure -> SOV-8.1 opt3. (src: https://www.transip.eu/knowledgebase/331-which-iso--certificates-datacenter-possess) |
| SOV-8.2 | Hardware reuse & recycling | 3. Documented program | 125/250 | SEAL-3 | low | As a major Dutch operator within ISO 14001-certified data centres, TransIP runs documented hardware lifecycle/decommissioning and circular practices comparable to its pure-EU Benelux peers -> documented program, SOV-8.2 opt3 (seal 3). Normalised to Leafcloud/Fuga/Greenhost (all opt3); avoids a spurious seal-0 floor on a non-distinguishing factor. |
| SOV-8.3 | Environmental impact reporting | 2. Basic reporting | 63/250 | SEAL-1 | low | Some sustainability communication exists but no detailed audited annual environmental report specific to TransIP -> basic reporting SOV-8.3 opt2. |
| SOV-8.4 | Energy supplies | 2. Only EU energy supplies | 63/250 | SEAL-4 | low | Operations run on Dutch/EU grid power; Dutch data centres typically on EU renewable contracts, but no verified 100% green-energy attestation -> opt2 (all-seal-4 factor, kept). (src: https://www.transip.eu/knowledgebase/331-which-iso--certificates-datacenter-possess) |