Documentation
Runex docs: from first deploy to production.
The Runex docs explain how to deploy an app from GitHub, configure it with environment variables, put it on your own domain, and fix it when something breaks. Start with Getting started if it's your first time.
- getting started
- /documentation/getting-started
- github app setup
- /documentation/github-app-setup
- custom domains
- /documentation/custom-domain-setup
- troubleshooting
- /documentation/troubleshooting
Guides
Which guide do you need?
Five guides cover the whole path. Each one answers a single question.
Getting started
Sign up, connect GitHub, and deploy your first app.
GitHub App setup
Install the App, grant repo access, and redeploy on push.
Environment variables
Secrets, DATABASE_URL, and build-time variables.
Custom domains
Point a CNAME to cname.runex.cloud and go live with HTTPS.
Troubleshooting
Failed builds, unreachable apps, and domain issues.
Troubleshooting
Something broke. Where do you start?
Match the symptom to the guide. Each is a short checklist.
Stacks
Is there a guide for my framework?
Yes, for Next.js, Node.js, Python, Go, and Docker.
FAQ
Docs questions
Fast answers before you dig in.
Where should I start with Runex?
Start with Getting started: create an account, install the Runex GitHub App, pick a repository and branch, and deploy. It takes a few minutes.
Do I need to know Docker to use Runex?
No. Runex builds Next.js, Node.js, Python, and Go apps straight from your code. Docker is optional, for when you want full control of the runtime.
Where are build and runtime logs in the Runex dashboard?
Open the app in the Runex dashboard. Build logs and runtime logs stream live for every deploy, including failed ones.
Next step
Read less. Deploy more.
The fastest way to learn Runex is to deploy something.