Use case

Deploy full-stack applications

Runex is an easy cloud deployment platform for developers who need to ship a frontend and a backend API without manually operating a VPS for every service.

Deploy a full-stack app Deploy from GitHub

Architecture on Runex

A common full-stack layout looks like this — Runex hosts the application services; data stores stay where you already run them unless a managed database feature is explicitly available in your account:

Browser / client
      |
      v
Frontend (e.g. Next.js on Runex)
      |
      v
Backend API (Node / Python / Go on Runex)
      |
      v
External database (provider of your choice)

Each Runex deployment gets an HTTPS URL on *.runex.cloud. You can attach custom domains via cname.runex.cloud for production hostnames such as app.example.com and api.example.com.

Typical workflow

Push frontend and API code to GitHub (monorepo or separate repos).
Install the Runex GitHub App and deploy each service you need publicly reachable.
Configure environment variables for API URLs, secrets, and database connection strings.
Point custom domains when ready — see custom domains.

Stacks that fit

Next.js frontend or full-stack app
Node.js API
Python API
Go API
Docker when you need a custom image

Databases — accurate expectations

Full-stack apps almost always need a database. On Runex, treat databases as external unless your dashboard documents a managed database offering. Pass credentials through environment variables; never commit secrets.

FAQ

Can I deploy a full-stack app on Runex?+

Yes. Deploy your frontend and backend API as Runex applications (often from the same monorepo or separate repos), expose them over HTTPS, and have the frontend call your API. Databases are typically external services your app connects to via environment variables.

Does Runex provide managed databases?+

Do not assume a managed database product unless your Runex dashboard documents one. Apps commonly connect to external Postgres, MySQL, or other providers using environment variables.

Next step

Ship frontend + API on Runex

Connect a GitHub repository, deploy with Runex, and get a production HTTPS URL on *.runex.cloud.

Deploy with Runex Read the docs