Runex

Deploy

Deploy any web app from GitHub.

Runex deploys Next.js, Node.js, Python, and Go apps from GitHub, and anything else with a Dockerfile. Pick your stack for a step-by-step guide; every path ends at a live HTTPS URL on *.runex.cloud.

Start deploying →Pick your stack
deploy guides
github
/deploy/github
docker
/deploy/docker
next.js
/deploy/nextjs
node.js
/deploy/nodejs
python
/deploy/python
go
/deploy/go
deploy guidesrunex

Stacks

Which stacks can you deploy on Runex?

Four languages with guides, plus any Dockerfile. GitHub is how they all get there.

How it works

How does every Runex deploy work?

The same four steps, whatever your stack. Traffic moves to a new version only after it passes a health check, which is how zero-downtime deployments work.

  1. You

    Push to GitHub

    Your repo is the source of truth.

  2. Runex

    Build

    From your framework, or your Dockerfile.

  3. Runex

    Health-check

    Traffic switches only when the new version is ready.

  4. Runex

    Serve

    Live on https://<slug>.runex.cloud.

Compare

Framework build or Dockerfile: which should you use?

Start with the framework build; switch to a Dockerfile when you need control. The Docker hosting guide shows a production-ready Dockerfile.

Framework build or Dockerfile: which should you use?
Framework buildDockerfile
What you provideYour code and its dependency fileA Dockerfile in the repo
Who decides the runtimeRunex detects itYou do, line by line
System packagesNot needed for most appsInstall anything with apt or apk
Best forStandard Next.js, Node, Python, Go appsCustom runtimes and other languages

Before you deploy

What should you check before your first deploy?

Five checks prevent most failed first deploys. If something still breaks, deployment troubleshooting is organized by symptom.

  • The app builds locally from a clean clone
  • The server listens on 0.0.0.0 and the PORT variable
  • Secrets are in environment variables, not in Git
  • A health path such as /health returns 200
  • Your lockfile is committed so builds are reproducible

FAQ

Deploy questions

What developers ask before the first push.

Do I need a Dockerfile to deploy on Runex?

No. Runex builds Next.js, Node.js, Python, and Go apps from your code. Add a Dockerfile only when you need system packages, another language, or full control of the runtime.

Can I deploy more than one app on Runex?

Yes. Each app or service deploys separately and gets its own container and HTTPS URL, and services in one project share a private network.

What happens if a deploy fails?

The previous version keeps serving traffic. The failed deploy is marked failed with its build or start logs, so you can fix it and push again.

Which URL does my app get after deploying?

Every app gets https://<slug>.runex.cloud, with HTTPS already on. You can add your own domain with a CNAME to cname.runex.cloud.

Next step

Pick a stack. Ship it.

Every guide ends at a live HTTPS URL. Free to start.

Deploy with Runex →Getting started guide