-
Notifications
You must be signed in to change notification settings - Fork 28
Enarx FAQ
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.
The letter "n", then "arks". En-arks. Enarx. Simple
It's almost Latin for "in the citadel" or "within the stronghold". Nathaniel McCallum and Mike Bursell, who are ultimately to blame of the project, are both old/ancient language geeks, and wanted a cool name. We tried lots: some were rubbish, some were taken. We chose Enarx, which also (luckily) turned out not to be trademark-encumbered.
Absolutely. All of Enarx is, and always will be, open source. We use the Apache 2.0 license.
Everybody. No: really. Do you have some sensitive data or processes? Yes, you do. So you're a potential Enarx user.
(2019-06-27) Sadly not. We're working hard, and we'd love people to work with us. We hope to be adding more information very soon, to allow you to get started. If you want more, or something sooner, please feel free to add an Issue, and we'll see what we can do.