superedge/superedge resource
An edge-native container management system for edge computing observed · 2026-08-28
Health v2 · maintenance only
23/100
- Activity 0
- Release rhythm 8
- Longevity 100
Flags: no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 2083
- days_rel: n/a
- days_push: 925
- n_releases_24m: 0
Adoption not part of the score
1069 stars · 202 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
SuperEdge is an open-source, Kubernetes-native container management system for edge computing that extends Kubernetes orchestration to multi-region edge nodes non-intrusively. It provides edge autonomy, distributed node health monitoring, region-based service orchestration (ServiceGroup), cloud-edge network tunneling, and an edgeadm installer, and is a CNCF sandbox project.
Use cases
- manage kubernetes workloads across multiple edge sites
- keep edge nodes running autonomously when cloud connection drops
- deploy the same microservices to many edge locations with region-closed traffic
- manage edge nodes without public IPs via cloud-edge tunneling
- bootstrap an edge kubernetes cluster with one command
- run lightweight offline k3s clusters on edge nodes
- monitor edge node health in a distributed way
- convert an existing kubernetes cluster into an edge cluster
When to choose
- you need Kubernetes-native edge management fully compatible with standard K8s APIs
- you operate many geographically distributed edge sites with unstable cloud connectivity
- you want region-scoped deployment and traffic closure for edge microservices
- you need to onboard edge nodes lacking public IP addresses
- you want a one-click edgeadm installer instead of assembling separate tools
When to avoid
- your workloads run entirely in a central cloud with no edge nodes
- you need a fully managed cloud Kubernetes service rather than self-managed edge infrastructure
- you require a very actively developed project - releases are infrequent and it is in maintenance mode
- you need non-Kubernetes container orchestration or lightweight single-node edge setups outside K8s
Facets
infra-config · maturity maintenance
container-orchestration monitoring networking deployment scheduling cloud-computing iot microservices go self-hosted cloud edge-computing edge-kubernetes edge-autonomy servicegroup distributed-node-health network-tunneling edgeadm kins k3s cncf-sandbox containers devops linux kubernetes
7 sources
- readme: https://github.com/superedge/superedge · fetched 2026-08-28 · 2d54fa11f0fa
- homepage: https://superedge.io · fetched 2026-08-29 · 114be9ed9751
- site_page: https://superedge.io/docs · fetched 2026-08-29 · 3b2b6ede8b46
- site_page: https://superedge.io/docs/reference/edge-health · fetched 2026-08-29 · e3870e8485b8
- site_page: https://superedge.io/docs/components/servicegroup · fetched 2026-08-29 · fd3ff6f3676a
- site_page: https://superedge.io/docs/components/tunnel · fetched 2026-08-29 · 7a1d765c3877
- site_page: https://superedge.io/docs/installation/how-to-bootstrap-an-edge-kubernetes-cluster · fetched 2026-08-29 · 298b5d0cc392
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| superedge/superedge | main | 23 |
For agents
markdown · JSON · MCP: product_card(name="superedge/superedge")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem