Show HN: SQLite for Rivet Actors – one database per agent, tenant, or document
Summary
The article introduces Rivet Actors as a serverless primitive for stateful workloads and highlights one database per actor for granular ownership (per agent, session, tenant, or document). It covers built-in features like in-memory state, SQLite or JSON persistence, WebSockets, workflows, queues, and scheduling, and positions Rivet for multi-tenant, real-time, and AI-enabled applications. The piece also outlines deployment options (self-host, Rivet Cloud, open source) and common use cases such as per-tenant databases and collaborative documents.