Skip to content

Web Services

Available

A Web Service is a long-running container — your API, full-stack app, worker behind HTTP, anything that needs a process and CPU/RAM. Optionally attach a persistent disk that survives restarts.

Each service gets a free *.runsite.app subdomain and can serve any custom domain you attach.

Pricing & plans

Comparing options or looking for the free tier? See plans, specs and pricing on the Web Services hosting page.

Runsite always runs your app as an isolated Docker container. You ship one in two ways:

  • From a Git repo — push your code, we build the image. We use your Dockerfile if there is one, otherwise we auto-detect the stack (Node, Python, Go, Java today).
  • From a registry image — point at any public or private Docker image.

Supported Git providers: GitHub, GitLab, Bitbucket.

For the full platform model — deployment lifecycle, deploy states, ephemeral filesystem, health checks — see Runtime.

Most stacks need only a few lines. Pick your runtime — Minimal gets you to a first deploy, Production is a multi-stage build with smaller images and faster cold starts.

FROM node:20-alpine
WORKDIR /app
COPY package*.json ./
RUN npm ci --omit=dev
COPY . .
EXPOSE 8080
CMD ["node", "server.js"]

The default port is 8080. If your app listens elsewhere, change it in Settings → Build & Deploy.

Don’t have a Dockerfile and your stack is one of Node, Python, Go or Java? Push without one — Runsite will detect the project and build it for you.

  • Runtime — container model, lifecycle, states, storage, health checks.
  • Deploying — auto-deploy from Git and manual actions.
  • Dashboard — what every tab does.
  • Domains — default subdomain and custom domains.
  • Scaling & resources — CPU, RAM, disk, autoscaling, sleep.

Front-end only?

If your project is a static site (React SPA, Astro, Hugo, plain HTML), use Static Sites instead — simpler, served from the edge, always-on.