Skip to content
Why pay for a free tier that sleeps?Free always-on tier — never sleeps

Docker Compose

Deploy your whole docker-compose.yml

The compose file you already run locally becomes a production deployment — private networking, shared env, and autoscaling.

Docker Compose

Your docker-compose.yml is the deploy config.

Stop rewriting infra for every platform. Runko reads the compose file you already run locally and provisions each service — private networking, shared env, health checks, autoscaling.

  • Multi-service stacks deployed as one unit
  • depends_on becomes real startup ordering
  • Private service-to-service networking by default
  • Per-service scaling, logs and metrics
Join waitlist for Compose
docker-compose.yml
services:
web:
build: ./web
ports: ["3000:3000"]
depends_on: [api, redis]
api:
build: ./api
environment:
DATABASE_URL: ${DATABASE_URL}
worker:
build: ./worker
command: celery -A app worker
redis:
image: redis:7

From compose file to cloud in four steps

01

Point Runko at your repo

Connect GitHub or GitLab, or run runko init locally. We detect your docker-compose.yml automatically.

02

We parse every service

Each service becomes its own scalable workload. build:, image:, ports:, environment:, depends_on: and volumes: are all honored.

03

We build and provision

Images build in parallel and land in the registry. Services boot in dependency order on a private network.

04

Ship & scale

Get one URL for your web service, autoscaling per service, and unified logs and metrics across the whole stack.

How compose maps to Runko

services:One deployable workload per service
build: ./apiBuilt with your Dockerfile
image: redis:7Pulled and run as a managed workload
ports: ["3000:3000"]Exposed publicly with free TLS
depends_on: [db]Real startup ordering + health gates
environment:Injected as encrypted env vars / secrets
volumes:Backed by persistent disks
deploy.replicasSets baseline instances + autoscaling

Idle hosting shouldn't cost a starter plan.

Free always-on: one web service, Postgres, and Redis under fair-use quotas. No sleep cycle. No $5 bill just to keep a test env alive.