You can now have a managed service and keep it in your own cloud account. Restate’s Bring-Your-Own-Cloud announcement, published on 7 July 2026, describes Restate running, managed by Restate, inside the customer’s own account and private network.
For businesses with hosting rules, the useful question is where integration data is processed, who can see it and who looks after the service. That is usually your IT lead’s question first and your auditor’s second. BYOC gives it another answer.
What stays in your account
Restate coordinates the steps of a process, such as moving an order between a storefront, ERP and warehouse. With BYOC, the servers, storage and data Restate holds sit in your cloud account. Restate still runs the service and its upgrades.
According to the announcement, Restate’s own service receives metrics and metadata about the running system, but its staff cannot see your data. Links to your other private networks can stay private too. That distinction matters: application data staying in your account does not mean there is no communication with the provider.
It also does not bring Shopify, your ERP or every other connected system into that account. You still need to understand the complete route your information takes, including external systems, logs and backups.
What it means for you
Consider BYOC if you have a clear need for private networking, a set hosting location or control over the account running the service. Account ownership is not a compliance certificate. The region, who has access, the supplier terms and your own obligations still need checking.
You pay for reserved capacity. Compare the service charge and your own cloud bill against your real workload and your busiest days. A capacity model can suit sustained high volumes; it is not automatically cheaper for a quieter integration.
The launch named AWS and Google Cloud as the initial options, with access by request. Confirm current cloud and regional availability directly with Restate, particularly for Azure, rather than treating a launch announcement as a delivery commitment.
BYOC is an option to assess, not a requirement to move a working integration. If your hosting rules or volumes have changed, talk through the requirements with us before planning a migration, and bring whoever owns the cloud account, because the decision is theirs to live with.
