Deploying / Supported Frameworks
Supported Frameworks
Riven auto-detects your framework and configures the build for you. These are the frameworks supported today — with more on the way.
Supported frameworks
Riven detects your project type from the files in your repo and sets up the right build automatically. No config needed for these:
Frontend apps that build into static HTML, CSS, and JS. Served fast from the edge.
Detected via vite.config.js / vite.config.ts
Full-stack React with server rendering, API routes, and static export.
Detected via next.config.js
Python web apps. Riven runs your WSGI server and serves your app.
Detected via manage.py
Node.js APIs and servers. Riven runs your start command and exposes your port.
Detected via package.json with express
How detection works
When you create a service, Riven clones your repo and looks for tell-tale files — a vite.config.ts, a manage.py, a next.config.js, and so on. From that, it figures out:
- Which framework you're using.
- Whether it's a static site or a web service.
- The right build and start commands.
- The port your app runs on.
You can override any of these in your service settings if the defaults aren't right for your project.
If Riven detects the wrong track (static vs web service), it'll tell you at deploy time so you can pick the correct one.
Using your own Dockerfile
Using a framework Riven doesn't detect yet? Add a Dockerfile to your repo, and Riven will build and deploy it as-is. This works for almost any stack — Go, Rust, PHP, or a custom setup.
If your app needs build-time environment variables (like a frontend that bakes in an API URL), declare them in your Dockerfile with ARG and ENV in the build stage. Rivenpasses your VITE_, NEXT_PUBLIC_, and REACT_APP_ variables as build args automatically.
More coming
We're adding frameworks based on what Indian developers use most. Vue, Nuxt, SvelteKit, FastAPI, Flask, and others are on the roadmap. Need one that's not here yet? A Dockerfile gets you deployed today.