Sovereign Digital Cloud · Vendor-Neutral. Always.

We Have Nothing to Sell
Except the Right Answer

SDcloud operates with a structural advantage that no commercial vendor can replicate: we have no proprietary platform, no OEM agreement, and no financial interest in any specific technology. Our only revenue comes from building infrastructure that actually serves you — not our sales quota.

Our Model

Why Vendor Neutrality Is a Structural Property, Not a Promise

Any company can claim to be "vendor neutral." The claim is meaningless unless backed by structural independence — no revenue tied to a specific product, no partnership agreements that create financial bias.

Red Hat earns revenue when you run RHEL. Canonical earns revenue when you run Ubuntu Pro. VMware earns revenue when you run vSphere. These companies employ brilliant engineers — but their commercial incentives are structurally misaligned with your sovereignty.

SDcloud holds no commercial agreements with any software vendor. We earn revenue only from our clients — from the design, deployment, and support of infrastructure built to serve their requirements. When we recommend OpenStack over another platform, or Cilium over Calico, or Ceph over a proprietary SAN, it is because of engineering merit and fit — not because someone pays us a referral fee.

What We Don't Have

  • x
    OEM or Reseller Agreements

    No revenue from recommending or selling any commercial product

  • x
    Vendor Partnership Tiers

    No AWS Partner Network, no Google Cloud Partner, no Microsoft Partner status

  • x
    Proprietary Platform

    No SDcloud-branded cloud management layer, no licenced software stack

What We Do Have

  • Direct client relationships only — 100% of revenue from clients
  • Deep upstream open-source expertise — OpenStack since 2012, Kubernetes since 1.x
  • Knowledge transfer as a first principle — we build your capability, not dependency
Market Context

How We Differ from the Market

This is not a criticism of commercial vendors — they build excellent products. It is an observation about structural incentives.

Aspect Red Hat / IBM Ubuntu / Canonical VMware / Broadcom SDcloud
Revenue model RHEL subscriptions Ubuntu Pro + Juju vSphere licences Client engagements only
Proprietary product RHEL (proprietary patches) Ubuntu Pro / Landscape vSphere / vCenter None
Upstream open-source Fork (restricted access 2023) Mostly upstream Proprietary 100% upstream
Incentive to recommend competitor None None None Full — we pick best tool
Knowledge transfer goal Support subscription renewal Support subscription renewal Licence renewal Your internal capability
CLOUD Act exposure Yes (IBM US) Partial (UK entity) Yes (Broadcom US) No (NL + UAE entities)
How We Work

Engineering Principles

Principles that are non-negotiable in how we design and operate infrastructure.

🔓

Exit-Ready by Design

Every architecture we build starts with the question: "How does the client leave if they need to?" We design for maximum portability from day one.

📚

Documentation as Infrastructure

Undocumented infrastructure creates dependency. Every deployment includes runbooks, architecture decision records, and operational playbooks.

🎓

Capability Transfer

The goal of every engagement is to increase your team's operational capability. We do not build dependency on SDcloud.

Pure Upstream, Always

We use upstream open-source releases — not commercial forks with proprietary layers. OpenStack, Kubernetes, Ceph, and Cilium as published by their communities.

Honest Trade-off Analysis

Every architecture decision has trade-offs. We present them clearly — including trade-offs that might lead you to choose a solution we cannot directly support.

🔒

Security Without Compromise

Security is never traded for convenience or speed. We will slow a project timeline before delivering an architecture with unaddressed security gaps.

Company History

Where We Came From

SDcloud was built from 29+ years of infrastructure engineering experience — starting before virtualisation, before "cloud" was a product category, and before open-source was considered enterprise-grade.

Our founder worked through the full arc of IT infrastructure: bare-metal UNIX and network administration at national-scale ISPs, building and running hosting companies, open-source virtualisation with KVM, multi-country CloudStack and OpenStack deployments, public clouds with 10,000+ tenants, private clouds for telcos, defence-grade air-gapped environments, and cloud product ownership — defining IaaS and PaaS products end-to-end from customer problems to roadmap, PRDs, and delivery.

SDcloud FZ-LLC is incorporated in the Ras Al Khaimah Economic Zone (RAKEZ), United Arab Emirates. CloudToko B.V. has been serving European clients from The Hague since 2017.

1997 - 2004

ISP, Hosting & Data Centres

2005 - 2012

Open-Source Virtualisation & Telecoms

2012 - 2014

CloudStack & Ceph

2014 - 2022

OpenStack, Ceph & Kubernetes

2022 - 2025

Kubernetes, Cilium & BGP

2025 - Present

Sovereign Cloud & AI

Where We Are

Two Jurisdictions. One Engineering Team.

🇳🇱

CloudToko B.V.

The Hague, Netherlands

GDPR NIS2 EU Law
🇦🇪

SDcloud FZ-LLC

Ras Al Khaimah, United Arab Emirates

UAE PDPL GCC

Talk to Engineers, Not Account Managers

When you contact SDcloud, you speak directly with infrastructure engineers who have deployed the technology you're asking about. No pre-sales gatekeeping.