Deploy

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

Deployment Options

Nodes 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 nodes

Rivet Cloud runs the control plane, storage, and your actor nodes. There is nothing to operate.

See the Cloud overview.

Rivet Cloud & bring your own nodes

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

See Deploy Nodes.

Bring your own cloud

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

See the BYOC quickstart.

Self-host

You run the nodes, the control plane, and its 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:

• Node: The process running your Rivet Actors, 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: Schedules Rivet Actors onto nodes, routes requests to them, and serves the API.
• Storage: An object storage bucket that holds each Rivet Actor’s durable data. The control plane replicates writes across its own disks first.

See Architecture for how they fit together.

Next steps

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