Directory DevOps & Platform EngineeringInfrastructure as CodeOpenYurt

OpenYurt

Open Source

About OpenYurt

OpenYurt is an edge computing platform intended to extend the Cloud Native ecosystem to edge computing and IoT scenarios. It makes non-intrusive enhancements that allow management of large scale edge computing workloads across different architectures in a native Kubernetes manner. It has been used in edge computing scenarios including IoT, distributed cloud, logistics, transportation, manufacturing, retail, and CDN. It is a Cloud Native Computing Foundation sandbox project.

Products

raven: Builds cloud-to-edge and edge-to-edge network communication across geographies while maintaining compatibility with native CNI container networks.
pool-coordinator: Provides cloud-edge traffic reuse capability that reduces control plane communication data between cloud and edge.

Used for

Managing large scale edge computing workloads across different architectures such as ARM and X86
Synchronizing edge service state with cloud control after network recovery
Classifying and dividing edge site resources according to geographical distribution
Collecting, processing and controlling data from edge devices

Who it is for

Used by developers managing edge devices

From OpenYurt'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 OpenYurt. 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 .