FAQ

I want to try Edera Protect, how do I get access?

Edera Protect is currently available as a release candidate. If you’re interested in early access and becoming one of our design partners, please reach out to us via our contact form.

How does Edera Protect work without Nested Virtualization?

Edera Protect is written in Rust with a safe microkernel. Edera Protect manages a concept called zones which correspond to VMs. One of these zones is a root zone, which runs the node’s standard operating system image, which makes it unnecessary to run a different operating system or change OS details. The root zone can create other zones to run applications or jobs within. These zones have their own kernel within them with their own resources that are managed by Edera Protect.

Does this look similar to a stripped down Linux with gVisor running on top for instance?

When compared to gVisor where syscalls are intercepted, Edera Protect is a level deeper, creating a managed environment for the zone, so the syscalls aren’t intercepted or restricted, but the allocation of resources within the zone is. The zone uses features already inside the Linux kernel to run the unmodified kernel in a paravirtualized mode. Device drivers still function normally, but the hypervisor provides a virtual interface such that hardware support is not required to achieve virtualization.