Keeping a managed service and keeping it in your own cloud account do not have to be opposite choices. Restate’s Bring-Your-Own-Cloud announcement, published on 7 July 2026, describes a managed Restate deployment inside the customer’s account and private network.
For businesses with specific hosting requirements, the useful question is where integration data is processed, who can access it and who looks after the service. BYOC gives those questions another possible answer.
What stays in your account
Restate coordinates the steps of a process, such as moving an order between a storefront, ERP and warehouse. In the BYOC model, the compute, storage and application data held by Restate sit in your cloud account, while Restate manages the service’s upgrades and operation.
According to the announcement, Restate’s management service receives operational metrics and metadata, while its operators cannot access application data. Connections to your other private cloud networks can also stay private. 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 your organisation has a defined need for private networking, a particular hosting location or control over the account running the service. Account ownership is not a compliance certificate. The region, access controls, supplier terms and your own obligations still need checking.
The pricing model is based on reserved processing capacity. Compare the service charge and your underlying cloud costs against actual workload and peak demand. 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.
