Company · Use cases
What developers ship on Runex.
Developers use Runex to host full-stack web apps, APIs, background workers, scheduled jobs, and client sites: anything that runs in a container. Each use case below shows the features it relies on.
- web app
- Next.js · public
- api
- Node / Python / Go
- worker
- private · no public port
- cron
- 0 3 * * * · nightly
- database
- PostgreSQL · managed
Use cases
What can you build and host on Runex?
Five common workloads. Each links to the guide or feature that matters most.
Full-stack web apps
Frontend, API, and database in one project.
REST and GraphQL APIs
Node.js, Python, or Go services that scale with traffic.
Scheduled jobs
Reports, cleanups, and syncs on a cron schedule.
Client sites for agencies
Client domains, previews, and per-project roles.
Side projects
Free Hobby plan with HTTPS from the first deploy.
Match
Which Runex features does each use case need?
Start with the features in the middle column. Add the rest as you grow.
| Key features | Start here | |
|---|---|---|
| Full-stack web app | Managed database, private networking, env variables | Full-stack guide |
| API | Autoscaling, logs and monitoring, zero-downtime deploys | Stack guides |
| Background worker | Private networking, Redis, logs | Private networking |
| Scheduled job | Cron jobs, logs, alerts | Cron jobs |
| Agency client site | Custom domains, preview deployments, team roles | Custom domains |
Boundaries
What is Runex not built for?
Workloads that need your own servers or enterprise identity. Better to know now. For how Runex compares with other hosts, see deployment platforms compared.
- Deploying over SSH to servers you run yourself
- Launching stacks from one-click deployment templates
- Single sign-on (SAML) for your company login
- Repositories on GitLab or Bitbucket
- Root access to the host machine
FAQ
Use case questions
Can Runex run it? Short answers.
Can I host an API on Runex?
Yes. Deploy a Node.js, Python, or Go API from GitHub and it gets its own HTTPS URL, autoscaling replicas, and live logs.
Can Runex run background workers?
Yes. A worker is a service without a public port: it runs in its own container and talks to your database or Redis over the private network.
Is Runex a good fit for agencies?
Yes, for client web apps: each client gets a project with custom domains, preview URLs for review, and per-project roles for your team.
Next step
Deploy your use case.
Start with one app on the free plan and add services as you go.