Deploy

Choose where the control plane and your workers run: Rivet Cloud, bring your own cloud, or self-host.

Deployment Options

Workers always run your code, so you always own them. The options differ in where the control plane and storage run, and who operates them.

Rivet Cloud & managed workers

Rivet Cloud runs the control plane, storage, and your workers on Rivet Compute. Nothing to operate; deploy from the Rivet dashboard.

See the Cloud overview.

Rivet Cloud & bring your own worker

Rivet Cloud runs the control plane and storage. Your workers run on your own infrastructure and connect outbound, so you keep your code and data next to the rest of your stack.

See Deploy Workers.

Bring your own cloud

Rivet Enterprise Edition and FoundationDB run inside your VPC, operated by Rivet. An operator in your cluster pulls deployment instructions from Rivet Cloud and maintains the deployment. Your workers run alongside it.

See the BYOC quickstart.

Self-host

You run the workers, control plane, and storage. Choose this when you need to operate the stack yourself, including fully air-gapped deployments.

See Self-Host.

Architecture

Rivet has 3 core components:

• Worker: A process running your code with the Rivet SDK. It connects outbound to the control plane, so it never needs a public URL or an inbound firewall rule.
• Control plane: The orchestration service that manages actor lifecycle, routes messages, and serves the API.
• Storage: The persistence layer for actor state and the messaging infrastructure for real-time communication.

Next steps

• Deploy on Rivet Cloud
• Deploy workers
• Self-host the control plane