Up to 3,000 users

The 3,000 users architecture targets large-scale enterprises, possibly with on-premises network and cloud deployments.

Target load: API: up to 550 RPS

High Availability: Typically, such scale requires a fully-managed HA PostgreSQL service, and all Coder observability features enabled for operational purposes.

Observability: Deploy monitoring solutions to gather Prometheus metrics and visualize them with Grafana to gain detailed insights into infrastructure and application behavior. This allows operators to respond quickly to incidents and continuously improve the reliability and performance of the platform.

Hardware recommendations

Coderd nodes

UsersNode capacityReplicasGCPAWSAzure
Up to 3,0008 vCPU, 32 GB memory4 / 1 coderd eachn1-standard-4t3.xlargeStandard_D4s_v3

Provisioner nodes

UsersNode capacityReplicasGCPAWSAzure
Up to 3,0008 vCPU, 32 GB memory8 / 30 provisioners eacht2d-standard-8t3.2xlargeStandard_D8s_v3

Footnotes:

  • An external provisioner is deployed as Kubernetes pod.
  • It is strongly discouraged to run provisioner daemons on coderd nodes at this level of scale.
  • Separate provisioners into different namespaces in favor of zero-trust or multi-cloud deployments.

Workspace nodes

UsersNode capacityReplicasGCPAWSAzure
Up to 3,0008 vCPU, 32 GB memory256 nodes / 12 workspaces eacht2d-standard-8t3.2xlargeStandard_D8s_v3

Footnotes:

  • Assumed that a workspace user needs 2 GB memory to perform
  • Maximum number of Kubernetes workspace pods per node: 256
  • As workspace nodes can be distributed between regions, on-premises networks and cloud areas, consider different namespaces in favor of zero-trust or multi-cloud deployments.

Database nodes

UsersNode capacityReplicasStorageGCPAWSAzure
Up to 3,0008 vCPU, 32 GB memory21.5 TBdb-custom-8-30720db.t3.2xlargeStandard_D8s_v3

Footnotes:

  • Consider adding more replicas if the workspace activity is higher than 1500 workspace builds per day or to achieve higher RPS.
See an opportunity to improve our docs? Make an edit.