Directory DevOps & Platform EngineeringInfrastructure as CodeSuperEdge

SuperEdge

Open Source

About SuperEdge

SuperEdge is an open-source container management system for edge computing. It extends native Kubernetes to the edge in a non-intrusive way. It supports all native Kubernetes APIs and resources. It provides edge autonomy for unstable network conditions between cloud and edge hosts. It is a CNCF sandbox project.

Products

ServiceGroup: Provides a workload unit to orchestrate container applications in a closed-looped network by region, with canary deployment support.
Network Tunneling: Creates a tunnel between kube-apiserver on the cloud and kubelet at the edge.
Edgeadm Installer: Provides edgeadm to bootstrap an edge Kubernetes cluster.
Distributed Health Check: Provides built-in edge-side health monitoring for health-checking to maintain edge autonomy.

Used for

Orchestrating container applications in a closed-looped network by region
Bootstrapping an edge Kubernetes cluster
Monitoring edge-side health to maintain edge autonomy
Tunneling between kube-apiserver on the cloud and kubelet at the edge

From SuperEdge's own website, read 2026-10-24. 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 SuperEdge. 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 .