Authentication

Choose credentials for a self-hosted control plane or Rivet Cloud.

The control plane checks credentials before serving management requests or routing Actor traffic. Application-level authorization still belongs in your Actor. See Authentication.

Self-hosted control plane

The configured auth.admin_token grants every operation in every namespace. Keep it in your backend or secret store. Use it to create namespaces and issue scoped JWTs for applications.

A JWT grants access to one namespace and an explicit set of resources and operations. Give browser clients only the permissions they need, and keep tokens that can register nodes or manage pools on your backend.

Pass credentials in Authorization: Bearer <token>, or use an endpoint URL such as https://production:<token>@rivet.mycompany.com.

Rivet Cloud

Get your namespace endpoints and credentials from the Rivet Cloud dashboard. Keep secret credentials on your backend. See Rivet Cloud for managed deployment and token settings.