GitHub App
Install once. Deploy from branches.
Repository access, branch selection, and push-triggered redeploys when webhooks are active.
Deploy from GitHub →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.
New here? What is Runex? · Deploy hub
Capabilities
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
GitHub App
Repository access, branch selection, and push-triggered redeploys when webhooks are active.
Deploy from GitHub →HTTPS + domains
Production HTTPS out of the box. Custom domains via CNAME to cname.runex.cloud.
Custom domains docs →Isolation
Workloads run isolated — we document mechanisms, not slogans. See security for what is enforced vs roadmap.
Security overview →Visibility
Track what shipped and diagnose failures. Log depth continues to evolve — labeled honestly.
All features →How it works
Connect, configure, deploy, and ship — without operating a VPS for every application.
01
Install the Runex GitHub App and grant access to the repositories you want to deploy.
02
Select a repository and branch. Runex detects the project and prepares a build.
03
Your application is built and started in an isolated container environment.
04
Reach your app at https://<deployment>.runex.cloud — then attach a custom domain when ready.
Learn
Getting started, GitHub deploys, custom domains, security, and practical guides.
Guide
Brand entity page: what Runex is, how it works, and who it is for.
Guide
GitHub, Docker, and framework landings in one place.
Guide
Install the GitHub App, pick a branch, and ship to *.runex.cloud.
Guide
Create an account, connect GitHub, and ship your first deployment.
Guide
Point a CNAME to cname.runex.cloud and attach HTTPS to your brand domain.
Guide
Container isolation, HTTPS/TLS, webhooks, and what we do not overclaim.
FAQ
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.
Yes. Runex is a cloud deployment platform (PaaS-style) focused on easy application deployment for developers — also referred to as Runex Cloud.
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.
Yes. Runex uses a GitHub App for repository access, branch selection, and deployment. Push-triggered redeployment is supported when webhooks are configured.
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.
Yes. Runex provides HTTPS for deployed applications on *.runex.cloud and for custom domains connected through cname.runex.cloud.
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.
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.
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
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.”
“I can hand a deployment link to the team without writing another runbook.”
“From repo to a public URL, the path feels refreshingly short.”
“I can hand a deployment link to the team without writing another runbook.”
“Runex keeps the deployment surface small so we can stay focused on the product.”
“The GitHub flow is the right level of boring: connect, select, ship.”
“Runex keeps the deployment surface small so we can stay focused on the product.”
“The GitHub flow is the right level of boring: connect, select, ship.”
“Custom domains came after the first deploy, not before it.”
“Clear status, isolated workloads, and a URL I can share.”
“Custom domains came after the first deploy, not before it.”
“Clear status, isolated workloads, and a URL I can share.”
“From repo to a public URL, the path feels refreshingly short.”
“I can hand a deployment link to the team without writing another runbook.”
“Runex keeps the deployment surface small so we can stay focused on the product.”
“The GitHub flow is the right level of boring: connect, select, ship.”
“Custom domains came after the first deploy, not before it.”
“Clear status, isolated workloads, and a URL I can share.”
“From repo to a public URL, the path feels refreshingly short.”
“I can hand a deployment link to the team without writing another runbook.”
“Runex keeps the deployment surface small so we can stay focused on the product.”
“The GitHub flow is the right level of boring: connect, select, ship.”
“Custom domains came after the first deploy, not before it.”
“Clear status, isolated workloads, and a URL I can share.”
Next step
Connect a GitHub repository, deploy with Runex, and get a production HTTPS URL on *.runex.cloud.