DebutDeploy / platform
Deploy an app
Home Pricing Compare providers Platform pages Migrate FAQ Status Compare my bill Deploy an app
Managed Postgres Node.js hosting Python hosting Docker hosting European PaaS

/docker-hosting.html

Docker hosting

Your Dockerfile, built and run for you.

If it builds locally, it deploys here. Bring your own image definition and let the platform handle registry, placement, TLS, health checks, restarts and rollbacks.

Dockerfile builds · multi-stage · private base images · persistent volumes · isolated containers

Build from your Dockerfile
==> Dockerfile found at ./Dockerfile
==> Stage 1/2: builder · installing deps
==> Stage 2/2: runtime · copying artefacts
==> Image built: 182 MB
==> Pushing to EU registry
==> Starting container · 2 vCPU / 4 GB
==> Health check /health → 200 OK
==> Live · previous image retained
Build sourceDockerfile in your repo
RegistryEU-hosted, ours
Isolationone container per service
Volumespersistent disks supported

What container services get

buildmulti-stage ok

Standard Docker builds

Multi-stage builds, build arguments and private base images work as they do in your own CI.

isolationper-service

Genuine isolation

Every service runs in its own container with its own resource boundaries; dedicated plans do not share CPU with other tenants.

diskpersistent

Volumes

Attach a persistent disk where your container needs state that must outlive a deploy.

healthauto-restart

Health and restarts

Failing health checks stop a bad release from taking over, and crashed containers are restarted automatically.

networkprivate (beta)

Service-to-service

Private networking between your own services is in beta — useful for an API and worker pair that should not go via the public internet.

egress20 TB included

Transfer included

Container workloads that serve media or large API responses are not metered per gigabyte.

What a container costs

Containers are billed as the box they run on, not per image or per build. Multi-service applications are several plans; agencies and larger architectures are quoted directly.

See all plans and what is included →
Pro2 GB RAM · 1 vCPU · shared $15 /mo
Pro Plus4 GB RAM · 2 vCPU · dedicated $45 /mo
Scale8 GB RAM · 4 vCPU · dedicated $85 /mo
Custommulti-service and larger boxes POA /mo

USD per month, ex-VAT. No per-build, per-image or registry storage charge. 20 TB transfer included on every plan.

Deploying a container

01

Point at the repo

The Dockerfile is detected; set a different path or build context if needed.

dockerfile: ./docker/Dockerfile

02

Declare the port

Expose the port your process listens on and the platform routes to it.

EXPOSE 8080

03

Add a health check

A health endpoint lets deploys verify themselves before taking traffic.

healthcheck: GET /health

Container questions

Building from your repository is the supported path today. If you need to deploy an image from your own registry, ask us — it is handled case by case.

Yes, with registry credentials stored as encrypted environment values.

Not as a single file. Each service in a compose file becomes its own DebutDeploy service, which is usually a cleaner production shape anyway.

Service-to-service private networking is in beta. Say so during a migration review and we will confirm your case before you commit.

Nothing you are likely to hit with a sensible multi-stage build. Very large images slow deploys down rather than being rejected.

More operational detail is on the full FAQ page.

Build one image and run it here.

If your Dockerfile builds on your machine, it will build here. Try it on a test service before moving production.

Deploy a test application Speak to a migration engineer

Keep your existing service online while you evaluate DebutDeploy.