Riff environment

How Riff apps and agents are structured — the two environments (development and production), the file layout, and the infrastructure underneath.

Every Riff app has two environments that are completely independent.

Environment
Purpose

Development

Your private build workspace. Changes here do not affect live users.

Production

The live environment. Becomes active when you deploy.

Development and production have separate databases, separate environment variables, and separate secrets values. You can point a secret (e.g. your ERP API key) to a test endpoint in development and the live endpoint in production.

How apps are built

Riff apps use the following stack — the Riff agent manages all of this for you:

Layer
Technology

Frontend

React + TypeScript

Backend

Python + FastAPI

Database

PostgreSQL (serverless)

You describe what you want to build. The Riff agent writes, tests, and deploys the code. You do not need to know the technology stack.

File structure

Location
What lives there

frontend/src/pages/

One file per page (route) in your app

frontend/src/components/

Reusable UI components

backend/app/apis/

Backend API endpoints

backend/app/libs/

Shared backend logic

Notes

  • You do not need to manage infrastructure or hosting — the platform handles these.

  • The Riff agent connects to external systems through Secrets and Integrations.

  • Runtime output and errors are visible in Logs.

Last updated

Was this helpful?