Introduction

Reactor is an open-source backend for web and mobile apps. One stateless server serves auth, Postgres data through PostgREST, file storage, functions, and sites. Postgres and a blob store are the only dependencies.

The same image runs as a long-lived process or as Lambda handlers. A project created on your machine uses the same client URLs it will use anywhere else.

Hosted Reactor is not open yet. Self-host the server, or read the quickstart and run the local Compose stack.

What you get

Surface	Path	What it is
Auth	/auth/v1	Users, sessions, magic links, recovery, invites
Data	/data/v1	PostgREST, with row-level security
Storage	/storage/v1	Presigned uploads and downloads
Functions	/fn/v1	Bun or Lambda, with versions and pins
Sites	project host	Static files, a site process, or a function path
Console	/console	Cluster admin. Separate from project users

Start here

1. Concepts — tenancy, tokens, and the data boundary.
2. Quickstart — Compose, the console, a project, a deploy.
3. Projects — refs, schemas, keys, and hostnames.

JavaScript and Swift clients live under Clients. The todos example is a static site, a table with row-level security, and one function.