Run the Thalassa Cloud platform on dedicated servers — in your building, in a data center you choose, or dedicated in the Netherlands. Self-managed, co-managed, or fully managed. Your teams keep the APIs, Terraform, Kubernetes, and services they already use — without sharing tenancy or sending the control plane abroad.
From four physical servers — on-prem, in a data center you choose, or stretched across availability zones.
IaaS, Kubernetes, databases, KMS, and IAM — the same stack as Thalassa Public Cloud.
Built and supported in the Netherlands. No foreign management plane, no hyperscaler tether.
Thalassa Private Cloud is a dedicated installation of our platform. It is not a hypervisor with a portal, and it is not a US public cloud with a rack in your building. Compute, storage, networking, and the control plane run on hardware reserved for you — on-prem, in a facility you trust, or in Dutch data centers under Dutch and EU law.
Hardware can be purchased, leased, or supplied by you if it meets our technical requirements. Operate it yourself (self-managed license and updates) or with us. You can offer the same cloud to internal teams — or to your own customers — with isolation that a shared public cloud cannot give you.
Physical security, network topology, and data residency stay with you. No data leaves the sites you choose unless you attach an external network on purpose.
Console, CLI, APIs, and Terraform / OpenTofu. Platform teams do not relearn a private-cloud stack. New public-cloud services are intended to land on Private Cloud as the platform grows.
License and updates as the baseline. You operate, we co-operate, or we run platform operations. Service management, NOC, and 24/7 cover are optional — they are not required for a four-node start.
The services your teams already automate on Thalassa Public Cloud, on dedicated metal.
Virtual machines, managed Kubernetes, and a private container registry — including node pools and workload identities.
KubernetesVPCs, security groups, firewalls, load balancers, NAT, DNS, and VPN. Dedicated physical network, consumed through the same VPC model and APIs. Own IP prefixes are supported.
VPCsBlock, object, and file storage, snapshots, and managed PostgreSQL with backups and high availability.
PostgreSQLIAM, KMS, and Secrets Manager on the local control plane. Keys and secrets stay inside the Private Cloud boundary.
KMSManaged Prometheus and Managed Logging (Loki). Metrics and logs remain on the dedicated platform.
Not only public internet. Dedicated connections land in the VPC model so your teams consume them through API and Terraform.
Networking modelDigital sovereignty is not isolation. It is choosing where data lives, who operates the control plane, and which law applies when something goes wrong.
Hyperscaler “on-prem” products still tether management to a US public cloud. A hypervisor gives you VMs, not a cloud. Thalassa Private Cloud keeps the control plane with the workload: European software, a location you choose, open standards, and an exit path that does not depend on a foreign vendor.
Read the sovereignty articleDeveloped, supported, and operated from the Netherlands — for teams that cannot outsource jurisdiction.
The platform is developed and supported in the EU. Azure Stack and AWS Outposts still depend on a US public cloud for management. This one does not.
IAM, KMS, secrets, and logging are part of the platform. You set residency and access policy on infrastructure you can point to in a data-processing agreement.
On-prem, a data center you trust, or Dutch facilities. Stretch across sites when you need more than one availability zone. External networks are attached only when you design them in.
Organisations that need a modern cloud without giving up the perimeter.
Public-sector organisations that need data residency, compliance, and a dedicated security boundary.
Fixed residency, auditability, and a dedicated security boundary for regulated workloads.
A white-labelable platform to sell cloud services from a location you choose, with the same APIs your customers expect.
Edge or on-site capacity with Kubernetes, networking, and storage under your operational control.
From design to a running platform on the sites you choose. The same team that builds the platform delivers the software — and, if you want, the on-site installation. Self-managed: you install; we supply the platform, updates, and support.
We translate your environment into a platform design: number of sites, physical servers, network, and identity. Setup follows that design, not the other way around.
Control plane, platform services, IAM, and monitoring are configured. You get the same console, APIs, and Terraform provider as on public cloud.
Self-managed: your team installs against our requirements. Or engineers visit each site: physical preparation, cabling and checks, provisioning, and commissioning. Hardware, rack space, and network follow the chosen location.
Monitoring, administration, and operational handover. Updates then follow the same release train as public cloud. Extra integrations or hardening are delivered as engineering alongside the standard setup.
A comparison of private cloud alternatives for European organisations.
| Feature | VMware vSphere | Azure Stack | AWS Outposts | Proxmox VE | OpenStack | Thalassa Private Cloud |
|---|---|---|---|---|---|---|
| Sovereignty & Compliance | ||||||
European Development | EU Company | Open Source | ||||
GDPR Compliance | Basic | Complex | Complex | Basic | Manual | |
Data Sovereignty | Limited | Limited | ||||
European Support | ||||||
Management Plane | ||||||
| Platform Architecture | ||||||
Cloud Platform Features | Limited | Limited | Complex | |||
API-First Design | Limited | Basic | ||||
Built on Open Source | ||||||
No Vendor Lock-in | ||||||
| Infrastructure as a Service | ||||||
VPCs | Basic | Basic | ||||
Block Storage | ||||||
Object Storage | No | No | ||||
VM Instances | ||||||
NAT Gateways | No | No | Manual | |||
Load Balancers | Basic | Basic | Limited | |||
| Identity & Access Management | ||||||
Multi-Tenant RBAC | Basic | Basic | ||||
SSO Integration | Limited | No | Manual | |||
API Keys & Tokens | Basic | Basic | ||||
Fine-Grained Permissions | Limited | Basic | ||||
Audit Logging | Basic | Basic | Manual | |||
| Advanced Cloud Services | ||||||
Databases as a Service | No | No | Manual | |||
Kubernetes as a Service | Manual | Manual | Manual | |||
Container Registry | No | No | Manual | |||
Key Management | Basic | No | Manual | |||
Serverless | No | No | Manual | Q1 2027 | ||
New Thalassa Cloud services are intended for Private Cloud as well — without a second platform project.
Kubernetes, databases, storage, and networking share identity, APIs, and operations. You do not stitch five products together.
Teams that already use Thalassa Public Cloud keep Terraform, CLI, and console. Hybrid does not mean two operating models.
Capacity is physical servers and sites, not a catalogue SKU. Self-managed or managed. See how a deployment is delivered — hardware, AZs, operations, and connectivity.
Tell us the sites, the starting node count, and whether you will operate it yourself. We will turn that into a design you can take through procurement. No public price list.
Talk to an engineer Technical overview Whitepaper Nederlands
Ready to take control of your Cloud Infrastructure?
Thalassa Cloud
