Note: This is the Vercel-optimized version of the per-tenant-database example. It uses the hono/vercel adapter and is configured for Vercel deployment.

Per-Tenant Database

Example project demonstrating per-company database isolation with Rivet Actor state.

Getting Started

git clone https://github.com/rivet-dev/rivet.git
cd rivet/examples/per-tenant-database
npm install
npm run dev

Features

Per-tenant isolation: Each company name maps to its own CompanyDatabase actor and state
State as the database: Employees and projects live in c.state for every actor instance
Action-driven updates: Add and list data through actions like addEmployee and listProjects
Live switching: Swap company names in the UI to see fully isolated datasets

Implementation

The dashboard connects to one CompanyDatabase actor per company. The actor key is the company name, and its state becomes that company database.

See the implementation in src/actors.ts and frontend/App.tsx.

Resources

Read more about state, actions, and events.

License

MIT