Skip to content
This repository was archived by the owner on May 3, 2022. It is now read-only.

Enarx FAQ

Mike Bursell edited this page Jun 27, 2019 · 31 revisions

What's the point of Enarx?

The project aim is this:

  • Create a way to create and run "private, fungible, serverless" applications using Trusted Execution Environments (TEEs). In other words, to provide a platform abstraction for TEEs.

The problem we're trying to address is that there are many sensitive workloads that you shouldn't entrust to a public cloud to run, or may even have concerns about running on on-premises systems. TEEs (see below) provide a great opportunity to help secure these workloads, but they're not easy to use. Enarx aims to make it simple to deploy workloads to a variety of different TEEs in the cloud, on your premises or elsewhere, whilst ensuring that your application workload is as secure as possible.

You can find a basic introduction here: Introducing Enarx.

Is Enarx open source?

Absolutely. All of Enarx is, and always will be, open source. We use the Apache 2.0 license.

To be answered

What's a TEE?

How can I contribute?

Does Red Hat own Enarx?

Why not do containers?

Clone this wiki locally