vpc-air-gapped

Deploying Rivet in a VPC or Air-Gapped Network IMPORTANT: Before doing anything, you MUST read BASE_SKILL.md in this skill's directory. It contains essential guidance on debugging, error handling, state management, deployment, and project setup. Those rules and patterns apply to all RivetKit work. Everything below assumes you have already read and understood it. Patterns for running self-hosted Rivet inside a private network: a VPC without internet egress, an on-premises rack, or a fully air-gapped environment. The engine is one service, the recommended single-node storage backend is the local file system, and the engine makes no outbound connections by default. Self-hosting is the only Rivet deployment model that supports air-gapped networks; see the Self-Hosting Overview for the full comparison with BYOC. What Runs Inside the Perimeter A self-hosted deployment has three components, all of which live inside your network: Component Role Inside the perimeter Your backend Your application server, including the runner that executes actor code Yes Rivet Engine Orchestration service that manages actor lifecycle, routes messages, and serves the dashboard and APIs Yes Storage Persistence for actor state. Local file system for single-node, PostgreSQL or FoundationDB for multi-node Yes There is no license server, no Rivet Cloud account, and no callback to rivet.dev . Clients inside the perimeter reach actors through the engine's gateway over your private network. See Architecture . Single-Binary Install Show more Installs 814 Repository rivet-dev/skills GitHub Stars 17 First Seen Jun 14, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Warn