Deploy to your organization
Learn how to deploy and scale Plannix Bot compute workers within your own AWS, GCP, Azure, or Kubernetes environments.
Rollout strategy
A successful enterprise deployment follows a phased approach to validate network connectivity, security perimeter compliance, and internal tool adoption.
- Architecture Validation: Review VPC CIDR blocks, egress NAT gateways, and TLS inspection rules.
- Staging Deployment: Deploy the Helm chart to a non-production cluster and execute synthetic verification runs.
- Team Onboarding: Connect SSO/SCIM and provision workspaces with pre-configured project templates.
Terraform & Helm quickstart
Use our production Helm chart to deploy stateless Plannix worker daemons into your Kubernetes cluster:
# Add Plannix charts repository
helm repo add plannix https://charts.plannix.web.id
helm repo update
# Install worker cluster with autoscaling
helm upgrade --install plannix-workers plannix/worker-node \
--namespace plannix-system --create-namespace \
--set organizationId=org_enterprise_01 \
--set secretToken=${PLANNIX_ENTERPRISE_KEY} \
--set autoscaling.minReplicas=2 \
--set autoscaling.maxReplicas=50Sizing worker compute pools
Each active bot session typically requires 1-2 vCPU cores and 4GB RAM. For heavy compilation or container building tasks, configure dedicated high-memory node pools labeled plannix.io/pool=heavy-build.
DNS and TLS certificate configuration
Plannix daemons communicate with the control plane over TLS 1.3 over standard port 443. Custom root CA bundles can be injected via the Helm values to facilitate corporate proxy inspection.
Health checks & telemetry
Expose Prometheus metrics on port 9090 (/metrics) to monitor sandbox boot latencies, active session counts, memory saturation, and CPU throttling.