Getting started

1 min read

Edera runs every container in its own VM. You get hypervisor-level isolation with one line of Kubernetes config—no image changes, no rebuilds, no new workflows.

See it in action

The interactive demo shows Edera blocking a real container escape attack. No install required—just sign up and watch it work.

Run it yourself

ℹ️

Already have Edera installed? Skip to Deploy your first workload.

Install Edera on your nodes (detailed guides):

git clone https://github.com/edera-dev/learn.git
cd learn/getting-started/edera-installer
# Add your GAR key as key.json (contact support@edera.dev if you need one)
INSTALLER_IP={node_ip} make deploy

Deploy your app with one change:

spec:
  runtimeClassName: edera
  containers:
    - name: my-app
      image: my-app:latest

Verify it’s running in a zone:

kubectl get pod my-app -o jsonpath='{.spec.runtimeClassName}'
# edera

That’s it. Your container is now isolated in its own VM with a dedicated kernel.

Go deeper

For Developers

Build and deploy with zero changes

For Platform Engineers

Set up and manage infrastructure

For Security Teams

Understand the security model

Learn more: How Edera works · GPU passthrough · FAQ

Need help? support@edera.dev

Last updated on 2026-03-04