An open-source control plane on Kubernetes that creates and governs any resource, on any infrastructure.
Platform teams publish golden paths once; developers get a self-service portal for everything else.
Install · Documentation · Community · Contributing · Enterprise
A developer orders a service from a blueprint. More scenarios below.
Platform teams spend their time on tickets and copy-pasted templates, while every new project waits days for infrastructure that should be routine.
Krateo PlatformOps is a control plane that runs on Kubernetes and creates any resource on almost any infrastructure: Kubernetes clusters, applications, pipelines, databases, registries, API gateways.
- One requirement. The resource can be described in YAML as its desired state.
- Validated, applied, reconciled. Krateo validates every change, applies what was approved and continuously reconciles it to the desired state.
- Inside and outside the cluster. It manages resources beyond the cluster it runs on, on the major clouds and on-premises.
- Clear roles. The platform team writes the templates as blueprints; developers use them from a self-service portal and manage the whole lifecycle from one place, instead of searching across dozens of dashboards.
Krateo installs with one Helm chart, the installer. You need a Kubernetes cluster (1.36 or later) with no previous Krateo installation, kubectl and helm.
helm install installer \
oci://ghcr.io/krateo-platformops/charts/installer \
--version 0.3.469 \
--namespace krateo-system --create-namespace \
--set bootstrap.coreProvider.enabled=trueBrowser-facing services get a LoadBalancer by default. On kind or bare metal, use --set exposure.type=NodePort; behind a Gateway API controller, use Gateway. The kind walkthrough covers a local cluster end to end, and the usage guide covers upgrades and uninstall.
No cluster at hand? Try Krateo in the browser in the free self-service lab.
- Golden paths as Kubernetes APIs. Each blueprint becomes a CRD with its own schema, versioning and RBAC.
- Any API as a resource. Generate a Kubernetes operator from an OpenAPI spec with oasgen-provider and manage external services declaratively.
- A composable portal. Navigation, pages and forms are Kubernetes resources.
- Observability built in. OpenTelemetry collects logs, metrics, traces and Kubernetes events into ClickHouse, explorable in HyperDX. Events are tagged with the composition they belong to and stream live into the portal.
Recorded on the Krateo portal. Each clip is one scenario, with a caption for every step.
Platform team · publish a blueprint from the Marketplace
Developer · order a service from a blueprint
Developer · fix a failed deployment
Ready-to-use blueprints for AWS, Azure, Google Cloud, OpenStack, Keycloak and more live in the krateo-blueprints organization.
- Documentation for concepts, guides and reference
- What's new in 3.0 and the compatibility matrix
- Release notes for the history of every platform release
Questions and ideas go to GitHub Discussions. For real-time chat, join us on Discord.
If Krateo PlatformOps is useful to you, star this repository: it helps other platform teams find it.
Bug reports, documentation fixes and new blueprints are the most valuable contributions right now. Read CONTRIBUTING before opening a pull request, and report vulnerabilities privately as described in the security policy.
Platform releases are tag-driven and assembled by the installer; see how a release ships.
Licensed under the Apache License 2.0.
Once the platform runs, most of the work is keeping it healthy and changing it safely. AGENTIKO is the reasoning plane built by Krateo on Krateo PlatformOps: its agents read the platform, investigate, and prepare the change. They propose, they prove, a person decides, and the loop closes.
AGENTIKO is a commercial product, in alpha at Kiratech since 3 August 2026.