
# Estuary BYOC

Managed data capture, transformation, and delivery with a dedicated data plane in the customer's cloud account.

Canonical page: https://launchinyourcloud.com/directory/estuary-byoc/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Estuary BYOC

Managed data capture, transformation, and delivery with a dedicated data plane in the customer's cloud account.

- Listing: https://launchinyourcloud.com/directory/estuary-byoc/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial BYOC under an annual Enterprise agreement with custom pricing.
- Licensing model: commercial-only
- Installation: Arrange Enterprise BYOC onboarding and grant the documented permissions in a separate AWS account, Azure subscription, or Google Cloud project.
- Architecture: Dedicated customer-cloud instances run task brokers and reactors. Estuary's control plane starts connectors and applies task configurations.
- Operations: Estuary provisions and manages data-plane resources, including patching, scaling, and deletion. The customer owns the cloud environment and manages its surrounding firewall, routing, and policies.
- Product website: https://estuary.dev/
- Source review: 2026-11-21; cloud review: 2026-11-21; licensing review: 2026-11-21; infrastructure review: 2026-11-21

### Scope and qualifications

The data plane accepts connections from Estuary's control plane and authorized users. Pipeline specifications can be pulled with flowctl. Confirm storage export and account teardown with Estuary.

Commercial BYOC under an annual Enterprise agreement with custom pricing.

Dedicated customer-cloud instances run task brokers and reactors. Estuary's control plane starts connectors and applies task configurations.


### Category fit

- data-analytics: Captures, transforms, and delivers data to analytical destinations through managed connectors.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/ (checked 2026-11-21). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/ (checked 2026-11-21). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/ (checked 2026-11-21). 

Operating responsibility: Estuary provisions, patches, scales and removes the customer-account data plane. Its vendor-operated control plane starts connectors and applies task configuration; the customer governs the surrounding cloud account, permissions and network policies. Source: https://docs.estuary.dev/private-byoc/byoc-deployments/ (checked 2026-11-21). Supporting source: Control-plane and management connectivity — https://docs.estuary.dev/private-byoc/networking/.


### Cloud deployment evidence

- Estuary BYOC on AWS (aws): https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/
  The documented cross-account IAM role uses an external ID and grants AmazonEC2FullAccess.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Estuary BYOC on Azure (azure): https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/
  The guide adds Estuary's deployment application and grants a role scoped to the customer's subscription.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Estuary BYOC on Google Cloud (gcp): https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/
  The guide asks for project-level Editor access for Estuary's controller principal.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.


### Sources

- BYOC operating model: https://docs.estuary.dev/private-byoc/byoc-deployments/

- Data-plane network requirements: https://docs.estuary.dev/private-byoc/networking/

- Enterprise BYOC pricing: https://docs.estuary.dev/getting-started/pricing/

- Pull published specifications: https://docs.estuary.dev/guides/flowctl/edit-specification-locally/

- Estuary BYOC on AWS: https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/

- Estuary BYOC on Azure: https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/

- Estuary BYOC on Google Cloud: https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/

### Licensing sources

- https://docs.estuary.dev/getting-started/pricing/

### Infrastructure sources

- https://docs.estuary.dev/private-byoc/networking/


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Enterprise plans, including BYOC, include SSO. Estuary documents support-assisted SAML 2.0 configuration for its hosted dashboard, with domain metadata and just-in-time account creation. This is control-plane user identity, separate from connector credentials and data-plane authentication. Scope: Enterprise BYOC dashboard SSO; coordinate domain and IdP configuration with Estuary.. Source: https://docs.estuary.dev/getting-started/sso-setup/ (reviewed 2026-11-21). Supporting source: Enterprise BYOC and SSO entitlement — https://docs.estuary.dev/getting-started/pricing/.

- SCIM provisioning: Explicitly unsupported. Estuary explicitly documents just-in-time SSO account creation rather than SCIM. Tenant administrators invite users and assign access after the SSO account is created. SAML support does not establish SCIM lifecycle provisioning. Scope: Documented Estuary dashboard provisioning flow for Enterprise BYOC.. Source: https://docs.estuary.dev/getting-started/sso-setup/ (reviewed 2026-11-21).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The provider guides document permissions and vendor-assisted provisioning. The AWS example creates a delegated IAM role with an external ID and AmazonEC2FullAccess; it does not expose a reviewed, versioned data-plane deployment template. Obtain the actual provisioning artifact, permission scope and rollback procedure from Estuary. An IAM policy example alone does not establish a reusable runtime installer. Scope: Estuary-managed BYOC runtime deployment artifact unresolved.. Source: https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/ (reviewed 2026-11-21). Supporting source: Azure onboarding permissions — https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/. Supporting source: Google Cloud onboarding permissions — https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/.

- Minimum footprint / sizing: Sources checked — unresolved. The networking guide identifies broker/reactor instances, coordination and management access, but does not publish a quantitative CPU/RAM/storage baseline or HA topology. Estuary sizes the managed data plane during onboarding. Obtain connector counts, data rates, retention, replay and recovery requirements before selecting resources; 100 users and 1 TB alone do not size a streaming pipeline. Scope: Dedicated Enterprise BYOC data plane; quantitative production sizing unresolved.. Source: https://docs.estuary.dev/private-byoc/networking/ (reviewed 2026-11-21).

- License pricing: Documented. BYOC is available on annual or multi-year Enterprise contracts with custom pricing based on data volume, connector instances, deployment model, term and support. The customer pays the cloud provider directly for infrastructure. Public Cloud-plan per-GB/task-hour examples do not quote the BYOC contract. Scope: Enterprise managed BYOC commercial terms and separate cloud bill; request a quote.. Source: https://docs.estuary.dev/getting-started/pricing/ (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






