Directory DevOps & Platform EngineeringInfrastructure as CodeKCL

KCL

Open Source

About KCL

KCL originates from programming languages such as Python and Golang. It uses schema-centric configuration types and modular abstraction based on Config, Schema, Lambda, and Rule. Configuration stability is built on a static type system, immutability, and constraints. It supports CRUD APIs, multilingual SDKs, and language plugins for GitOps. It natively supports API ecological specifications such as OpenAPI, Kubernetes CRD, and KRM spec.

Products

Schema: Abstracts a schema-centric model with static typing.
Lambda: Defines and reuses configuration and logic through small function fragments.
Rule: Defines environmental rules to ensure consistency and stability.

Used for

Codifying modern configuration and policy
Modeling configuration types and modular abstractions
Merging isolated configuration blocks with multiple strategies
Automating CRUD APIs and GitOps workflows via SDKs and language plugins

From KCL's own website, read 2026-10-23. How we build listings.

How to evaluate Infrastructure as Code

This is how the CIOPages Research Team evaluates this category. It is not an assessment of KCL. It comes from our Infrastructure as Code (IaC) Platforms buyer guide.

25%

Language & Authoring Model

Declarative DSL (HCL) vs. general-purpose language (TypeScript, Python, Go, C#); readability for reviewers vs. expressive power (loops, conditionals, abstractions); module/component reuse and registry maturity; testing and IDE support; learning curve for the people who will actually write infrastructure

20%

State Management & Drift

Where state is stored, remote-state locking to prevent concurrent-apply corruption, state encryption and secret handling, plan/preview fidelity, drift detection and continuous reconciliation, import of existing resources, and blast-radius controls on apply

20%

Policy-as-Code & Governance

OPA/Rego and Sentinel support, pre-apply guardrails (block non-compliant resources, mandatory tags, region/cost limits), RBAC and SSO/SAML/SCIM, audit logging, approval workflows, and integration with cost-estimation and security scanning in the pipeline

15%

Provider Ecosystem & Portability

Breadth and quality of providers/resource coverage, day-one support for new cloud services, multi-cloud and on-prem reach, third-party SaaS providers, and how locked-in the resulting code is to one vendor or one cloud

10%

Collaboration & Workflow (TACOS)

Run orchestration and queuing, VCS/PR-driven plans, stack dependencies, self-service environments with TTL/ephemeral teardown, drift remediation workflows, and whether you self-host in CI (Atlantis-style) or buy a managed platform

10%

Licensing & Project Health

License (open-source MPL/Apache vs. source-available BUSL vs. proprietary), governance and ownership after recent M&A, release cadence and roadmap, community/foundation backing (CNCF, Linux Foundation), and how easily you could exit or fork

Other Infrastructure as Code Vendors

CIOPages put this listing together from public sources. It’s information, not an endorsement. How we build listings. Work here? Claim this listing or .