Skip to main content
Restate BYOC (Bring Your Own Cloud) gives you the same fully-managed Restate Cloud experience, deployed as a private region inside your own cloud account and VPC. Your application data never leaves your infrastructure, and at high volume BYOC is dramatically cheaper than usage-based pricing.

​
Why BYOC?

BYOC is designed for organizations that need:
  • Data sovereignty — all data remains in your cloud account and chosen region
  • Network isolation — Restate workloads run in your VPC, and application data never crosses the public internet
  • Compliance — meet policies that require workloads to remain within customer-controlled infrastructure
  • Cost at scale — priced by reserved capacity, up to 10x cheaper at high volume than per-action pricing
  • Existing commitments — use your cloud provider savings plans, reserved instances, and negotiated pricing

​
How it works

A BYOC deployment has three layers:
  1. Foundation — You deploy a cloud-native template (CloudFormation on AWS, ARM on Azure) into your account. This creates the networking, secrets store, and a deployment agent that manages the rest of the infrastructure on Restate’s behalf.
  2. Infrastructure — The deployment agent provisions a Kubernetes cluster, container registry, certificate management, and supporting infrastructure. This happens automatically after the foundation is deployed.
  3. Application — Restate data plane components are deployed into the cluster: the ingress proxy, tunnel, Restate operator, and monitoring stack. Environment creation, updates, and scaling are managed by Restate’s control plane.
The deployment agent uses an egress-only polling model — it reaches out to Restate’s control plane to pull work, rather than receiving inbound commands. To manage the region’s environments, Restate’s control plane connects to your managed Kubernetes API endpoint (which you can restrict by IP allowlist) using a scoped token. Application data stays inside your VPC — it never crosses the public internet, and Restate operators can never see it.
For details on the security properties of each layer, see Security Model.

​
Supported cloud providers

Need a multi region or multi cloud deployment? Contact us on Discord or Slack to discuss your requirements.

​
Get started

BYOC deployments are set up in collaboration with the Restate team. To get started:

Contact Restate

Reach out to discuss your requirements and begin onboarding.

​
Frequently asked questions

​
General

AWS and GCP are generally available. Azure is in preview. Regions are deployed on demand based on your requirements. The infrastructure can be deployed in any region supported by EKS on AWS, GKE on GCP, or AKS on Azure.
Not currently. Restate’s ability to offer SLAs for availability and patching relies on having complete control over the infrastructure configuration. An enterprise distribution for Kubernetes that you manage may become available in the future.

​
Operations

Availability depends on the deployment topology you choose:
  • Single node: lower cost, but rolling updates require a brief restart
  • Multiple availability zones: survives a single availability zone failure and supports updates without downtime
Specific availability targets are agreed as part of your plan. Contact Restate to discuss SLAs for your deployment.
Restate coordinates Kubernetes upgrades with you:
  1. Restate notifies you 30 days before your cluster’s Kubernetes version reaches end of life.
  2. Upgrades are scheduled during your preferred maintenance window.
  3. The control plane is upgraded first, followed by rolling node upgrades.
  4. A rollback plan is documented before each upgrade.
Operational metrics that contain no customer data are sent to a metrics service managed by Restate. This enables proactive monitoring and alerting for cluster health.Logs from Restate environments and other cluster components remain inside the cluster. Authenticated customers can access environment logs through the Restate Cloud console.
Offboarding is a two step process coordinated with Restate:
  1. Restate deprovisions the application and infrastructure layers through the deployment agent.
  2. You delete the foundation stack, which removes the deployment agent, networking, and secrets store from your account.
Because everything runs in your account, you can confirm that no resources managed by Restate remain. Take any final snapshots or data exports before teardown because object storage data in your account is removed with the foundation stack.

​
Disaster recovery

Recovery depends on the topology:
  • Pod failure with high availability: another replica takes over without data loss
  • Availability zone failure with high availability: the environment continues from replicas in surviving zones without data loss
  • Full cluster loss: the environment is restored from the most recent object storage snapshot, with the recovery point determined by the configured snapshot interval
Concrete recovery objectives are agreed as part of your plan.
Cross region replication is not currently supported in BYOC. For multi region requirements, deploy separate environments in each region with application level coordination. Contact us on Discord or Slack to discuss your deployment.