Software agencies & ISVs · Public Cloud
Agencies end up with a different hosting setup for every client. On Thalassa Public Cloud that is one setup: organisations, Terraform, Kubernetes, databases, and networking, in the Netherlands.

The first environment is easy to stand up. It gets expensive when client three wants their own IAM, their own invoice, and a straight answer on where the data sits. Public Cloud is that setup, reused.
One organisation per engagement. IAM, resources, and the bill stay with that client. Your own company can live in a separate organisation from the work you deliver.
Clusters, databases, networks, and keys go through the same provider. The pipeline and the console call the same API, so a change in CI is the change you see in the UI.
Kubernetes, PostgreSQL, and S3-compatible storage. When the contract ends, another team can run it. They do not need a panel only your people know.
Services a delivery team puts on a client platform. New organisations get €100 credit for three months, enough to stand up a demo.
The console is for looking things up. Terraform is for changing them. Both use the same API.
Managed clusters and databases on the VPC and IAM of that organisation, with load balancers and security groups on the same account.
Keys and secrets are platform services in the Netherlands, next to the workloads. No second vendor for them.
Kubernetes, S3, PostgreSQL, Prometheus. The team that takes over already knows those APIs.
Register and open the organisation yourself, or write to us about the engagement. Either way it is Terraform, IAM, and a region in the Netherlands.
Contact our team Register for freeSoftware agencies & ISVs
Offer your clients a European Public Cloud solution.