The **serverpod_auth** module (Serverpod 3) provides **token managers** (JWT, server-side sessions) and **identity providers** (Email, Google, Apple, GitHub, Facebook, Microsoft, Passkey, Firebase, Anonymous).

In-memory and optional Redis caches via `session.caches`. Cached objects must be serializable models or primitives supported by Serverpod.

Priority (highest wins): **Dart config object** > **environment variables** > **YAML config files**. YAML lives in `config/`. Secrets in `config/passwords.yaml` or env vars with `SERVERPOD_PASSWORD_` prefix.

PostgreSQL via ORM. Models with `table` in `.spy.yaml` get generated ORM code.

Flow: server issues upload description → client uploads → server verifies. Default storage is the database; use S3 or GCP for production.

Modules are reusable Serverpod packages with server, client, and optionally Flutter code in their own endpoint/model namespaces.

Serverpod is an open-source backend framework for Flutter written in Dart. A Serverpod project consists of three packages: a server, a generated client, and a Flutter app. The server exposes typed endpoints that the client calls via RPC. Models are defined in YAML and generate Dart classes for both

Generated test tools let you call endpoints in tests with full server context (DB, caching, etc.). Import the **generated** test tools file, not `serverpod_test` directly — it re-exports everything needed.

Built on Relic, shares `Session` (DB, logging, auth) with the main server. Runs on `webServer` port (default 8082). Use for REST, webhooks, static files, SPAs, or server-rendered pages.

Define Serverpod endpoints, use Session, pass parameters, and call from client. Use when creating RPC endpoints, working with Session, or client code generation.

Define Serverpod data models in YAML (.spy.yaml), serialization, database tables, relations, enums, and exceptions. Use when creating or editing models, database schema, .spy.yaml files, or Serverpod ORM entities.