Fixed-Price Kubernetes Cloud for Developers
Run virtual machines, Kubernetes clusters, managed databases, object storage and networking in one resource pool. Manage it through native manifests, an AI-assisted workflow, or a real-time Web Console. Plans start at €19/month.
14-day free trial · card required, not charged · cancel anytime
one resource pool for your entire stack
You start by choosing a fixed amount of CPU, RAM, NVMe storage, object storage and IPv4 addresses. That pool becomes the home for everything you run: applications, virtual machines, managed databases and Kubernetes clusters all draw from the same capacity.
Create as many supported objects as fit within your pool capacity and platform limits. Kube-DC brings compute, storage and networking together on a single Kubernetes-native control plane, so you're not stitching together separate services for each part of your stack.
code it, click it or build with AI assistance
Choose your workflow. Whether you're an AI enthusiast, a DevOps engineer, or a visual manager, Kube-DC adapts to your style.
The Kube-DC Web Console — real-time monitoring and management of your entire infrastructure
ai-assisted workflow
Kube-DC provides context files for tools like Cursor and Windsurf. Describe what you want — for example, "deploy a PostgreSQL cluster" — and the tool prepares a manifest for you to review and apply.
kubernetes-native workflow
Everything on Kube-DC is a CRD. Manage virtual machines and networks the same way you manage any other Kubernetes object, using kubectl, Helm, or your existing GitOps pipeline.
web console
Prefer a graphical interface? The Web Console shows workloads, metrics, logs, networking, databases and storage in one place — no terminal required.
everything you need to deploy and operate an app
vms, containers and helm charts
Deploy from Helm charts or raw YAML, or run a full virtual machine with VNC console, SSH access and live migration.
managed postgresql and mariadb
Automated backups and failover, so your app has a place to store data from day one.
private networking and public access
Each project gets isolated networking, with the option to expose services publicly when ready.
nvme and s3-compatible storage
Persistent volumes on local NVMe, plus S3-compatible object storage for files and backups.
ingress, tls and domains
Point a domain at your app and Kube-DC handles the certificate — reachable over HTTPS without extra setup.
projects, roles and access control
Organize work into projects with role-based access, so teams can share a pool safely.
built for builders and real workloads
ai-built apps and agent backends
Host an AI agent or a backend generated with Cursor or Windsurf alongside its database and API.
saas backends and microservices
Run a handful of services, a database and an ingress together, and grow within your pool's capacity.
development and test environments
Spin up a short-lived environment for a feature branch or staging without a separate account.
databases and stateful applications
Combine a managed PostgreSQL or MariaDB instance with persistent volumes for stateful workloads.
pay for pool capacity, not every object
Your plan includes a set amount of CPU, RAM, NVMe storage, object storage and IPv4 addresses. Running workloads draw on your CPU and RAM quota. Persistent volumes and stored files draw on your storage quota.
How many objects you can run depends on how much of that capacity they use — not on how many objects you create.
Example: a single pool can hold an application, a database, a background worker and a test VM, as long as their combined resource requests stay within your selected capacity. Ingress, TLS and load balancing don't carry a separate charge.
what counts against your pool
| counts against your pool | not billed per object |
|---|---|
| CPU and RAM requested by running workloads | Virtual machines — any number that fits |
| Persistent volume (NVMe) capacity | Managed databases — any number that fits |
| Object storage used | Managed Clusters — any number that fits |
| Public IPv4 addresses (1 / 1 / 3 by plan) | Projects, namespaces, users and roles |
| Managed Cluster worker nodes (they reserve their requested CPU and RAM) | Ingresses, TLS certificates, network policies, S3 buckets |
| — | Egress traffic — unlimited 1 Gbit/s on every plan |
| — | Stopped VMs — no CPU or RAM held; only the disk still counts |
Technical ceilings sit far above what the RAM allows: 100 / 200 / 500 pods and 100 load balancers on Dev / Pro / Scale.
start with a pool that fits your workload
dev
A first app, an MVP, a team of one.
pro
SaaS backends and small teams.
scale
Multi-service platforms.
what can fit in one pool?
A typical Pro Pool can hold:
- a web application
- an API or background worker
- a PostgreSQL database
- a caching layer
- the ingress and TLS certificate that make it all reachable over HTTPS
- — with capacity left over.
This is one illustration, not a guarantee: actual usage depends on the resource requests of your specific workloads.
hosted in amsterdam for european workloads
Kube-DC runs out of the AMS-1 facility in Amsterdam, on a storage and networking platform built for European workloads. Full facility, security and compliance details are below and on Kube-DC.
AMS-1 · Amsterdam
enterprise iron. developer soul.
Hosted in Amsterdam (AMS-1)
ams-1 region
Tier-3 compliant facility with a 99.99% power uptime guarantee.
data sovereignty
Your data never leaves the EU.
nvme based
Enterprise-grade SSDs for zero-wait state databases.
physical security
24/7 on-site security, biometric access control, and redundant cooling.
All systems operational • Amsterdam, Netherlands
a cloud platform built for the way developers work
-
Kube-DC gives you Kubernetes-native workflows you likely already know — kubectl, Helm, manifests — instead of a proprietary deployment model.
-
Its capacity model is fixed and predictable: you know your monthly cost before you deploy anything.
-
Because applications, databases, storage and networking share one interface, you're not jumping between separate dashboards to see the state of your stack.
Explore Kube-DC through VSYS Host to see whether it fits your next project, then continue to kube-dc.cloud for full documentation, pricing and a trial.
ready to explore kube-dc?
Pricing, account creation and service terms are available on kube-dc.cloud.
14-day free trial · card required, not charged · cancel anytime
Read kube-dc documentationkube-dc cloud faq
A fixed-price Kubernetes cloud platform. Choose a resource pool with set CPU, RAM, NVMe, object storage and IPv4, then run VMs, containers, managed databases and Kubernetes clusters inside it.
Not in the traditional sense. A standard pool runs in its own namespace with quotas, RBAC and network isolation — logical isolation on shared infrastructure, not dedicated hardware.
Applications, background workers, VMs, managed PostgreSQL or MariaDB, and Kubernetes clusters — as long as combined resource requests fit your pool's capacity.
A fixed monthly price for your pool's capacity. Running workloads draw on that capacity rather than being billed per object.
Yes. Kube-DC provides context files for AI-assisted coding tools, which help generate manifests you review and apply yourself.
Yes. Kube-DC resources, including VMs and networks, are exposed as Kubernetes custom resources.
Yes. Run full virtual machines alongside containers, and use managed PostgreSQL or MariaDB in the same pool.
The AMS-1 facility in Amsterdam, the Netherlands.
Instant kubeconfig access. Exact trial terms, including card requirements and cancellation policy, are listed on Kube-DC.
Full pricing, technical ceilings and pool rules are maintained on kube-dc.cloud.
