Platform / How It Works
How It Works
You give Riven. a GitHub repo. Riven. turns it into a running app on the internet, with HTTPS and a URL. Here's what actually happens between those two points — no magic, just steps you don't have to do yourself.
The big picture
At its core, Riven. does what you'd otherwise do by hand to deploy an app: clone your code, build it, run it, and put it behind a URL with HTTPS. The difference is it does all of it automatically, in seconds, on infrastructure in India.
You never touch a server, write a deployment script, or configure a certificate. You push code; Riven. does the rest.
What happens on deploy
Every deploy runs through the same steps:
Clone
Riven. pulls your latest code from GitHub, from the branch your service deploys from.
Detect
It figures out your framework — Vite, Next.js, Django, Express — and the right way to build it.
Build
Your app is compiled inside a clean, isolated container, with your build-time variables injected.
Package
The built app becomes a container image — a self-contained snapshot that runs the same everywhere.
Deploy
Riven. runs that image, wires up networking, and routes traffic to it.
Go live
Your app is reachable at its URL over HTTPS, and you get logs the whole way through.
You can watch each step stream live in your service's Logs while it deploys.
Containers & Kubernetes
Every app runs in its own container — an isolated box with just your app and what it needs. Containers are why your app runs the same on Riven. as it does on your machine.
Those containers are managed by Kubernetes, which handles keeping your app running, restarting it if it crashes, and scaling it. You don't have to know or think about any of this — it's the engine under the hood. You just see your app, live.
Domains & HTTPS
Each service gets a URL on .rivendeploy.com the moment it deploys. Traffic to that URL is routed to your app's container automatically, and served over HTTPS with a certificateRiven issues and renews for you.
When you add your own domain, the same routing applies — Rivenpoints it at your app and secures it with HTTPS, no manual certificate work.
Where it all runs
Your apps run on infrastructure in India — specifically the Mumbai region. That means lower latency for your Indian users, because the server is physically close to them, and your data stays in the country.
This is the whole point of Riven: the same deploy experience you'd get from a global platform, but running where your users actually are, billed in rupees.
What you don't have to manage
The reason Riven exists is to take all of this off your plate. You never have to:
- Rent or configure a server.
- Write a Dockerfile (unless you want to).
- Set up HTTPS or renew certificates.
- Configure load balancing or networking.
- Manage Kubernetes, even though your app runs on it.
All of that is handled. You focus on your code; Riven handles the infrastructure.