As we continue launching and introducing new cloud services, recently we have been receiving feedback that it can be overwellming to quickly try out our platform. You need familiarity with other cloud platforms such as AWS, Azure to fully understand the services we are offering. This makes sense, as we are building an alternative for the hyperscaler clouds, so we focus on building blocks, APIs and tight service integrations.
But as we love to also make things easier to just try out and see what we have, without having to setup a terraform project, or do a lot of clickops work, we are happy to introduce a new feature that allows people to quickly launch a preconfigured environment with a Kubernetes cluster and other Infrastructure.
Introduction into Load Balancers on Thalassa Cloud Load balancers play a critical role in any cloud infrastructure. They ensure that incoming traffic is reliably routed to healthy services, distributing load across multiple backend targets. On Thalassa Cloud, load balancers are designed from the ground up to be fast, flexible, and API-driven. Built on top of Envoy Proxy, our load balancer implementation provides high performance with a strong focus on automation and self-service.
We’ve just released the first version of thalassa-cloud/client-go, our Go SDK for integrating with the Thalassa Cloud API.
This SDK is intended for engineers and teams looking to interact with Thalassa Cloud programmatically. It provides a native Go interface to our API and will be the base for upcoming tools like our CLI, Terraform provider, Kubernetes CCM, and other integrations.
What’s included The initial release includes support for core primitives such as VPCs, Subnets, Organizations, basic compute functionality.
Introducing Custom Route Tables for VPCs Networking is at the core of any cloud infrastructure, and Thalassa Cloud’s Virtual Private Clouds (VPCs) provide secure, isolated environments for deploying workloads. Until now, our VPC networking was fully automated—when a NAT Gateway or other networking component was created, routing rules were automatically assigned. While this made deployment seamless, it limited flexibility for advanced networking use cases.
With the introduction of custom route tables, users now have full control over how traffic moves within their VPCs, enabling:
Understanding Digital Sovereignty Digital sovereignty has become essential for organizations in Europe looking to maintain control over their digital infrastructure and operations. With increasing reliance on external platforms, the ability to secure and manage data independently is critical for compliance, resilience, and growth. By prioritizing digital sovereignty, businesses can safeguard their operations, ensure alignment with European regulatory compliance, and build a foundation for sustainable success.
What is Digital Sovereignty? Digital sovereignty means having complete control over your organization’s data, infrastructure, and cloud environments.
Why We Chose Cilium as the Default CNI for Thalassa Cloud When we set out to build the Kubernetes platform for Thalassa Cloud, we knew that every component we selected had to align with our vision: a platform that prioritizes performance, security, and flexibility. One of the most critical choices we faced was selecting the right Container Network Interface (CNI). Networking is the backbone of any Kubernetes deployment—get it right, and your platform thrives.
Waarom Digitale Soevereiniteit Jouw Concurrentievoordeel Is In een tijd waarin data wordt gezien als het nieuwe goud, is de vraag niet langer waar je data staat, maar wie er controle over heeft. Data is de motor van innovatie en een cruciale pijler voor besluitvorming, bedrijfsvoering en concurrentievoordeel. De groeiende afhankelijkheid van publieke cloudproviders roept echter vragen op over zeggenschap, veiligheid en flexibiliteit. Wie toegang heeft tot jouw data en hoe deze wordt beheerd, kan directe gevolgen hebben voor de continuïteit van je bedrijfsvoering en je naleving van regelgeving.
In this post, we explore why multi-tenancy in your cloud platform is crucial for modern cloud operations by examining an example of a financial services company navigating common challenges in private cloud management. We highlight how the lack of multi-tenancy contributes to why development teams often advocate for public cloud.
To illustrate, consider a large financial services company that operates its entire infrastructure on a private cloud, retaining ownership of its hardware to maximize control over data, performance, and compliance.