Restate has announced Restate BYOC: a version of Restate Cloud that runs inside your own cloud account and VPC. Instead of hosting your integration flows on Restate’s infrastructure, BYOC deploys the same managed service into your AWS or GCP account, with Azure support on the way. Your compute, storage, and application data stay under your ownership, while Restate handles upgrades, monitoring, and operational management.
This matters because durable execution sits between the systems that run your business: orders, ERP, warehouse, finance, and storefronts. BYOC means no application data crosses into Restate’s infrastructure, and links to your application VPCs can stay private. The pricing is based on reserved capacity rather than per action, which Restate says becomes materially cheaper at high volumes. Access is by request today, with public signup expected in the coming months.
How we are responding
We will treat BYOC as a deployment option for Restate-hosted integrations, not a mandatory change. For customers already on Restate Cloud, we will review whether BYOC fits your data residency, compliance, or scale needs once Azure support lands for those on Microsoft. For new designs, we will include BYOC in our architecture conversations wherever your integrations need to remain inside your own cloud account. We are also validating how BYOC fits with Kori’s monitoring and our deployment pipeline, so the day-to-day support experience stays consistent.
What it means for you
If your integrations run on Restate Cloud today, nothing changes unless you choose to move. BYOC is worth considering when you need stricter data ownership, private network paths, or predictable capacity pricing at higher volumes. If you are on AWS or GCP and operate in a regulated sector, or you simply prefer your data to remain inside your account, ask us about it now. If you are on Azure, support is coming soon, and we will flag it when it is ready. Talk to us if you would like to review whether BYOC fits your setup.
