Deploy from GitHub

Easy deployment
for developers.

Runex is an easy cloud deployment platform for developers. Deploy applications from GitHub or Docker to HTTPS on *.runex.cloud — without manually managing deployment infrastructure.

$connect github → select repo → deploy
Deploy

Capabilities

GitHub deploy, HTTPS, domains, and isolation.

Deploy from GitHub or Docker, ship HTTPS on *.runex.cloud, attach custom domains, and run apps in isolated containers.

Live deploy

In progress

# runex deploy — exhibit

  • Connecting GitHub Apprepo · main
  • Building containerdetect · install · compile
  • Starting runtimeisolated · resource-limited
  • Livehttps://app.runex.cloud
HTTPS · *.runex.cloudcontainer isolation

GitHub App

Install once. Deploy from branches.

Repository access, branch selection, and push-triggered redeploys when webhooks are active.

Deploy from GitHub →

HTTPS + domains

*.runex.cloud, then your name.

Production HTTPS out of the box. Custom domains via CNAME to cname.runex.cloud.

Custom domains docs →

Isolation

Containers with resource limits

Workloads run isolated — we document mechanisms, not slogans. See security for what is enforced vs roadmap.

Security overview →

Visibility

Build and runtime status

Track what shipped and diagnose failures. Log depth continues to evolve — labeled honestly.

All features →

How it works

From GitHub to HTTPS in four steps.

Connect, configure, deploy, and ship — without operating a VPS for every application.

01

Connect repository

Install the Runex GitHub App and grant access to the repositories you want to deploy.

02

Configure deploy

Select a repository and branch. Runex detects the project and prepares a build.

03

Build & isolate

Your application is built and started in an isolated container environment.

04

Ship HTTPS URL

Reach your app at https://<deployment>.runex.cloud — then attach a custom domain when ready.

Stacks

Next.js, Node.js, Python, Go, and Docker.

Start at the deploy hub, or jump straight to GitHub, Next.js, Node.js, Python, Go, or Docker.

FAQ

Frequently asked questions.

What is Runex?+

Runex is an easy cloud deployment platform for developers. Connect a GitHub repository, deploy into an isolated container environment, and get a public HTTPS URL on *.runex.cloud.

Is Runex a deployment platform?+

Yes. Runex is a cloud deployment platform (PaaS-style) focused on easy application deployment for developers — also referred to as Runex Cloud.

How does Runex work?+

Runex connects to your application source via a GitHub App, builds the application, creates an isolated deployment environment, and exposes the result through a public HTTPS URL on *.runex.cloud.

Can I deploy from GitHub?+

Yes. Runex uses a GitHub App for repository access, branch selection, and deployment. Push-triggered redeployment is supported when webhooks are configured.

Can Runex deploy Docker, Next.js, Node.js, Python, and Go?+

Yes. Dedicated deploy landings cover Next.js, Node.js, Python, Go, and Docker. Start from the deploy hub or install the GitHub App and ship a supported project.

Does Runex provide HTTPS?+

Yes. Runex provides HTTPS for deployed applications on *.runex.cloud and for custom domains connected through cname.runex.cloud.

Can I use a custom domain?+

Yes. Point your domain's CNAME to cname.runex.cloud and attach it to a Runex deployment. See the custom domains documentation for the full steps.

How does Runex isolate applications?+

Runex deploys applications in isolated containers with resource controls. Isolation is described at a high level on the security page; we only claim controls that are enforced in production.

How does Runex compare with a VPS?+

A VPS is a machine you administer. Runex is a deployment platform: you ship apps from GitHub/Docker without operating the host OS for every project. See the Runex vs VPS comparison and the PaaS vs VPS guide for details.

Customer voices

Loved by the people who ship

Developers and teams ship production apps with Runex. Here's what they say about the path from code to a live URL.

“From repo to a public URL, the path feels refreshingly short.”
MMayaProduct engineer
“I can hand a deployment link to the team without writing another runbook.”
AAlexIndependent developer
“From repo to a public URL, the path feels refreshingly short.”
MMayaProduct engineer
“I can hand a deployment link to the team without writing another runbook.”
AAlexIndependent developer
“Runex keeps the deployment surface small so we can stay focused on the product.”
PPriyaTechnical founder
“The GitHub flow is the right level of boring: connect, select, ship.”
SSamFull-stack engineer
“Runex keeps the deployment surface small so we can stay focused on the product.”
PPriyaTechnical founder
“The GitHub flow is the right level of boring: connect, select, ship.”
SSamFull-stack engineer
“Custom domains came after the first deploy, not before it.”
JJordanProduct builder
“Clear status, isolated workloads, and a URL I can share.”
NNoorPlatform engineer
“Custom domains came after the first deploy, not before it.”
JJordanProduct builder
“Clear status, isolated workloads, and a URL I can share.”
NNoorPlatform engineer
“From repo to a public URL, the path feels refreshingly short.”
MMayaProduct engineer
“I can hand a deployment link to the team without writing another runbook.”
AAlexIndependent developer
“Runex keeps the deployment surface small so we can stay focused on the product.”
PPriyaTechnical founder
“The GitHub flow is the right level of boring: connect, select, ship.”
SSamFull-stack engineer
“Custom domains came after the first deploy, not before it.”
JJordanProduct builder
“Clear status, isolated workloads, and a URL I can share.”
NNoorPlatform engineer
“From repo to a public URL, the path feels refreshingly short.”
MMayaProduct engineer
“I can hand a deployment link to the team without writing another runbook.”
AAlexIndependent developer
“Runex keeps the deployment surface small so we can stay focused on the product.”
PPriyaTechnical founder
“The GitHub flow is the right level of boring: connect, select, ship.”
SSamFull-stack engineer
“Custom domains came after the first deploy, not before it.”
JJordanProduct builder
“Clear status, isolated workloads, and a URL I can share.”
NNoorPlatform engineer

Next step

Deploy your first application

Connect a GitHub repository, deploy with Runex, and get a production HTTPS URL on *.runex.cloud.