For seven years, I've watched the same pattern. An organization decides it needs a platform and assigns two of its best engineers. They estimate it will take three months, but eighteen months later, they're still integrating ArgoCD with their secrets manager, still debugging Crossplane providers, and still arguing about how to structure the GitOps repo. What’s happened is they’ve built something that works for one team and can't be repeated for a second.

I've said before that this problem ends with Konstruct. But there was still a barrier: you needed a Kubernetes cluster, you needed Helm, and you needed to get through the install before you could see what the platform actually does.

Today we're removing the friction entirely.

Konstruct hosted control plane

Konstruct 0.4 introduces a hosted control plane at konstruct.saas.konstruct.io. Civo manages the entire control plane tier. You can sign up with your Civo account, connect an API key, and immediately begin building your platform without needing to install or configure anything upfront.

Here's what happens:

  1. Sign up at konstruct.saas.konstruct.io
  2. Create an organization
  3. Connect your Civo cloud account
  4. Connect your GitHub account
  5. Create a management cluster
  6. Deploy your first workload cluster

Once completed, your first cluster can be running in under 30 minutes. You will have a complete platform with ArgoCD, Crossplane, cert-manager, External Secrets, ingress, and DNS, all fully integrated and reconciling through your own GitOps repository. This is not a demo or a sandbox, but a production-ready platform that you own and can extend from the start.

What changes and what remains the same

With the hosted control plane, Civo manages the control plane tier, including the Konstruct operators, API, user interface, upgrades, availability, and security patching. This removes the need for you to operate or maintain that layer.

What you own hasn't changed at all:

  • Your management cluster runs in your Civo account, where you retain full control over the nodes, workloads, and ArgoCD instance, along with complete kubectl access.
  • Your GitOps repository remains in your GitHub or GitLab organization, containing every configuration, automation, and application manifest. If you choose to stop using Konstruct, your platform continues to run.
  • Your workload clusters run wherever your business requires, including Civo, AWS, and GCP, all managed from a single management cluster.

This is the same zero lock-in architecture we have always built. The hosted control plane removes the friction of getting started without changing the underlying ownership model, so you continue to own everything that matters.

Multi-cloud from day one

One of the biggest additions in 0.4 is multi-cloud workload clusters. A single management cluster on Civo can now provision and manage workload clusters across Civo, AWS EKS, and GCP GKE simultaneously.

This reflects how platform engineering works in practice. Your management cluster does not need to reside in the same cloud as your workload clusters. You can run your platform tooling on Civo, for speed and cost efficiency while running production workloads on whichever cloud your business requires. The result is a consistent set of GitOps workflows, developer experience, and reusable templates across environments.

Because everything is defined through your GitOps repository, adding or switching cloud providers becomes a configuration change rather than a migration.

Free to start, with no hidden constraints

With the Starter tier, your first two Civo clusters are license-free. This is not a time-limited trial or evaluation period, but a permanent entry point.

You can sign up for the hosted control plane, create an organization, provision both a management cluster and a workload cluster, deploy applications, and operate a real platform without paying any licensing fees. You only pay for the underlying Civo compute resources, while Konstruct itself remains free at this level.

When you need additional clusters, hyperscaler support, or enterprise features, the Pro tier starts at $250 per month per additional cluster. There is no enforced upgrade timeline, and you can continue using the free tier for as long as it meets your needs.

This approach is based on the belief that the primary barrier to platform engineering adoption is not the technology itself, but the cost and complexity of getting started. If you can experience a complete platform within 30 minutes at no cost, the value becomes clear without requiring a traditional sales process.

Self-hosted isn't going anywhere

The hosted control plane provides the fastest path to getting started, but it may not suit every enterprise requirement. Self-hosted Konstruct remains available as the same product, with full control over the control plane tier.

This option is appropriate for use cases such as air-gapped environments, direct kubectl access to the control plane, custom operator configurations, management clusters on non-Civo clouds, or specific data residency requirements. The 0.4 Helm chart is backward compatible with 0.3 configurations, allowing for a standard upgrade path.

Both deployment models deliver the same platform capabilities. The distinction lies in who operates the control plane. You can start with the hosted model and transition to self-hosted when necessary, or adopt self-hosted from the beginning, depending on your requirements.

What this means

Over the past year, I have said that Konstruct can deliver in minutes what typically takes teams months to build. While that was accurate, it still required installation and setup. Now, it requires only a login.

Platform engineering should not be gated by multi-day setup processes or require dedicated effort just to evaluate tooling. Eliminating that operational overhead is a core principle of what we are building, and it should be reflected in the very first interaction with the product.

You can sign up at konstruct.saas.konstruct.io, have a working platform running within the same morning, and extend it as needed from there.

If you would like to discuss how Konstruct can support your teams at scale, schedule time with me. I would be interested to hear what you are building.

Learn more