$0/ month
A workspace, three services and three databases, and $10 of infrastructure credit waiting when you sign up.
- Workspaces
- 1
- Services and databases
- 3 each
- Custom domains
- Not included
- Included usage
- $10 credit, once, at signup

Pricing
A plan fee you can memorise, and infrastructure metered at rates we print on this page. No quote, no sales call, and no per-seat charge for the people you work with.
No card required to start.
$0/ month
A workspace, three services and three databases, and $10 of infrastructure credit waiting when you sign up.
$5/ month
Every limit removed. Infrastructure is metered separately at the rates below.
Most teams land here
$20/ month
Everything in Hobby, and the fee comes back to you as usage. Below $20 of consumption, the plan is the whole bill.
What “unlimited” means. Dockup does not cap how many workspaces, deployments, databases or machines you create. What you run still consumes compute, storage and bandwidth, and that is metered at the rates below.
Metered infrastructure
Sampled every minute and drawn from your balance. A service that runs six hours a day is billed for six hours a day.
| Resource | Rate | In practice |
|---|---|---|
| Compute | $0.02778 / vCPU-hour | ≈ $20.28 per vCPU, per month |
| Memory | $0.01386 / GB-hour | ≈ $10.12 per GB, per month |
| Persistent storage | $0.10 / GB-month | Volumes and database disks |
| Network egress | $0.09 / GB | Inbound traffic is free |
| Build minutes | $0.007 / minute | Only while an image is building |
Worked examples
The same three workloads on each paid plan, using the rates above. Rounded to the cent, not to the argument.
| Workload | Infrastructure | On Hobby | On Pro |
|---|---|---|---|
| A side project0.25 vCPU · 512 MB | $10.13 | $15.13 | $20.00 |
| A small production service0.5 vCPU · 512 MB | $15.20 | $20.20 | $20.00 |
| An app and its database1 vCPU · 2 GB · 10 GB disk | $41.52 | $46.52 | $41.52 |
The crossover is $15. Below roughly $15 of monthly infrastructure, Hobby costs less. Above it, Pro does — and past $20 of usage Pro is cheaper by the $5 difference in fees, every month, because the Pro fee comes back as credit.
Compared
Compute and memory cost roughly the same everywhere — everyone is renting the same machines. What separates the bills is seats, and what the platform will run at all.
| Compared on | Dockup | Railway | Render | Vercel | Supabase |
|---|---|---|---|---|---|
| Entry paid plan | $5 | $5 | $0 | $0 | $0 |
| The plan most teams buy | $20 | $20 | $25 | $20per seat | $25 |
| Charged per team member | No | No | No | Yes — $20 each | No |
| Unit rates published | Yes | Yes | Per instance size | Per unit | Per unit |
| Linux VMs with root | Yes | No | No | No | No |
| Windows VMs over RDP | Yes | No | No | No | No |
| Deploy to servers you own | Yes | No | No | No | No |
| EU region | Yes | Limited | Yes | Yes | Yes |
Competitor figures are their published list prices as of August 2026 and change without warning — check theirs before you decide. Ours are on this page because we would rather you did the arithmetic than took our word for it.
Four teams, four different reasons. The one that matches yours is the one worth reading.
We started using dockup.ai because we wanted to spend less time dealing with servers and deployment configuration. Connecting our Git repository and getting the application live was surprisingly straightforward. SSL, domains and deployments are handled for us, which saves a lot of time compared to managing everything manually.
The biggest advantage for me is how well Dockup fits into an AI-assisted development workflow. I use Claude Code and Codex regularly, and with the Dockup CLI they can actually interact with our deployments instead of just generating commands for me to run. Being able to deploy, check status and inspect logs from the CLI is a huge improvement.
We previously had several different tools for CI/CD, hosting, databases and monitoring. Dockup has simplified that setup considerably. We can deploy our services, manage environment variables, check deployment history and access logs from one platform. For a small engineering team, that makes a real difference.
The PR preview functionality has become one of our favorite features. Every time we work on a larger change, having an isolated preview environment makes it much easier to test before merging. It has made our development and review process noticeably faster.
I wanted to launch our application without spending days learning Docker, servers and complicated CI/CD configuration. Dockup made the process much easier. We connected our repository, configured the environment and had a working production deployment very quickly. Exactly what I was looking for as a founder.
I initially expected Dockup to be mainly a simple deployment platform, but the CLI is actually quite powerful. Being able to inspect services, deployments, environment variables and runtime logs directly from the command line works very well for our automation. The structured JSON output is especially useful in scripts and agent workflows.
Being able to deploy a database alongside the application is extremely convenient. We use PostgreSQL and no longer have to set up a separate database infrastructure just to get a new project running. It makes spinning up new environments much faster.
We have several applications running through Dockup and the deployment workflow has been very smooth. The zero-downtime approach is particularly important for our production services. We can push updates without having to manually coordinate the deployment process every time.
I build and launch products fairly quickly, so I don’t want to spend my time managing infrastructure. Dockup gives me a simple path from code to a live application. I especially like that I can add a database, configure the domain and deploy without setting up a complicated server environment myself.
What convinced us about Dockup is the combination of a straightforward deployment platform and the ability to work with AI coding agents. Our developers can build with Claude Code or Codex and then use Dockup to handle the deployment and operational side. It feels much closer to how modern development teams actually want to work.
Reviews are published with permission and shown in full. “Verified customer” means Dockup confirmed the reviewer uses the platform — these are not collected by an independent review service.
Before you commit
On Pro, consumption past the first $20 is billed at the rates above — nothing stops. On Free, the $10 is a one-time balance, and services pause rather than running up a bill you did not agree to.
Below about $15 of monthly infrastructure, Hobby is cheaper. Above it, Pro is — and once you pass $20 of usage, Pro is cheaper by exactly the $5 difference in fees, every month. You can change plans without redeploying anything.
No. A workspace costs the same with one person in it or twelve. Adding a colleague adds no fee.
No. It does not expire and does not need a card. The $10 of infrastructure credit is granted once at signup, and the plan limits — one workspace, three services, three databases — are what the platform enforces.
CPU, memory and disk are sampled per minute, so a service that runs for six hours is billed for six hours. Idle capacity you reserved but did not use is still reserved capacity, and is charged as such.
Your code is in your Git repository and your databases dump with standard tools. There is no proprietary format to unwind and no exit fee. Cancel from the dashboard and billing stops at the end of the period.
Ten dollars of infrastructure is already there, no card is required, and nothing here needs a conversation with us first.