Start Here
Helm
Deploy Monkeys services to Kubernetes with Helm
Monkeys still uses the same product boundary in Kubernetes as it does locally. Core services stay together, while optional capability services are added only when needed.
Use Docker Compose for local development and smoke testing before creating Kubernetes values. Helm deployment should promote the same service boundaries to a cluster environment.
What to Deploy
| Area | Repositories |
|---|---|
| Core product | monkeys-server, monkeys-studio, monkeys-kernel, monkeys-compute |
| Agent | monkeys-agent-server, monkeys-mcp-server, monkey-tools-agentkits |
| Billing | monkeys-billing-server |
| Data | monkeys-data-server, monkeys-conductor-worker |
| Webhook | monkeys-webhook-server |
| Workers | monkeys-conductor-worker, monkeys-training-worker, monkeys-comfyui-worker |
| Tools | monkey-tools-third-party-api, monkey-tools-third-party-api-python, monkey-tools-sandbox, monkey-tools-agentkits |
Reference Material
- Helm charts:
https://github.com/infmonkeys/helm-charts - Ecosystem entrypoint:
https://github.com/infmonkeys/monkeys
Deployment Checklist
- Prepare Kubernetes namespace, ingress, TLS, storage classes, and image pull credentials.
- Decide whether PostgreSQL, Redis, Elasticsearch, Conductor, MinIO, Prometheus, and Grafana are managed services or chart-managed dependencies.
- Build and publish service images for the repositories you deploy.
- Put runtime config and secrets in Kubernetes Secrets or your external secret store.
- Deploy core services first, then add optional capability services.
- Verify health, metrics, workflow execution, and Studio API connectivity.
Notes
- The docs repo intentionally does not keep production secrets.
- Runtime config such as
config.yamlstays in the owning service repository or the deployment secret store. - Use the service README and deployment charts together when deploying a specific capability.