VM Settings
VM Settings defines the default target server your organization's compiled code deploys to. This setting applies organization-wide, and feeds directly into Phase 4 — Build and Phase 7 — Deployment for every project, unless a project overrides it.
Choosing Your Deployment Infrastructure
From Organization → VM Settings, choose between two infrastructure options:
| Option | Description | Best For |
|---|---|---|
| Colakin Dedicated VM | A managed virtual machine provisioned and maintained by DeX. No setup required on your end. | Teams who want to start building immediately without managing their own servers. |
| Your VM (Custom Infrastructure) | Connect your organization's own server/VM as the deployment target. | Teams with existing infrastructure, compliance requirements, or specific hosting providers. |
Configuring a Custom VM
If you select Your VM (Custom Infrastructure), you'll need to provide your server's connection details (host, credentials, and any required access keys, depending on your provider).
- Enter your custom VM's connection details.
- Click Test Connection to confirm DeX can reach your server before saving.
- Once the test succeeds, click Save Default VM Settings.
⚠️ Always click Test Connection before saving. An unreachable or misconfigured VM won't surface as an error until a project actually reaches Phase 4 — Build, at which point the build will fail and need to be retried after the connection issue is fixed.
How This Connects to Build Access
VM Settings defines the default target for all projects in your organization. Individual project access to Build, Code, QA, and Deployment phases is still gated separately through Build Access, which the Org Admin grants per-project — see Requesting Build Access.
What's Next
➡️ Document Templates — Customize the markdown structures DeX's AI uses when generating your BRD, SRD, FSD, and other documents.