Edera
A commercial Kubernetes runtime that boots each pod into its own paravirtualised "zone" with a dedicated kernel on a Xen-derived hypervisor, without needing nested virtualisation. A commercial alternative to Kata for pod-level VM isolation on everyday cloud instances; evaluate it if nested virtualisation is your blocker.
Overview
Edera is a venture-backed company whose "Edera Hardened Runtime" runs "each Kubernetes pod with its own kernel for true hardware isolation at performance within 5% of native". The architecture is a "microkernel hypervisor (Xen)" whose control components are "rewritten in Rust for safety and maintainability"; the hypervisor is limited to essential hardware interaction while networking and device drivers live in user-space processes in a hardened root zone or in separate driver zones, so "Compromise of a driver does not compromise the host". Each workload runs in a zone, "a virtual machine guest environment where pods run with a dedicated zone kernel" pulled as an OCI image. Zones run as paravirtualised guests, which the docs say avoids the need for nested virtualisation and lets Edera run on most cloud instances; PVH and an "Edera KVM" backend (early access) are alternatives. Pods opt in with runtimeClassName: edera.
Install guides cover AWS EKS, Google Compute Engine, Azure Linux, Linode and Bottlerocket, plus a standalone mode without Kubernetes. The product is commercial and its licence is not stated; the edera-dev GitHub organisation publishes components under open licences, notably krata, a GPL-2.0 Xen control plane described as "the base layer upon which Edera Protect zones are built", plus styrolite (Apache-2.0 programmatic sandboxing) and am-i-isolated. The product page claims "Edera pods ran ~20% faster and up to 40% more efficient than Kata" in one customer environment. Pricing, compliance certifications and SLAs are not published. No sandbox platform on this site documents building on Edera.
Notable
- Backers listed on the site: 645 Ventures, MANTIS, Eniac, IQT, FPV and M12 (Microsoft's venture fund)
- krata, the open-source Xen control plane under Edera zones, is GPL-2.0; styrolite and other components are Apache-2.0
- Claims performance "within 5% of native" and ~20% faster than Kata in a customer environment (vendor figures)
Edera specifications
| Attribute | Details |
|---|---|
| Isolation | Xen-derived microkernel hypervisor with control components rewritten in Rust; each pod runs in a zone (a lightweight VM with its own Linux kernel) as a paravirtualised guest, with PVH and a KVM backend as options |
| Deployment | Self-hosted software · Self-hostable |
| Open source | No |
| SDKs and interfaces | CLI |
| Cold start (vendor claim) | Not documented |
| Max session length | Not documented |
| Persistence | Not documented |
| GPU | Yes - NVIDIA and AMD GPU passthrough, NVIDIA GPU Operator with zones and a DRA driver; GPU drivers can run in separate driver zones |
| Networking | Not documented |
| Pricing | Not published; the site offers "Book a Meeting" and early access forms |
| Free tier | Not documented |
| Compliance | Not documented |
| Regions | Not documented |
Facts from Edera’s public documentation, verified November 9, 2026. Performance numbers are vendor claims.
Strengths and trade-offs
Strengths
- You run Kubernetes on cloud instances without nested virtualisation and still want a kernel per pod
- You need GPU workloads isolated with drivers kept out of the host kernel
- You want VM isolation adopted through a standard RuntimeClass with no application changes
Trade-offs
- The runtime itself is proprietary with unpublished pricing; only components such as krata are open source
- Kubernetes-centric: no sandbox SDK, snapshots or per-execution API documented
- Xen-based design is unusual in the container ecosystem and sits outside the Kata/Firecracker tooling
- Compliance certifications and SLAs are not published
Good fit for: Kubernetes clusters on ordinary cloud instances that need a kernel per pod without nested virtualisation.
How Edera compares
| Sandbox | Isolation | Open source | Self-host / BYOC | Cold start (vendor) | Max session | Snapshots / pause | GPU | SDKs |
|---|---|---|---|---|---|---|---|---|
| Edera | Xen-based zone VM | No | Yes / No | Not documented | Not documented | Not documented / Not documented | Yes | CLI |
| Kata Containers | VM per pod | Yes | Yes / No | Not documented | Not documented | Not documented / Not documented | Yes | CLI |
| gVisor | User-space kernel | Yes | Yes / No | ms (claim) | Not documented | Yes / Not documented | Yes | CLI |
| Kubernetes Agent Sandbox | gVisor or Kata | Yes | Yes / Yes | <1 s (warm pool) | Not documented | Yes / Yes | Yes | Kubernetes CRDs, Python, kubectl |
| Northflank Sandboxes | Cloud Hypervisor microVM | No | No / Yes | <1 s | Unlimited | Not documented / Yes | Yes | JavaScript/TypeScript, Python |
| Firecracker | KVM microVM | Yes | Yes / No | <125 ms (spec) | Not documented | Yes / Yes | No | REST API, CLI |
Frequently asked questions
What is Edera?
How does Edera isolate code?
Is Edera open source?
How much does Edera cost?
What are the alternatives to Edera?
Sources
Cite this page
Agent Sandboxes. (2026). Edera. agentsandboxes.org. Last reviewed November 9, 2026. https://agentsandboxes.org/sandboxes/edera/
Found an error or a missing sandbox? Submit a correction — every entry links to the sources it relies on.