Run apps, VMs, and databases
on hardware you already own.
Kumo is a self-hosted control plane for applications, virtual machines, databases, and CI pipelines. Point it at a server you control, click through a form, get production workloads. No proprietary APIs.
What's in the box
One dashboard for compute, ingress, data, and pipelines. The plumbing is wired up so you can focus on shipping.
Drop-in applications
Pick an image, pick a port, click deploy. A small catalog of common workloads (Grafana, n8n, MinIO, WordPress, Plane and more) lands in one click.
Containers and VMs together
Launch container workloads or full virtual machines (Ubuntu, Debian, Rocky, Alma) from the same place. Snapshots, backups, and resize are built in.
Managed databases
PostgreSQL, MySQL, MariaDB, MongoDB. Auto-generated credentials, optional read replicas, metrics on a toggle.
GitHub-driven builds
Push to a branch, Kumo builds the image and ships it to GHCR or your private registry. Auto-deploy rules cover each environment.
Custom domains, automatic TLS
Point a domain at a workload. Route several ports through one host. HTTPS is handled by the edge proxy. No certbot, no nginx config to edit.
Shared storage
Buckets backed by CephFS, mountable into any workload. No external object store to wire up.
Observability toggles
Prometheus and Loki forwarding are checkboxes, not config files. On for metrics, off to save resources.
Secrets sealed at rest
Env vars marked secret are encrypted with Fernet before they hit Postgres. Audit logs scrub them automatically.
Workspaces and roles
Workspace-scoped permissions you can customize. Invite teammates, hand out roles, revoke in one click.
From bare server to production in three steps
No SPA to learn, no IAM maze. Bring a box you own and Kumo wires up the rest — open-source virtualization and routing under the hood, nothing proprietary to lock you in.
Point Kumo at your server
Bring a box you control — bare metal or a VPS running Ubuntu, Debian, Rocky, or Alma. Kumo installs the control plane and takes it from there.
Pick what to run
Choose an app, VM, or database from the catalog. Set a port and a domain, click Create. TLS, routing, and credentials are handled for you.
Ship and watch
Push to GitHub to rebuild, flip on metrics and logs when you need them, and invite your team with scoped roles.
Kumo vs. public cloud
Same outcomes: apps on a custom domain, with metrics, logs, and a database behind them. The difference is who owns the bill and the box.
Public cloud (AWS, GCP, Azure)
- Monthly bill
- Variable. Egress, NAT, balancer hours all meter.
- Vendor lock-in
- High. Proprietary APIs across the stack.
- Data residency
- In their region.
- Time to first deploy
- Days. IAM, VPC, RDS, load balancer first.
- 1 small DB + 2 VMs / month
- Around $80 to $200.
- Edit a setting on the move
- Console with 14 nested tabs.
Kumo on your own hardware
- Monthly bill
- Flat. Your hardware plus power.
- Vendor lock-in
- None. Open-source virtualization and routing underneath.
- Data residency
- Wherever the server lives.
- Time to first deploy
- Minutes. Pick an image, click Create.
- 1 small DB + 2 VMs / month
- $0 incremental on a box you already own.
- Edit a setting on the move
- A few tabs, redeploy in seconds.
See Kumo running on real hardware
Book a 20-minute walkthrough. We'll show your kind of workloads live on a box you'd actually run, and answer the "how hard is this to stand up?" question directly — no surprise bill at the end.
Book a demoFrequently asked questions
What is Kumo by Dalang?
Kumo is Dalang's self-hosted cloud control plane for running apps, VMs, databases, and CI/CD on hardware you own. It gives teams a dashboard and API to operate their own infrastructure, combining hyperscaler-style control with self-hosting freedom, a flat monthly cost, and zero vendor lock-in.
How is Kumo different from a public cloud?
Kumo is a self-hosted control plane that runs on hardware you control rather than a public-cloud vendor's managed platform. Workloads and data stay on the servers you choose, the platform uses flat monthly pricing, and the underlying virtualization and routing stack is based on open components.
Who should use Kumo?
Kumo suits platform teams, MSPs, and businesses that want to operate cloud infrastructure with their own control plane rather than a hyperscaler console. It fits organizations needing data residency, self-hosted orchestration, or to offer cloud services to their own users while keeping management under their direct control.
Can I run Kumo on my own hardware?
Yes. Kumo can be installed on a baremetal server or VPS you control, including Dalang baremetal. The current product page lists Ubuntu, Debian, Rocky Linux, and AlmaLinux as supported operating systems; capacity and network requirements should be confirmed before deployment.
What can I run on Kumo?
Kumo runs applications, virtual machines, managed databases, and CI/CD pipelines from a single self-hosted control plane. Teams deploy and operate their whole stack on their own hardware, replacing several separate tools with one platform at a flat monthly cost and no per-service metered fees.