Runex

Deploy · GitHub

Deploy from GitHub. Every push ships.

Runex is a GitHub deployment platform: install the Runex GitHub App, pick a repository and branch, and every push deploys automatically. Pull requests get their own preview URL, and each deploy goes live only after it's healthy.

Start deploying →See the steps
  • GitHub App, scoped access
  • Redeploy on push
  • Preview per pull request
acme/storefront
repository
acme/storefront
branch
main · deploy on push
webhook
verified
pull request
#42 → preview url
url
https://storefront.runex.cloud
illustrative namesrunex

Definition

What is push-to-deploy from GitHub?

A workflow where pushing code to a branch automatically builds and releases it. No manual deploy step.

With push-to-deploy, your GitHub branch becomes your release button. Merge to main and production updates; open a pull request and a preview appears.

Runex connects through a GitHub App: an integration you install on your account or organization with access to only the repositories you choose.

When you push, GitHub sends a webhook. Runex verifies its signature, builds that commit, health-checks it, and switches traffic.

How to deploy

How do you deploy a GitHub repository on Runex?

Four steps, once. After that, you just push.

  1. You

    Sign up

    Create an account at runex.cloud.

  2. You

    Install the GitHub App

    Grant access to only the repos you'll deploy.

  3. You

    Pick repo and branch

    Usually main for production.

  4. Runex

    Build and serve

    Live on *.runex.cloud with HTTPS.

Push = redeploy.

Each push to your branch starts a new deploy; each pull request gets a preview that updates with every commit.

Configuration

What happens when you push a commit?

Webhook in, verified build, health check, live.

git push → runex
$ git push origin main
# GitHub → webhook → Runex (signature verified)
build     7be20d4  succeeded
container started   isolated
health    GET /health → 200
traffic   switched  live
url       https://storefront.runex.cloud
git push → runexrunex

If the build or health check fails, traffic stays on the previous version and the deploy is marked failed.

Included

What does the Runex GitHub integration include?

Everything between a push and production.

Scoped repo access

The App reads only the repos you grant.

Redeploy on push

Every push to your branch ships.

Preview deployments

A live URL for each pull request.

One-click rollback

Return to any earlier deploy.

Avoid

What stops GitHub deploys from working?

Usually access, not code.

  • The GitHub App doesn't have access to the repository
  • Pushing to a branch that isn't the one you selected
  • Secrets committed to the repo instead of set as env variables
  • The repo lives on GitLab or Bitbucket: Runex supports GitHub only

FAQ

GitHub deploy questions

Short answers for your first deploy.

Does Runex redeploy automatically when I push to GitHub?

Yes. Each push to the branch you selected triggers a new deploy, and the new version goes live once it passes its health check.

Which GitHub permissions does Runex need?

Read access to the repositories you choose, plus webhooks so pushes and pull requests trigger deploys. Grant only the repos you intend to deploy.

Does Runex support GitLab or Bitbucket?

No. Runex connects to GitHub only, through the Runex GitHub App.

Can I deploy a private GitHub repository?

Yes. Install the Runex GitHub App on the account or organization that owns it and grant access to that repository.

Next step

Connect GitHub. Push to ship.

Connect your repo and get a live HTTPS URL on your first deploy. Free to start.

Deploy with Runex →Getting started guide