Rivet on X: "Introducing Rivet BYOC ☁️ for AWS and Google Your data never leaves your security perimeter. Your entire agent infrastructure is in your VPC. Manage from the Rivet dashboard. https://t.co/34KpFNSL4g" / X

Post

Rivet
@rivet_dev
Introducing Rivet BYOC ☁️ for AWS and Google Your data never leaves your security perimeter. Your entire agent infrastructure is in your VPC. Manage from the Rivet dashboard. rivet.dev/changelog/2026…
00:00
3:22 PM · Sep 15, 2026
34.5K
Views
4
Rivet
@rivet_dev
Sep 15
No inbound rules. Your admin token stays in your cloud secret manager. Rivet Cloud never connects in. A Rivet operator runs in your Kubernetes cluster. It pulls commands from Rivet Cloud, applies updates to the control plane inside your cluster, and reports status back.
00:00
1
Rivet
@rivet_dev
Sep 15
BYOC is multi-region. Each region gets its own VPC, cluster, operator, and control plane. Data stays in the region that produced it: pin EU users to an EU region for GDPR, or keep regulated workloads in-country. Try it free for 14 days: create a BYOC project at
00:00
Manna Code
@MannaCodeAI
Sep 15
This is the right boundary. For a desktop agent, I want the same thing without a control-plane dependency: chats on my machine, keys in the OS credential manager, and BYOK across OpenAI or Anthropic-compatible endpoints (including local).

Introducing Rivet BYOC ☁️ for AWS and Google Your data never leaves your security perimeter. Your entire agent infrastructure is in your VPC. Manage from the Rivet dashboard. rivet.dev/changelog/2026…

00:00

3:22 PM · Sep 15, 2026

34.5K

Views