DOCKER HOSTING

Run your containers. We run the server.

If your app ships as a Docker image or a Compose file, we can host it: HTTPS and Cloudflare in front, persistent volumes for data, and backups. Pricing is per project, in LKR, agreed before we start.

USE CASES

When containers are the right fit.

  • Your app needs system packages that a standard Node.js or PHP setup doesn't have — image processing libraries, headless Chrome, a specific Python version.
  • It's more than one service — an API, a worker and a queue that have to run together.
  • You already run it with Docker Compose locally or in CI and want production to match.
  • You want to stay portable — a standard image runs on any host, so you aren't locked in.

If your project is a single Node.js app or a WordPress site, a regular plan is simpler and cheaper — see Node.js hosting or pricing.

PLANNING

What to think about before going live.

Resources

Know roughly how much memory each container uses under load. Set limits so one runaway service can't starve the others. We size the quote from this.

Persistent data

Anything written inside a container disappears when it's replaced. Databases, uploads and other state belong on volumes, and those volumes need backups that you have tested restoring.

Networking

Only the web-facing service should be reachable from the internet. Databases and internal services stay on a private network between containers.

Security

Pin image versions, keep secrets in environment variables rather than baked into images, run as a non-root user where you can, and rebuild regularly to pick up base-image fixes.

Deployment

Updates should be a deliberate version change you can roll back: build and tag a new image, deploy it, and keep the previous tag. Our production Docker checklist has a Compose example for each point.

HOW IT WORKS

From Compose file to running app.

  1. Send us what you have — a repository link, Dockerfile or compose.yaml, plus a sentence on what the app does and the traffic you expect.
  2. We quote in LKR based on the CPU, memory and storage it needs.
  3. We set it up with HTTPS, Cloudflare, volumes and backups, and point your domain at it.
  4. You ship updates by publishing new image versions; we help with the deploy flow if you need it.

Need help containerising an app in the first place? That's part of our deployment help.

FAQ

Docker hosting questions.

How much does Docker hosting cost?

It depends on the CPU, memory and storage your containers need, so there's no fixed plan. Send us your Compose file or a description of the services and we'll quote a monthly price in LKR before anything is set up.

Do I get root access to the server?

No. We run the host and the container runtime; you supply the images and configuration. If you need a server you fully control, that's a self-managed VPS, which we don't sell — but we can help you set one up.

Can I run a database in a container?

You can, with its data on a persistent volume that is backed up. For many apps a managed MySQL or PostgreSQL database is simpler; we'll suggest whichever fits.

My app runs on Docker Compose locally. Will it work?

Usually, with a few production changes: pinned image versions, restart policies, volumes for data, secrets in environment variables and only the web-facing port exposed. Our production Docker checklist covers each one.

Get a price for your containers.

Send your Compose file or repo on WhatsApp. We'll reply with a monthly price in LKR.

Get a quotein LKR