← Selected projects
One-user pilot · workspace not launched

Developer Environment Platform

A self-hosted control plane for remote development workspaces, with a separate app/test environment proposed for a later stage. This page shows what is set up and what still needs evidence.

Architecture flow: an intended developer request, still pending onboarding, points to the deployed Coder control plane connected to external PostgreSQL and Prometheus. The Terraform workspace template is not imported; no workspace or home volume has been created. The separate app/test service is proposed, not implemented. Current access is temporary trusted-LAN HTTP; private DNS and trusted TLS are not ready.
Current pilot boundary: the control plane is deployed; onboarding, the workspace template, and the separate app/test lifecycle are not qualified.

Control plane

  • Coder Community is deployed for a single trusted user.
  • External PostgreSQL connectivity and migrations are verified.
  • Prometheus metrics are being scraped.
  • Temporary access is trusted-LAN HTTP; private DNS and trusted TLS are not ready.

Workspace template

  • Terraform defines an unprivileged Kubernetes workspace.
  • A 1 GiB node-local home volume is described by the template.
  • The template has not been imported or applied; no workspace volume exists.

App/test environments

  • A separate service would create short-lived application and test environments.
  • CI trust, artifact provenance, expiry, cleanup, and recovery still need design and qualification.
  • Its lifecycle must remain separate from developer workspace files.

What has to work before this is a workspace service

  1. Complete first-admin setup and import the reviewed template.
  2. Launch a workspace and verify the Coder agent connection.
  3. Prove home-directory persistence across three stop/start cycles.
  4. Test network boundaries, deletion behavior, backup, and recovery.

No workspace qualification gate has passed.