How to Deploy a Docker Container on ComputeSphere

If your app already builds into a Docker image, you don't need a buildpack, a Procfile, or a framework-specific platform. ComputeSphere runs your image as-is on a fixed per-spherelet price — point it at a registry, set the port, and you have a live HTTPS service.

This guide deploys an existing Docker image to production, then covers environment variables, a custom domain, and autoscaling.

Before you start

• A Docker image (or a Dockerfile that builds one)
• A registry to push to — Docker Hub, GHCR, Quay, or a private registry
• A free ComputeSphere account — the trial runs 14 days, no card required

Install the csph CLI

brew install computesphere/tap/csph
# or
npm install -g @computesphere/csph

Then sign in:

csph auth login

Build and push your image

Build, tag, and push to your registry:

docker build -t my-app:1.0.0 .
docker tag my-app:1.0.0 registry.example.com/my-app:1.0.0
docker push registry.example.com/my-app:1.0.0

Deploy the image

Deploy what you just pushed:

csph deploy --image registry.example.com/my-app:1.0.0

ComputeSphere pulls the image, runs it on a spherelet, terminates TLS, and returns a public URL:

https://copper-lynx.computesphere.app

Specify the port your container listens on. For a private registry, add your credentials in the Console first, then deploy.

No image yet? Build and deploy in one step

If you have a Dockerfile but haven't pushed an image, run csph deploy from the project directory instead — ComputeSphere builds the image and deploys it in a single step.

Set environment variables

Pass config and secrets to your container at runtime:

csph services set-env LOG_LEVEL=info
csph services set-secret DATABASE_URL=postgres://user:pass@host:5432/db

Add a custom domain

Open Console → Domains, add your hostname, and create the CNAME it shows pointing to your service URL:

Type    Name    Value
CNAME   app     copper-lynx.computesphere.app

ComputeSphere issues and auto-renews the SSL certificate for you.

Scale with spherelets

A spherelet is your unit of compute, and you pay a fixed price per spherelet — no per-seat fees, no surprise bandwidth charges. Pick a size (Flex, Standard, or Performance), run as many spherelets as you need, and turn on autoscaling with a minimum, a maximum, and a target CPU.

Wrap-up

Any container that runs locally runs on ComputeSphere: push the image, run csph deploy --image, set the port, and you have HTTPS, custom domains, and autoscaling on pricing you can predict.

• See how per-spherelet pricing works
• Compare ComputeSphere and Render
• Follow the 5-minute Quickstart
• Browse runnable examples (each ships as a container) on GitHub

Ready to ship? Start your free trial or book a 15-minute demo.