Introduction

Riven is a Platform as a Service (PaaS). That means you give it your code, and it handles everything needed to put that code online — building it, running it, setting up HTTPS, and keeping it live. You don't manage servers, write Dockerfiles, or set up SSL certificates by hand.

If you've used Railway, Render, or Vercel, Riven works the same way. The difference is where it runs and how you pay: your apps live on infrastructure in India, and you're billed in rupees with a proper invoice.

Hosting wasn't built for Indian developers. You write code in India, your users are in India, but your app ends up running on a server in Virginia — billed in dollars, with latency added for every request, and a card that sometimes gets declined for "international activity."

Riven fixes the parts that don't make sense for us:

• Your app runs in India. Lower latency for Indian users, because the server is close to them.
• You pay in rupees. UPI, cards, netbanking — all native. No forex, no surprise declines.
• Your data stays in India. Built with the DPDP Act 2023 in mind, so data residency isn't an afterthought.

Riven is built for the way Indian developers actually ship:

• The student deploying their first full-stack project the night before a hackathon.
• The indie hacker building a SaaS after their day job.
• The small team running production without an AWS bill that eats their runway.
• The freelancer juggling client apps on one card that keeps getting flagged.

If hosting has ever felt harder and more expensive than it should be, Riven is built for you.

The whole flow is three steps:

• Connect your GitHub repo.
• Configure — Riven auto-detects your framework and fills in the build settings.
• Ship — push to deploy, and get a live URL with HTTPS and logs.

After the first deploy, every git push rebuilds and redeploys your app automatically. Under the hood, Riven runs your app in containers on Kubernetes — but you never have to think about that.

Static sites and server apps cost very differently to run, so Rivensplits them into two tracks. This keeps pricing honest — you only pay for what your app actually uses.

• Static Sites — frontend apps that build into HTML, CSS, and JS (like a Vite + React app). Always available, served fast.
• Web Services — apps that run a server process (like an Express API or a Django app). These can scale to zero when idle, so you don't pay for an app nobody's using at 4 AM.

Each track has its own plans, starting free. You can run apps on both tracks from the same account.