Before you start
- Single engine on file-system storage (RocksDB on the volume). It is not highly available; multi-node Rivet needs PostgreSQL and NATS, which this preset does not set up.
- Port 6420 is the engine endpoint for the API, the dashboard and actor traffic. It is private by default; make it public only if runners or clients outside this cluster must reach it.
- Your actor code runs separately, as a RivetKit app that connects out to the engine. Deploy it as a worker service with RIVET_ENDPOINT and RIVET_TOKEN and a 60 second termination grace period (see the README).
- Back up the volume off-node. Keep the admin token stable: runners and the dashboard authenticate with it.
Required secrets
Configure these scoped secrets during deployment review in your Hakopod installation. Secret values stay out of the application TOML.
-
admin-token
Use this preset
- Open the Catalog in your own Hakopod dashboard and select Rivet Engine.
- Choose the project, environment, and application name. Set the required values and secret references.
- Review the generated configuration, resource requests, networking, and storage plan.
- Deploy, then inspect readiness and logs. Configure backups for persistent data before relying on the service.
Read the upstream setup documentation ↗
View native TOML and setup notes ↗
Pinned container image
rivetdev/engine:2.3.31@sha256:791b3592c90911af44513848358f568236c73348081eab221ca317119289aeb4
The catalog pins this image for reproducibility. Review upstream updates and compatibility before changing it.