Docs
Private deployments
Run Riptide in your own infrastructure under a commercial agreement. Start with one regional serving cell, then add cells as traffic or data-residency requirements grow. OpenTofu modules and Helm charts provide the deployment configuration.
Start with one cell
A cell contains serving services and their local stores, configured through an OpenTofu module. Start in one region while you validate traffic and configuration. The control plane, including Postgres, the admin API, and the Plan Compiler, can run centrally.
Add cells as you scale
Add a cell for each additional region using the same deployment modules. Roll out each cell independently and check its health before sending traffic to it.
Roll out changes gradually
Service Helm charts and GitOps configuration support canary rollouts and automated rollback based on service-level objectives. Review database migrations before applying them and keep a rollback plan for each release.
Secrets and keys
Supply secrets through a managed secret store or environment variables. Tenant signing keys use KMS envelope encryption and key IDs that support rotation.
Prefer managed?
If you'd rather not operate the infrastructure yourself, the same platform is available as a managed, white-label deployment starting at the Starter plan. See pricing.
After the stack is up, follow the CLI walkthrough to load sample inventory and check an ad response.
Planning a private deployment?
Share your expected traffic, ad formats, and the systems you need to connect. We can help you choose a plan and identify the setup work.