Konstruct product updates: Hosted control planes and multi-cloud

March signified a very important period for the Konstruct team, where we were able to focus on something we’ve heard consistently from teams: reduce the time to value without compromising control.

In the previous post, we walked through how Konstruct 0.1–0.3 established the core platform model, introduced templates, and expanded GitOps into something that can represent both infrastructure and applications.

With 0.4, we’re taking a more opinionated step forward.

This release is about accessibility, deployment flexibility, and multi-cloud reality, making it significantly easier to get started, while expanding where and how Konstruct can operate.

Konstruct 0.4: Hosted control planes and multi-cloud by default

Konstruct 0.4 introduces one of the most important shifts in the platform so far: you no longer need to run the control plane yourself to use Konstruct. Alongside that, we’ve expanded cloud support and simplified the onboarding experience to the point where you can go from zero to a running platform in minutes.

You can learn more about our 0.4 release by clicking here.

The Hosted Control Plane

The headline feature in 0.4 is the Hosted Control Plane.

For the first time, Konstruct is available as a fully managed SaaS offering, where the control plane layer is operated by Civo. This means platform teams can use the full Konstruct experience, GitOps workflows, cluster provisioning, and application delivery, without provisioning or maintaining the underlying control plane infrastructure.

This isn’t a stripped-down version of the product. It’s the same platform model, just with a different operational boundary.

1                ┌───────────────────────────────┐
2                │   Civo-Hosted Control Plane   │
3                │   konstruct.saas.civo.com     │
4                │       (Managed by Civo)       │
5                └──────────────┬───────────────┘
6                               │
7                       Bootstrap via GitOps
8                               │
9                               ▼
10                ┌───────────────────────────────┐
11                │   Your Management Cluster     │
12                │      (Civo Kubernetes)        │
13                └───┬──────────┬───────────┬───┘
14                    │          │           │
15                    ▼          ▼           ▼
16              ┌─────────┐ ┌─────────┐ ┌─────────┐
17              │Workload │ │Workload │ │Workload │
18              │ Cluster │ │ Cluster │ │ Cluster │
19              │ (Civo)  │ │ (AWS)   │ │ (GCP)   │
20              └─────────┘ └─────────┘ └─────────┘

A simpler architecture for hosted users

With the hosted model, Konstruct shifts from a three-tier architecture to a more streamlined two-tier experience:

• Your management cluster (running on Civo Kubernetes), where your platform tooling lives
• Your workload clusters (running on Civo, AWS, or GCP), where your applications run

The Konstruct API, operators, and UI are handled by Civo-managed infrastructure. Availability, upgrades, and security patching of the control plane are no longer your responsibility.

But importantly, this does not reduce your ownership of the platform.

What you still own

Even in the hosted model, the boundaries are deliberate:

• You own and operate your management cluster
• You own the GitOps repository backing your platform
• You own and operate all workload clusters
• You control and customize platform tooling through GitOps

This is a key design decision. Konstruct removes operational overhead where it doesn’t add value, but it preserves control where it matters.

From sign-up to cluster in minutes

To support the hosted model, we’ve introduced a completely redesigned onboarding flow. Through the Konstruct UI, new users can:

• Connect a cloud account
• Connect a Git provider (GitHub or GitLab)
• Provision a management cluster
• Create their first workload cluster

There are no prerequisites, Helm installs, or bootstrapping steps required. This is the fastest path we’ve ever offered from initial sign-up to a functioning internal platform.

Civo as a first-class cloud provider

Konstruct 0.4 introduces native support for provisioning both management and workload clusters on Civo Kubernetes.

For hosted users, this is the default and required cloud for management clusters. For self-hosted users, it’s an additional option alongside existing providers. This tight integration allows for a much more cohesive experience, particularly when combined with the hosted control plane.

Multi-cloud workload clusters

In earlier versions of Konstruct, multi-cloud was possible, but it wasn’t the default mental model. In 0.4, it is. A single management cluster can now provision and manage workload clusters across:

• Civo Kubernetes
• AWS (EKS)
• GCP (GKE)

Each workload cluster is scoped to its own cloud account credentials, ensuring isolation and clear ownership boundaries.

This aligns with how real organizations operate: different teams, different workloads, different cloud requirements, all managed through a single platform control surface.

Simplified installation for self-hosted users

While hosted is the biggest addition, we’ve also continued to reduce complexity for self-hosted deployments.

Konstruct now installs through a single umbrella Helm chart, consolidating what were previously multiple platform services into one coordinated deployment.

This brings:

• Atomic upgrades
• Coordinated versioning
• Significantly reduced operational overhead

Just as importantly, Konstruct no longer depends on kubefirst. It runs as a fully independent platform while still integrating cleanly into existing environments.

Upgrading to 0.4

For existing users, the upgrade path is intentionally straightforward.

There are no breaking changes in 0.4, and the release remains backward-compatible with 0.3.x configurations.

Standard Helm upgrade:

1helm upgrade konstruct oci://europe-west2-docker.pkg.dev/civo-com/charts/konstruct \
2 --version 0.4.0 \
3 --namespace konstruct-system \
4 --reuse-values

If you manage Konstruct via GitOps, update the target revision in your ArgoCD application manifest:

1spec:
2 source:
3   chart: konstruct
4   repoURL: oci://europe-west2-docker.pkg.dev/civo-com/charts
5   targetRevision: 0.4.0
6   helm:
7     values: |
8       global:
9         konstructVersion: "v0.4.0"

Looking ahead

Konstruct 0.4 is a turning point. Up to now, we’ve focused on building the right abstractions: platform hierarchy, templates, and GitOps as a universal interface. With 0.4, we’re focusing on how quickly teams can adopt those abstractions and how broadly they can apply them across environments.

Hosted control planes remove the biggest barrier to entry. Multi-cloud support reflects how organizations actually operate. And simplified onboarding ensures that getting started doesn’t require a dedicated platform team from day one.

If you are interested in a demo of the Konstruct platform or talking to someone about our enterprise scalability, schedule time with me here.