Cloud deployment platform
Push to GitHub.
Get a live HTTPS URL.
Runex is an easy cloud deployment platform for developers. Connect a repo or upload a zip, and Runex builds it, runs it in an isolated container, and serves it on *.runex.cloud. No servers to manage.
- GitHub, zip & Dockerfile deploys
- HTTPS by default
- Custom domains
- Isolated containers
Definition
What is Runex?
A platform as a service (PaaS) that turns a GitHub repo or a zip upload into a live web app with HTTPS. You bring the code. Runex handles the build, the runtime, and the certificate.
Your code
Via the Runex GitHub App or a zip upload
Build
Language auto-detected, or your Dockerfile
Isolated container
Its own CPU and memory limits
Live HTTPS URL
On *.runex.cloud or your own domain
How it works
How does Runex deploy an app?
Four steps, and you only do two. Pick a repo and branch, or upload a zip; Runex builds, isolates, and ships it.
-
You
Connect GitHub or upload a zip
Grant access to only the repos you choose, or drag and drop a zip.
-
You
Pick repo & branch or zip
Add env vars like DATABASE_URL.
-
Runex
Build & isolate
Language auto-detected, built, and started in its own container.
-
Runex
Go live
Open https://<slug>.runex.cloud.
Push = redeploy.
With webhooks on, every push to your branch ships automatically, and Runex verifies each webhook really came from GitHub.
Capabilities
What does Runex include?
Everything between your code and a production URL. Builds, HTTPS, previews, rollbacks, scaling, databases, and logs in one platform.
GitHub App deploys
Pick a repo and branch. Authenticated, scoped access.
Redeploy on push
Verified GitHub webhooks trigger each new build.
Zip & Dockerfile deploys
Drag and drop a zip, or bring a Dockerfile for any stack.
Isolated containers
One container per app, with CPU and memory limits.
HTTPS by default
Every deploy gets a secure *.runex.cloud URL.
Custom domains
CNAME to cname.runex.cloud. HTTPS included.
Environment variables
Secrets injected at runtime, never in your repo.
Deployment status
Building, running, or failed, at a glance.
Also Preview deployments · Instant rollbacks · Autoscaling · Managed databases · Logs & metrics
Not offered SSH deploys · Deployment templates · SAML single sign-on
Stacks
What can I deploy on Runex?
Next.js, Node.js, Python, and Go, plus anything with a Dockerfile.
Compare
Runex vs a VPS vs a deploy tool: what's the difference?
It comes down to who runs the server. Runex runs it for you. A VPS makes you run it. A deploy tool ships code to servers you still maintain.
| Deployment platformRunex | Virtual serverSelf-managed VPS | Deploy automationDeploy tool + servers | |
|---|---|---|---|
| Server | Runs it for you | You patch and secure it | You still maintain it |
| Deploys | GitHub App, zip upload, or Dockerfile | Your scripts, SSH, or CI | Tool pushes code on commit |
| HTTPS | Built in, custom domains too | You install and renew certs | Set up on your servers |
| Isolation | Container per app, resource limits | Whatever you configure | Depends on your servers |
| Best for | Shipping apps without server admin | Full root control | Teams that already own servers |
Runex is a great fit if…
- You ship web apps or APIs in Next.js, Node.js, Python, Go, or Docker
- Your code lives on GitHub or fits in a zip you can upload
- You want HTTPS and custom domains without cert work
Runex isn't the right fit yet if…
- You need root access to the host machine
- You need push-to-deploy from GitLab or Bitbucket (zip upload works, auto-deploy is GitHub only)
- You need one-click templates or SAML single sign-on
- You require SOC 2, ISO 27001, or HIPAA certification
Example
A Next.js store, live in six steps
A Next.js app, a managed Postgres database, and a custom domain. No server involved.
- Install the GitHub App on acme/storefront
- Select the repo and the main branch
- Add DATABASE_URL as an env variable
- Runex builds and runs it in an isolated container
- CNAME shop.acme.com → cname.runex.cloud
- Push to main → automatic redeploy
- repository
- acme/storefront
- branch
- main · redeploy on push
- env
- DATABASE_URL = postgres://…
- runtime
- isolated container
- status
- running
- url
- https://storefront.runex.cloud
- domain
- shop.acme.com → cname.runex.cloud
Pricing
How much does Runex cost?
Free to start. Paid prices live in the dashboard, so you never see a stale number.
Hobby
Free
Deploy from GitHub or a zip with HTTPS and isolated containers.
Production
In dashboard
Higher resource allowances and more concurrent deploys.
Teams
Early access
Shared project access for small teams.
What's the easiest way to deploy a web app from GitHub?
Connect your repo to a platform as a service (PaaS). On Runex, you install the GitHub App, pick a repo and branch, and get a live HTTPS URL on *.runex.cloud, no server setup. No repo? Upload a zip and Runex detects the language for you.
PaaS vs VPS: which should I use?
A VPS is a raw server you configure, patch, and secure yourself. A PaaS like Runex runs the build, the container, and HTTPS for you. Pick a VPS for root control, a PaaS to skip server admin.
Do I need to manage a server to host a web app?
No. A PaaS runs the server for you. With Runex, you push code and it's built, run in an isolated container, and served over HTTPS: there's no host to patch.
How do I auto-deploy my app on every git push?
Connect your repo through a GitHub integration with webhooks. On Runex, every push to your selected branch triggers a new build, and each webhook is verified as coming from GitHub.
How do I deploy a Docker container to the cloud?
Add a Dockerfile to your repo and use a platform that builds from it. Runex builds your Dockerfile and runs the image in an isolated container with CPU and memory limits.
How do I add HTTPS (SSL) to my web app?
Use a host that provisions certificates automatically, so you never install or renew them. Every Runex deployment gets HTTPS on *.runex.cloud by default, including on the free plan.
How do I point a custom domain to my app?
Add a CNAME record at your DNS provider that points to your host. On Runex, point the CNAME to cname.runex.cloud and HTTPS is included for your domain.
Where should I store API keys and secrets for my app?
In environment variables, never in your code or repo. Runex injects them into your deployment at runtime; redeploy after changing one.
How do I connect a database to my deployed app?
Add a managed PostgreSQL, MySQL, Redis, or MongoDB database to your Runex project, and your app reads its connection string from an environment variable, usually DATABASE_URL. An external database connects the same way.
Is there a free way to host a web app?
Yes, many platforms have free tiers. Runex is free to start on its Hobby plan, with GitHub and zip deploys, HTTPS, and isolated containers; paid plan prices are in the dashboard.
Next step
Ready to ship your first app?
Sign up, connect GitHub or drop a zip. Your HTTPS URL is next.