Deployment
Deploy anywhere, in minutes
On-premises, cloud, or hybrid — DINOC runs wherever your infrastructure lives. Container-native with Docker and Kubernetes support out of the box.
On-Premises
Full control. Deploy DINOC entirely within your own infrastructure. Ideal for regulated industries, air-gapped networks, and organizations with strict data sovereignty requirements.
Deployment Steps
- 1Install Docker or Kubernetes on your server
- 2Pull the DINOC container images from our registry
- 3Configure the .env file with your database and secret settings
- 4Run docker compose up (or apply the Helm chart)
- 5Access the DINOC UI at your server IP within minutes
Cloud
Deploy DINOC to your cloud provider of choice — AWS, GCP, Azure, or any VPS. Agents still run on-prem if needed; only the server lives in the cloud.
Deployment Steps
- 1Provision a VM or managed Kubernetes cluster
- 2Deploy DINOC Server via Docker Compose or Helm
- 3Configure a managed Postgres database (e.g. Neon, AWS RDS)
- 4Install DINOC Agents on devices — they connect back over mTLS
- 5Access the UI via your cloud VM public IP or a custom domain
Hybrid
Run the DINOC Server in the cloud while agents remain on-premises. Agents push metrics over mTLS — no inbound firewall ports required on the agent side.
Deployment Steps
- 1Deploy DINOC Server in your cloud environment
- 2Install DINOC Agents on on-prem devices
- 3Agents initiate outbound mTLS connections to the server (no inbound NAT required)
- 4Metrics flow from on-prem agents to cloud-hosted VictoriaMetrics
- 5Access the UI from anywhere via the cloud-hosted server
Minimum system requirements
| Component | CPU | RAM | Storage | Notes |
|---|---|---|---|---|
| DINOC Server | 2 vCPU | 4 GB | 20 GB SSD | Scales with device count |
| VictoriaMetrics | 2 vCPU | 4 GB | 50 GB SSD | Storage grows with retention |
| Ollama (AI) | 4 vCPU | 8 GB+ | 10 GB | GPU accelerated recommended |
| DINOC Agent | 0.1 vCPU | 128 MB | 50 MB | Per monitored host |
| Database (Postgres) | 1 vCPU | 2 GB | 10 GB | For configuration + metadata |
* Requirements vary with device count, metric cardinality, and retention period. Contact us for sizing guidance for large deployments (>10,000 devices).