Linux
Ubuntu 22.04 and 24.04, Debian 12, Alpine 3.20
You reach it over
ssh dockup@worker-01One deployment platformfor everything you
Deploy apps, databases, and virtual machines from Git or straight from your AI coding agent.
Works with the tools your agents already use
Grok Build
Claude Code
Codex
Cursor
OpenCode
GitHub Copilot
Pi
GitHub deployments
From repository
to production.
Connect GitHub once. Every approved change becomes a repeatable deployment — built in isolation, verified before it takes traffic, and reversible from the same screen.
Production branchacme / agent-api
mainDeploy on every push, or hold each release for manual approval.
- Commit lands
Dockup watches the branch you nominated. Git stays the source of truth — there is no separate state to keep in sync.
- Built in isolation
Dependencies cached, variables applied, the image assembled away from whatever is currently serving.
- The gate
Nothing moves until the new version answers. If it never does, your users never see it — the release stops here.
- Traffic switches
The new version takes the domain. The previous one is held, so rolling back is a switch rather than a rebuild.
The same twenty seconds, either way
Then it is one service, not six tools
- Runtime and build logs
- CPU, memory and disk
- Custom domains and TLS
- Environment variables
- Redeploy any commit
- Roll back in one click
Managed databases
Your database,
ready for production.
PostgreSQL, MySQL, MongoDB or Redis, provisioned with credentials, TLS and encrypted storage — and reachable only from inside your workspace until you decide otherwise.
Pick an engine
PostgreSQL17 · 16 · 15
MySQL8.4 · 8.0
MongoDB8 · 7
Redis7
Version, region, CPU and memory, and encrypted storage are chosen at creation and changed later without rebuilding.
- Reachable at
main-db.internal:5432Your services resolve it by name over TLS, with credentials Dockup generates and injects into the ones that need them.
- From the internet
- No route by default.
There is no public hostname to firewall, because there is no public hostname. Open one deliberately when an outside client genuinely needs it.
Provisioning one, either way
Day two, from the same screen
Connections14 / 100
Storage6.8 / 25 GB
Last backupToday, 03:00 UTCEncrypted · 7 retained · restore to a new database
- Read-only users, scoped per person
- Browse and query from the dashboard
- Move to another region without a dump
Virtual machines
Your operating system.
Your rules.
A whole machine with root on it — Linux or Windows — provisioned in under a minute and already sitting on the same private network as your apps and databases.
Windows
Windows Server, full desktop
You reach it over
RDP, on a tunnelled portEither one, on the same canvas
Identical either way
- Private network
workspace.internal- The machine resolves your apps and databases by name. It is not a separate island you have to connect back.
- Capacity
- 4 vCPU · 8 GB · 80 GB NVMe
- Resized later without rebuilding. The disk persists across restarts.
- Provisioning
- 38 seconds, typical
- Ports you open are yours to choose. Nothing is exposed that you did not ask for.
Cloudflare domains
Connect the zone.
Route every service.
Connect a Cloudflare account once, with a token scoped to just two permissions. After that a hostname becomes a live HTTPS endpoint from one line — without opening Cloudflare again.
acme.comConnected zone · auto-synced
- Zone:Read
- DNS:Edit
Those two are the whole grant. Dockup cannot read your other zones, change your account, or touch anything it was not given.
One line, either way
What that produced
DNSA CNAME in your zone
Written through the scoped token. Propagation is typically under a minute.
RouteHostname to service
api.acme.com reaches agent-api on port 3000, and keeps following it through redeploys.
TLSA certificate, renewing
Verified and reissued on its own. There is no step where you upload anything.
Remote servers
Bring your servers.
Automate every release.
Your machine stays yours. Register it over SSH, write the steps you already run by hand once, and Dockup executes them in order — keeping the output, the timings and the exit code.
production-web-01203.0.113.42 · deploy@22 · key-based
Nothing is installed on the box and nothing migrates. Dockup connects as a user you scope, over a key you provide.
The same task, either way
- A failure stops the runThe step that broke is the last one attempted, and the output it produced is what you read.
- Every past run is keptCommands, durations, exit codes and output, per run.
- Tasks are reusableRestart a service, take a backup, run a migration — saved once, run from anywhere.
- Several servers, one placeStaging, workers and production sit in the same list with their own tasks.
Simple pricing
The platform stays simple.
You only pay for what runs.
The plan buys you the platform. Infrastructure — compute, storage, bandwidth — is metered separately, and no paid plan caps how many workspaces, deployments, databases or machines you create. Free starts you with $10 of it.
$0/ month
Sign up and $10 of infrastructure credit is already there. Enough to run something real before you decide anything.
- Workspaces
- 1
- Services and databases
- 3 each
- Custom domains
- Not included
- Infrastructure usage
- $10 credit on signup
$5/ month
A full workspace with nothing counted against you.
- Workspaces
- Unlimited
- Services and databases
- Unlimited
- Custom domains
- Unlimited, with TLS
- Infrastructure usage
- Billed on top
$20/ month
Everything in Hobby, and the fee comes back as usage.
- Workspaces
- Unlimited
- Services and databases
- Unlimited
- Custom domains
- Unlimited, with TLS
- Infrastructure usage
- First $20 included
$20 plan−$20 usage credit=$0if you already spend $20 a month on infrastructure
Choose ProAdd-on
Bring your own servers
Run Dockup on hardware you already pay for. One command on your machine attaches it to your account, and only your account: nobody else is ever scheduled onto it. You keep the server and its bill; we license the platform and give it a domain.
- Your machines, visible only to you
- Same deploys, domains, TLS and databases
- Works with any plan, or on its own
What “unlimited” means. Dockup does not cap how many workspaces, deployments, databases or virtual machines you create. What you run still consumes compute, storage and bandwidth, and that is metered — Pro simply covers the first $20 of it each month.
What teams say after they move
Ten reviews from people running production on Dockup. Published in full, in their words.
Finally, deployment without the infrastructure headache
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.
Daniel WeberFounder & CEOVerified customer Great workflow for AI-assisted development
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.
Michael CarterFull-Stack DeveloperVerified customer Much simpler than managing our own deployment stack
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.
James WilsonCTOVerified customer PR previews are incredibly useful
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.
Alex ThompsonSoftware EngineerVerified customer From Git repository to production in minutes
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.
Robert MillerStartup FounderVerified customer Surprisingly powerful CLI
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.
Chris AndersonDevOps EngineerVerified customer Databases without another infrastructure project
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.
Kevin BrownProduct EngineerVerified customer Zero-downtime deployments actually make a difference
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.
Thomas EvansEngineering ManagerVerified customer Perfect for shipping quickly
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.
Ryan JohnsonIndie HackerVerified customer A very good fit for modern development teams
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.
Matthew DavisHead of EngineeringVerified customer
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.