Upload a zip
Drag and drop your project as a zip. No Git, no setup.
- No repo or Git needed
- Language and framework auto-detected
- Upload a new zip to ship an update
How it works
Drop your code. Runex does the rest.
Upload a zip or connect GitHub. Runex detects the language, builds your app, runs it in an isolated container, and gives you a live HTTPS URL. You do two steps.
- Zip upload or GitHub
- Language auto-detected
- Live HTTPS URL
# my-app.zip · upload
- Upload receivedmy-app.zip · 4.1 MB
- Language detectedNode.js · npm
- Building containerinstall · build · isolate
- Live over HTTPShttps://my-app.runex.cloud
example deployauto-detected
Two ways
What are the two ways to deploy on Runex?
Upload a zip, or connect a GitHub repo. Both end in the same place: a live HTTPS app in its own container.
Connect GitHub
Install the GitHub App and pick a repo and branch.
- Every push redeploys automatically
- Preview deploys for pull requests
- Webhooks verified as coming from GitHub
Steps
What are the steps to deploy an app on Runex?
Four steps, and you only do two. You bring the code; Runex detects, builds, isolates, and ships it.
-
You
Upload a zip or connect GitHub
Drag and drop a zip, or pick a repo and branch.
-
You
Add env vars (optional)
Set values like DATABASE_URL.
-
Runex
Detect & build
Language, framework, and build steps found for you.
-
Runex
Go live
Open https://<slug>.runex.cloud.
Upload = live.
From a zip to a live HTTPS URL without touching a server. With GitHub connected, every push to your branch ships automatically.
Auto-detect
What does Runex detect automatically?
Runex reads your project and works out how to build and run it. If you include a Dockerfile, Runex uses that instead.
Language & framework
Next.js, Node.js, Python, Go, and more, from your project files.
Build steps
Installs dependencies and runs the build for your stack.
Start command
Starts your app the way your framework expects.
Port
Sends traffic to your app. Listen on 0.0.0.0 to be reachable.
Environment variables
Injected at runtime, never stored in your code.
HTTPS
A certificate for every deploy, on *.runex.cloud or your own domain.
Dashboard
What do you see after you deploy?
Every app shows up in your Runex dashboard with its status. Ready, building, idle, or stopped, at a glance.
How Runex helps
How does Runex make deployment easier?
Runex removes the server work between your code and a live URL. No servers to patch, no certificates to renew, no build scripts to write.
No servers to manage
Runex runs the infrastructure, so you never log in to a server.
HTTPS by default
Certificates are issued and renewed for you.
Isolated containers
Each app gets its own CPU and memory limits.
Instant rollbacks
Go back to a previous version in one step.
Preview deploys
Every pull request gets its own URL to review.
Logs & status
Build logs, runtime logs, and deploy status in one place.
Zip vs GitHub
Should you upload a zip or connect GitHub?
Upload a zip to ship fast; connect GitHub to ship on every push. Pick the one that matches how you work.
| Fastest startZip upload | Push to deployGitHub | |
|---|---|---|
| Git required | Not needed | Yes |
| Language detection | Automatic | Automatic |
| Ship an update | Upload a new zip | Push to your branch |
| Preview deploys | No | Per pull request |
| HTTPS URL | Included | Included |
| Best for | Prototypes, demos, projects without Git | Teams and ongoing projects |
FAQ
Questions about deploying on Runex
Short answers about zip uploads, GitHub, and auto-detection.
What is the easiest way to deploy an app on Runex?
Upload your project as a zip. Runex detects the language, builds it, and gives you a live HTTPS URL on *.runex.cloud, with no Git or server setup.
Can I deploy an app without GitHub?
Yes. Upload a zip of your project and Runex deploys it. Connect GitHub later if you want every push to redeploy automatically.
How does Runex know which language my app uses?
Runex reads your project files, such as package.json, requirements.txt, or go.mod, to detect the language and framework, then picks the build and start steps. If your project has a Dockerfile, Runex uses it instead.
What should be inside the zip file?
Your project's source code, with its dependency file at the top level, for example package.json for Node.js. Leave out folders like node_modules; Runex installs dependencies during the build.
How do I update an app deployed from a zip?
Upload a new zip of the updated project. Runex builds it and switches traffic to the new version.
Does every git push redeploy my app?
Yes, when the app is connected to GitHub with webhooks on. Each push to the selected branch triggers a new build, and Runex verifies the webhook came from GitHub.
Is a Dockerfile required to deploy on Runex?
No. Runex detects common languages and frameworks on its own. Add a Dockerfile only if you want full control over the build.
Is HTTPS set up automatically after deploy?
Yes. Every deploy gets a live HTTPS URL on *.runex.cloud, and custom domains get certificates issued and renewed for you.
Next step
Drop your code. Go live.
Sign up, upload a zip or connect GitHub. Your HTTPS URL is next.