Technical requirements
Oobeya on-premise infrastructure requirements
Choose your deployment model and engineering scale to compare minimum, standard production, and performance configurations. Use these values as a sizing baseline for your infrastructure planning.
Deployment sizing
Configure your deployment
Select an installation model, developer count, and repository scope. The capacity comparison updates with your selections.
Pilot, small team, or limited rollout
Small or pilot repository scope
Docker on VM
For single-host on-premise deployments where Oobeya runs on a dedicated VM or container host managed by your infrastructure team.
Showing Docker on VM requirements for 0-100 developers and 0-250 repositories.
Scroll horizontally to compare all three configurations.
| Area | Test / MinimumProof-of-concept, validation, and low-volume non-production environments. | Standard ProductionDefault starting point for the best cost and performance balance. | Scale / PerformanceLarger 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 | 4 vCPU | 8 vCPU | 16+ vCPU |
| Memory | 16 GB RAM | 16 GB RAM | 32 GB RAM |
| Disk | 100 GB SSD | 250 GB SSD | 500 GB+ 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 |
Sizing guidance. Repository size, integration volume, analytics load, and retention expectations can increase resource requirements. Start with the suggested configuration and scale as needed. Contact the Oobeya team to validate detailed production sizing.
Installation notes
Prepare for Docker on VM
Deployment-specific prerequisites for the selected installation model.
Read the installation guide- 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.
Platform checklist
Confirm before installation
These items apply across Docker, Kubernetes, Helm, and OpenShift deployments.
- DNS name or stable IP for Oobeya browser access
- TLS certificate and HTTPS termination plan for production
- Outbound network access to required SCM, issue tracking, CI/CD, code quality, identity, and observability systems
- Outbound registry access to Docker Hub and/or oobeya.azurecr.io, or approved internal registry mirroring
- Backup and restore procedure for persistent data
- Monitoring for host, pod, storage, ingress, and application availability
- SSO, identity provider, and access-control plan where enterprise authentication is required
- Retention and storage-growth policy aligned with repository volume and integration frequency
Validate your deployment plan
Share your infrastructure, repository scope, and operational requirements with the Oobeya team.