packet.net offers Trusted Compute: a cryptographic chain of trust from hardware to the distributed cluster. Yet, not all of the 9 CPU configurations that they offer under this service are Intel-based, and only one is SGX-capable: C1.SMALL.X86 based on a E3-1240 v5 CPU.

As of April 2018, in talking with their customer and technical support teams, they provided a quote for $270/month with a one-year contract and a 30-day cancellation for a dedicated C1.SMALL.X86 bare metal server, a very similar quote to what IBM quoted at the same time for the same specs.

Yet, when querying further about the feasibility of them enabling SGX through the BIOS when provisioning these dedicated servers, I got a more discouraging response:

I completed my testing against all of our potentially capable Intel servers: c1.small, c1.xlarge, m1.xlarge and m2.xlarge.

Unfortunately, none of them have SGX enabled. Enabling SGX is BIOS dependent (as some of you know), and for reasons that are unclear our hardware partners ship that turned off. I looked for this setting on some of our systems, and could not find it. It may be hidden behind other features (like TXT) that we cannot turn on. It may require new BIOS/UEFI firmware loaded on these systems to support that feature. We can't support TXT because we cannot enable a fully trusted boot chain and we cannot support manual steps during our provisioning and deprovisioning processes that TXT require.

Either way, enabling SGX on our Intel platforms would require a large amount of integration testing so I don't think it will be something we can support in the short term.