Runex features
Everything you need to deploy, run, and scale.
Runex features cover the whole path from a GitHub push to a production app: builds, previews, rollbacks, HTTPS, databases, scaling, and logs. Pick any feature to see exactly how it works.
- build & deploy
- #build ↓
- network & security
- #network ↓
- scale & data
- #scale ↓
- operate & collaborate
- #operate ↓
Build & deploy
How does code get from GitHub to production?
Push a branch; Runex builds, previews, and ships it. And if a release goes wrong, you undo it in one click.
GitHub deploys
Install the GitHub App, pick a repo and branch, and ship.
Automatic deploys
Every push to your branch triggers a verified redeploy.
Dockerfile deploys
Bring a Dockerfile; Runex builds and runs the image.
Preview deployments
Every pull request gets its own live HTTPS URL to review.
Instant rollbacks
Put the last good version back in production with one click.
Zero-downtime deployments
New versions go live only after they pass a health check.
Network & security
How is traffic secured and routed?
HTTPS everywhere, private by default. Public traffic is encrypted; internal traffic never leaves the private network.
Custom domains
CNAME to cname.runex.cloud and serve on your own domain.
Container isolation
Every app runs in its own container with CPU and memory limits.
Environment variables
Secrets injected at runtime and kept out of your repo.
Automatic SSL
TLS certificates issued and renewed for every domain.
Private networking
Services talk over an internal network, not the internet.
Scale & data
How do apps scale and store data?
Replicas for traffic, managed databases for data, cron for everything on a clock.
Operate & collaborate
How do teams run apps day to day?
See everything, control who changes what. Logs, metrics, alerts, roles, and an audit trail.
Boundaries
What doesn't Runex include?
Four things, so you can decide fast. If you need any of these today, Runex isn't the right fit yet.
- SSH deployment to your own servers: Runex runs your app for you instead
- Deployment templates or one-click starter kits
- Single sign-on (SAML / SSO)
- GitLab or Bitbucket: Runex deploys from GitHub
FAQ
Questions developers ask
Quick answers. Each feature page goes deeper.
What features should a deployment platform have?
At minimum: deploys from Git, HTTPS, environment variables, logs, and rollbacks. For production, add preview deployments, zero-downtime deploys, autoscaling, and a managed database.
What is the difference between a PaaS and a deployment tool?
A PaaS runs your app on its own infrastructure. A deployment tool ships your code to servers you manage yourself. Runex is a PaaS.
Which deployment features matter most for a small team?
Automatic deploys from GitHub, preview deployments, one-click rollbacks, and logs. Together they remove most of the manual work and most of the risk.
Does Runex support SSH deployment?
No. Runex deploys from GitHub or a Dockerfile onto its own infrastructure; it doesn't push code to your servers over SSH.
Next step
Ready to use all 16?
Sign up, install the GitHub App, pick a repo. Every feature is there when you need it.