Enclaves

Available on Enterprise.

Bring a blank server. Plug it into a regime’s server pool. That pool is an enclave — a product, not a ticket and a six week wait.

You stand up Vibe enclaves for the groups or customers who must achieve a regime (HIPAA, ISO 27001, NERC/CIP, SOC 2, or a custom program such as FedRAMP). The enclave keeps workloads on the right machines and helps you operate your regime.

That is the same object whether you are a platform team serving divisions, a partner serving customers, or the IT person who owns the regime for the company.

An enclave is a named pool of Remote Docker hosts bound to one regime. Container projects stay in that enclave. HIPAA, ISO 27001, NERC/CIP, SOC 2, and custom labels are first-class regimes. The Default pool has no regime.

What you do

  1. Bring a server you control — cloud, on-prem, or in-region.
  2. Put that host in an enclave (Workspace Settings → Docker on Enterprise, or hub Docker settings).
  3. Set the enclave regime: HIPAA, ISO 27001, NERC/CIP, SOC 2, or a custom label.
  4. Create or move container projects into that enclave. Placement does not fall back to other pools.

Connected workspaces that inherit an Enterprise master’s hosts can place into those enclaves; they do not create them. That is how you share one enclave into another workspace.

How this helps the regime

A regime is the control boundary those servers are meant to satisfy. An enclave is how you run that pool as a product: honest placement, a named regime, host operations that stay in-bounds — not a labeled VM and a six-week ticket queue.

An enclave’s regime gives you regime-specific infrastructure hygiene, compliance elements, and automation. Although it does not certify the hosts by itself, it plugs into your organization’s compliance program and can reduce or eliminate many of the manual tasks and attestations required.

For example, HIPAA is a first-class regime and “HIPAA enclave” means this is the pool you use for HIPAA workloads.

Who this unlocks

  • IT / platform teams — provide enclaves to groups, divisions, or customers who must achieve a regime; Vibe helps you operate your regime
  • Partners — the customer buys Vibe; you can provide the enclave they deploy into, and generate revenue from AI. See Diode MSP Partners
  • Compliance owners — a team or one person who needs a pool per regime, operated as a product
  • Domain experts (ESG, energy, ops) whose apps must land on those machines