Skip to main content
Version: 0.5 (Next)

What is Konstruct?

Konstruct is an Internal Developer Platform (IDP) that distributes self-service control planes to development teams in a consistent, repeatable format. Instead of spending months integrating GitOps tooling from scratch, platform teams start with a fully operational software delivery ecosystem on day one.

The Platform Engineering Challenge​

Building an internal platform is hard. Teams often spend 6-12 months integrating GitOps tooling, secrets management, certificate automation, and cluster provisioning—only to face the same work again for the next team or cloud provider.

Common pain points include:

  • Manual cluster provisioning with inconsistent configurations across teams
  • Custom integration work for every GitOps tool (Argo CD, secrets, certs, DNS)
  • No standardized way to onboard new applications or teams
  • Difficulty scaling platform capabilities across multiple clouds
  • Engineering teams waiting on platform teams for basic infrastructure needs

How Konstruct Solves This​

Konstruct delivers a complete platform engineering ecosystem that your teams can start using immediately.

Deployment Options​

tip

The fastest way to get started is with the Hosted Control Plane. No installation or infrastructure management required.

Konstruct is available in two deployment models:

  • Hosted: Civo manages the Konstruct control plane at konstruct.saas.civo.com. You sign up, create your organization, and start provisioning clusters immediately. No infrastructure to install or maintain.
  • Self-Hosted: You install Konstruct on your own Kubernetes cluster via Helm. You own the full control plane and all platform tooling runs in your environment.

Two-tier architecture — Civo manages the control plane for you:

  1. Civo-managed Control Plane (konstruct.saas.civo.com) — Runs Konstruct, Argo CD, and Crossplane. Fully managed by Civo.
  2. Management cluster (Civo) — Provisioned in your Civo account. Hosts your organization's platform tooling and manages your workload clusters.
  3. Workload clusters — Run your applications. Provisioned in your cloud account.

Self-Service Control Planes​

Each organization receives their own management cluster with pre-integrated platform tooling:

  • Argo CD for GitOps deployments
  • Cert-manager for certificate automation
  • External-DNS for DNS management
  • Secrets management integration
  • Crossplane for infrastructure provisioning

Platform admins operate this management ecosystem. Engineering teams receive ready-to-use workload clusters and focus on building applications, not managing infrastructure.

Day-1 Operational Readiness​

Clusters come production-ready. The bootstrapping process deploys all platform components in the correct order. Teams start deploying applications within minutes of cluster creation—no weeks of integration work required.

Customizable Everything​

Konstruct provides sensible defaults but allows customization at every layer:

  • Cluster Templates - Define your own Terraform modules and GitOps content for how clusters are provisioned. Built-in templates for Civo, AWS, GCP, Azure, and bare metal get you started immediately, or create custom templates for any infrastructure provider
  • Pipeline Templates - Customize the CI/CD workflows that get added to application repositories
  • Platform Tooling - Add, remove, or modify the applications bootstrapped into your clusters
  • Infrastructure as Code - Register your own IaC modules for teams to provision

GitOps Catalog (Coming Soon)​

Distribute individual application components, infrastructure modules, or hybrid packages to your fleets of GitOps clusters. The catalog provides a consistent way to roll out new capabilities across all teams and environments.

Multi-Cloud and Hybrid Ready​

Konstruct ships with built-in cluster templates for Civo, AWS, GCP, Azure, and bare metal. Because templates are fully customizable, Konstruct supports any cloud or infrastructure provider—define your own Terraform modules and GitOps content to provision clusters anywhere.

Your Platform, Your Repository​

Konstruct delivers the actual GitOps repository that powers your platform. This isn't a managed black box—you own the infrastructure code, Argo CD applications, and cluster configurations. This gives you:

  • Full transparency into how your platform is configured and deployed
  • Complete control to customize any component to your organization's requirements
  • No lock-in since your GitOps repository uses standard Kubernetes tooling
  • Self-sufficiency to maintain and extend your platform independently

Built-In Isolation Boundaries​

Konstruct provides isolation at every layer of the platform, giving platform engineering teams precise control over what teams can see, use, and contribute:

  • Control Plane Isolation - The Konstruct control plane operates independently from team workloads
  • Management Tier Separation - Each team's management cluster is isolated from other teams' infrastructure
  • Workload Cluster Namespaces - Fine-grained namespace isolation within workload clusters
  • GitOps Repository Boundaries - Separate GitOps repositories per team with controlled access
  • Argo CD Project Scoping - Argo CD projects limit what resources each team can deploy and where

Platform teams define these boundaries—engineering teams operate within them. This model enables self-service without sacrificing governance or security.

Architecture at a Glance​

On the Hosted Control Plane, Civo manages the top tier for you. You interact with a two-tier cluster model from your perspective:

  1. Management cluster — Provisioned in your Civo account. Hosts Argo CD, Crossplane, cert-manager, and the rest of your platform tooling.
  2. Workload clusters — Run your applications. Managed by the management cluster via GitOps.

Platform teams configure the management cluster. Engineering teams deploy applications to workload clusters without managing platform infrastructure.

Who Uses Konstruct?​

Platform Engineering Teams building internal developer platforms without starting from scratch. Get a working platform on day one and customize it to your organization's needs.

DevOps Teams evaluating IDP solutions that provide GitOps-native workflows out of the box. Skip the months of integration work and start with production-ready tooling.

Engineering Leaders standardizing how their organization delivers software. Give every team a consistent, self-service experience across multiple clouds and environments.

What's Next?​

  • Getting Started - Set up your first organization and cluster
  • Clusters - Explore cluster management, applications, and pipelines
  • Installation - Deployment options and prerequisites