BuildWithHQ
Canonical knowledge unit · developer

Isolated Developer VM

Each developer can work in an isolated no-unrestricted-internet VM with a local PostgreSQL instance; BuildWithHQ-controlled gateways mediate external AI, packages, MCP, integrations, artifacts, and deployment.

ID: BWHQ-DEV-001Status: specifiedAuthority: medium-highdeveloper-vmpostgresqlisolationgateways

Isolated Developer VM

Environment

The developer VM is an isolated development machine intended to give developers real coding freedom without placing BuildWithHQ core systems, production data, or unrestricted network access inside the same trust boundary.

Local data

Each developer VM should run its own local PostgreSQL instance for developer-controlled application data and testing.

Boundary-crossing services

External AI, MCP, package acquisition, documentation retrieval, integrations, deployment, Git/artifact movement, and other internet-facing actions should pass through BuildWithHQ-controlled gateways or explicitly approved services.

Goal

Provide a normal development experience and custom-code escape hatch while keeping the platform core, credentials, production data, and outbound network policy under controlled boundaries.

Related knowledge

Four MCP surfacesBuildWithHQ’s MCP strategy separates Builder Account, Developer VM, SaaS Application, and End-Customer MCP surfaces while reusing common capability, permission, and audit primitives.API-first custom service boundaryDeveloper custom code runs behind declared, schema-validated API endpoints so BuildWithHQ can bind custom logic into pages, workflows, AI, and external APIs without exposing platform core IP or direct unrestricted SQL.
Machine-readable source: canonical Markdown. This HTML companion exists for human reading, search indexing, and AI retrieval.