nixfredEXE.DEVFIELD GUIDE · BY NIX UNOFFICIAL
WHITEBOARD / BOARD: ENTERPRISE HOSTS

Board: enterprise hosts, single-tenant and BYOC

The goal is to show the same exe.dev experience on hardware nobody else shares, or on your own cloud account, backed by a contract and an SLA.

Whiteboard outcome

When you’re done, the board shows the exe.dev control plane, three kinds of hosts (exe.dev-racked, exe.dev in AWS, and your account), pools placed on hosts automatically, and the SLA table in a corner.

Before you draw: three questions

  1. Is the driver isolation, data locality, cloud commitments, or capacity on demand?
  2. Is there a compliance regime (HIPAA, an auditor asking about physical isolation)?
  3. Do you need nested virtualization inside the VMs?

Draw it in 7 steps

  1. At the top, draw a rounded rectangle “exe.dev control plane (lobby)”. Say: “You keep the same SSH, HTTPS API, proxy and integrations” (https://exe.dev/docs/enterprise).
  2. Below it, draw three host columns: “exe.dev hosts (its regions)”, “exe.dev hosts in AWS”, “Your cloud / your rack (BYOC)”. Say: “No other customer’s VM shares their CPUs, memory or disks” (https://exe.dev/docs/enterprise-single-tenant).
  3. Under BYOC, write “needs hardware virtualization + local NVMe: bare-metal or your own rack.” (https://exe.dev/docs/enterprise-byoc)
  4. Draw pool new data --cpus=64 with an arrow to “host decides (no, region)”. Say: “pool hosts shows each host and the largest pool it can take, and pools never fall back to shared hardware” (https://exe.dev/docs/enterprise-single-tenant).
  5. Inside one VM, draw a smaller VM labeled “nested VM (Enterprise)”. (https://exe.dev/docs/enterprise)
  6. In the corner, draw the SLA: “99.9%/month. Credits 10/15/20/30%. Urgent 30 min, Normal 4 h, Low 1 business day.” (https://exe.dev/docs/enterprise-sla)
  7. At the bottom, write the rule: “Minimum is one host. Start with a POC.” (https://exe.dev/docs/enterprise)
flowchart TB
  CP[exe.dev control plane] --> H1[exe.dev hosts<br/>its regions]
  CP --> H2[exe.dev hosts<br/>in AWS]
  CP --> H3[BYOC: your account<br/>bare metal + NVMe]
  H1 --> P1[pool data 64 vCPU]
  H3 --> P2[pool near-your-data]
  P1 --> N[VM with nested VMs]
Whiteboard diagram (rendered from the source mermaid)

What they’ll ask

QuestionAnswerSource
“HIPAA?”A BAA is available for Enterprise.https://exe.dev/docs/enterprise
“GCP?”The pricing page lists “AWS / GCP VPC support” for Enterprise. Scope it in the contract [verify].https://exe.dev/pricing
“Price?”Custom, by contract. The minimum is one entire host.https://exe.dev/docs/enterprise
“Support channel?”A shared Slack channel.https://exe.dev/docs/enterprise

← Board: team pools · The pitch →