Bring your own servers

Available on Standard and Enterprise.

Consumer vibe platforms usually host your app on their shared infrastructure. Regulated buyers often cannot accept that: data residency, network boundaries, and operational control matter as much as the UI.

With bring your own servers, your workspace registers Remote Docker hosts that you control — in your cloud account, on-prem, or in-region. Container projects can run there so the runtime stays inside environments your security and compliance teams already approve.

That blank server is the input. On Enterprise, you put it in an enclave and plug the enclave into a regime (HIPAA, ISO 27001, NERC/CIP, SOC 2, or custom). Standard registers the host; Enterprise is where the host joins a regime-bound pool you operate for the groups or customers who must achieve that regime.

Why it matters for regulated industry

“Deploy inside the customer’s own environment” is the difference between a clever prototype and something an auditor or counterparty will accept. BYO servers are how Vibe becomes infrastructure. Enclaves are how you keep that infrastructure on the right side of a regime — regime-specific hygiene, compliance elements, and automation, instead of a ticket queue.

What you can do

  • Add workspace Docker hosts (install one-liner from Workspace Settings → Docker when your plan unlocks it)
  • Place container apps on those hosts instead of only hub defaults
  • On Enterprise, assign hosts to enclaves so projects stay in a regime-labeled pool
  • Resize containers on the same runtime as your workload grows (Standard+)
  • Keep Diode as the secure publish/access path while compute stays yours