Run Rivet inside your perimeter.
Deploy Rivet in your VPC, embed it in your customers’ environments, or run it fully air-gapped. The same platform that powers Rivet Cloud, under your control.
Three ways to deploy.
Rivet ships as software you run, not a service you call out to. Pick the boundary, and Rivet stays inside it.
Your VPC
Run the same Rivet that powers our cloud as a single binary inside your perimeter. No outbound calls, no telemetry leaving your boundary.
Embedded in your customers
Ship Rivet inside your customer’s VPC, regulated environment, or on-prem hardware. They keep their data, you keep your product.
Air-gapped
Deploy on networks with no internet access. Everything Rivet needs ships in the artifact you install, so disconnected environments run the full platform.
Your compliance posture, intact.
Deploy inside the boundary your existing controls already cover. FedRAMP, HIPAA, and sovereign-cloud environments stay within your audit story because nothing leaves your perimeter. No new data processor to assess, no waiting on a vendor’s certification roadmap.
- No outbound connections required
- No telemetry by default
- Your data never leaves your boundary
- Air-gapped installs supported
- No new subprocessor to disclose
A footprint your ops team will sign off on.
Rivet self-hosts as a single binary or a Docker Compose file, and scales to Kubernetes when you need it. Most platforms in this space either require a multi-service cluster before you can evaluate them or only run on the vendor’s own cloud. Rivet starts as one process on one machine and grows with your deployment, so a proof of concept takes an afternoon instead of a quarter.
Single binary
One process to install, monitor, and upgrade. Ideal for evaluation, embedded deployments, and air-gapped installs.
Docker Compose
A complete environment in one file. Stand up Rivet alongside your existing services without changing how you operate them.
Kubernetes
Scale out across nodes and regions when traffic demands it. The same artifact you evaluated runs in production.
Bring Rivet inside your boundary.
Walk through your deployment model with an engineer, or start with the self-hosting docs and run it yourself.