Installation model
Choose your deployment path
Select the installation model that matches your operating environment. The sizing table below updates for the selected model and analysis scope.
Selected model
Docker on VM
For single-host on-premise deployments where Oobeya runs on a dedicated VM or container host managed by your infrastructure team.
Notes
- Docker and docker-compose are required.
- Outbound image access is required for Oobeya Azure Container Registry. You can also use a registry mirror or download images and transfer them for offline installation.
For setup steps, view the installation guide .
Analysis scope
Select scale before reviewing the table.
| Area | Test / Minimum Proof-of-concept, validation, and low-volume non-production environments. | Standard Production Default starting point for the best cost and performance balance. | Scale / Performance Larger production environments, more integrations, higher analytics volume, or stricter availability expectations. |
|---|---|---|---|
| Target use | Test environment, demo, small pilot | Standard production environment | Large production environment or heavy analytics usage |
| Compute | 12 vCPU | 16 vCPU | 24+ vCPU |
| Memory | 32 GB RAM | 48 GB RAM | 64+ GB RAM |
| Disk | 250 GB SSD | 500 GB SSD | 1 TB+ SSD or expandable volume |
| Operating system | Modern Linux server distribution | Enterprise Linux or Ubuntu LTS with patching policy | Enterprise Linux with monitored filesystem, backup, and hardening baseline |
| Container runtime | Docker Engine + docker-compose | Docker Engine + compose plugin, managed as system services | Hardened container host with monitoring, log rotation, and backup automation |
| Network | HTTPS, DNS name, outbound access to required integrations and registries (oobeya.azurecr.io, oobeya.germanywestcentral.data.azurecr.io) | HTTPS, DNS name, outbound access to required integrations and registries (oobeya.azurecr.io, oobeya.germanywestcentral.data.azurecr.io) | HTTPS, DNS name, outbound access to required integrations and registries (oobeya.azurecr.io, oobeya.germanywestcentral.data.azurecr.io) |
| Backup | Manual VM or volume snapshot | Scheduled volume/database backups | Tested restore procedure, retention policy, off-host backup storage |
These sizing calculations are intended as directional guidance. Repository size, integration volume, analytics load, and retention expectations can increase resource requirements. We recommend starting with the suggested configuration and scaling resources as needed. For detailed sizing, contact the Oobeya team.
Need help validating your environment?
