Examples
Use these source references to connect Effect Auth to your application's accounts, database, and request handlers. Each composition uses the package's public API.
Authentication methods
| Source | Integration |
|---|---|
| Passwords | Registration, sign-in, and account changes. |
| Codes, magic links, and address workflows. | |
| Phone OTP | Phone authentication backed by SQLite on Bun. |
| Password hashing | Hashing policy and verification. |
The GitHub OAuth composition shows provider and application wiring.
Sessions and identity
| Source | Integration |
|---|---|
| Sessions | Session lifecycle and strategy selection. |
| Identity | Application-owned subject identifiers and identity resolution. |
| Proofs | Bound proofs and private delivery. |
| Hooks | Lifecycle hook composition. |
Database adapters
| Source | Integration |
|---|---|
| SQLite on Bun | Drizzle and SQLite on Bun. |
| SQLite WASM | Drizzle and SQLite WASM. |
The Node SQLite and libSQL files provide additional composition references. See adapters and persistence for transaction and retry requirements.
HTTP and browser clients
The Studio example separates auth composition, HTTP server, and browser client. These are integration references rather than a packaged application. The HTTP and client state guide explains their shared contract.
Example stores, keys, delivery services, and policies are disposable development fixtures. Replace them with your application's authority and durable adapters before using the same composition in a deployed service.