# Edera for Developers

Edera provides hypervisor-level container isolation that works transparently with your existing workflows. No code changes required.

## What changes for you

**Nothing.** Your containers run exactly as before:

- Same Dockerfiles, same images
- Same Kubernetes manifests (just add `runtimeClassName: edera`)
- Same CI/CD pipelines

## Understanding Edera

- **[Architecture overview](https://docs.edera.dev/technical-overview/architecture/)** - How Edera fits into your stack
- **[How Edera works](https://docs.edera.dev/technical-overview/)** - What happens under the hood
- **[Zones explained](https://docs.edera.dev/technical-overview/concepts/zone/)** - The isolation boundary for your workloads

## Deploying your apps

- **[Deploy to Edera](https://docs.edera.dev/guides/deployment/deploy-apps/)** - Add one line to your pod spec
- **[CLI user guide](https://docs.edera.dev/guides/cli-user-guide/)** - Manage workloads with the Edera CLI
- **[GPU support](https://docs.edera.dev/guides/gpu/)** - Run AI/ML workloads with GPU passthrough

## Debugging and troubleshooting

- **[Troubleshooting guide](https://docs.edera.dev/support/troubleshooting/)** - Common issues and solutions
- **[FAQ](https://docs.edera.dev/support/faq/)** - Frequently asked questions

Last updated on 2026-02-18.