Monkeys Architecture
Logical architecture of the current Monkeys ecosystem
Architecture Overview
Monkeys is now organized as a multi-repository ecosystem. The monkeys repository is the documentation and infrastructure entrypoint. Product source code lives in the owning service repositories.
Core Product
The core product is the minimum useful Monkeys platform.
| Module | Repository | Responsibility |
|---|---|---|
| Studio frontend | monkeys-studio | Main user-facing workspace for workflows, agents, tools, assets, design, data, evaluations, and settings. |
| Kernel frontend | monkeys-kernel | Platform and kernel management frontend. |
| Compute frontend | monkeys-compute | Compute control-plane frontend. |
| Main backend | monkeys-server | Core API, workflow entrypoint, auth, marketplace, assets, tools, model configuration, and service bus. |
Capability Services
Capability services are deployed only when the feature area is needed.
| Capability | Repositories | Relationship |
|---|---|---|
| Agent runtime | monkeys-agent-server, monkeys-mcp-server, monkey-tools-agentkits | Agent threads, messages, model providers, tool calls, HITL approval, MCP access, and reusable agent tools. |
| Billing and metering | monkeys-billing-server | Tool pricing, team balance, usage records, and payment integration. |
| Data workflows | monkeys-data-server, monkeys-conductor-worker | Data resource APIs, tag/view search, indexing, and workflow task execution. |
| Webhooks | monkeys-webhook-server | Alert, recovery, daily report, weekly insight, and channel notification delivery. |
| Third-party tools | monkey-tools-third-party-api, monkey-tools-third-party-api-python, monkey-tools-sandbox, monkey-tools-agentkits | External API adapters, Python tools, code execution, and agent toolkits. |
| Image and ComfyUI flows | monkeys-comfyui-worker | ComfyUI queue and image generation execution. |
| Training flows | monkeys-training-worker | Model training and model-test background tasks. |
Infrastructure
The local infrastructure stack in monkeys includes:
| Infrastructure | Local endpoint | Used by |
|---|---|---|
| PostgreSQL | localhost:5432 | Main backend, agent, billing, data, webhook, Conductor, workers. |
| Redis | localhost:6379 | Cache, queues, background dispatch, workers. |
| Elasticsearch | http://localhost:9200 | Conductor indexing and data search acceleration. |
| Conductor API | http://localhost:8080/api | Workflow orchestration and task dispatch. |
| Conductor UI | http://localhost:5008 | Local workflow debugging. |
| MinIO | http://localhost:9000 | Local object storage for files and assets. |
| Prometheus | http://localhost:9090 | Metrics collection. |
| Grafana | http://localhost:3003 | Dashboards. |
Deployment Shape
Local service compose starts the core product by default:
monkeys-servermonkeys-studiomonkeys-kernelmonkeys-compute
Optional profiles add feature areas: agent, billing, data, webhook, mcp, worker, training, comfyui, tools, and sandbox.
Ownership Rules
monkeysowns ecosystem documentation, local infrastructure compose, services compose, and agent bootstrap guidance.- Each application or service repository owns its own source code, Dockerfile, config examples, tests, and build commands.
- Runtime configuration such as
config.yamlshould stay local and untracked. - Feature work should be tested in the owning repository before being published.