Estuary BYOC

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

7 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Arrange Enterprise BYOC onboarding and grant the documented permissions in a separate AWS account, Azure subscription, or Google Cloud project.

    External vendor control plane

  2. Operated by

    Vendor or service partner

    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.

Deployment boundaries by provider
  • AWS: Customer cloud account · Vendor / partner-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Estuary BYOC on AWS ↗ · Source checked 2026-11-21

  • Azure: Customer cloud account · Vendor / partner-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Estuary BYOC on Azure ↗ · Source checked 2026-11-21

  • Google Cloud: Customer cloud account · Vendor / partner-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Estuary BYOC on Google Cloud ↗ · Source checked 2026-11-21

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.

Operating responsibility source ↗ · Checked 2026-11-21

Control-plane and management connectivity ↗

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodArrange Enterprise BYOC onboarding and grant the documented permissions in a separate AWS account, Azure subscription, or Google Cloud project.
InfrastructureServers / containers
Dedicated customer-cloud instances run task brokers and reactors. Estuary's control plane starts connectors and applies task configurations.
Licensing modelCommercial Only
Commercial BYOC under an annual Enterprise agreement with custom pricing.
LicenseCommercial BYOC under an annual Enterprise agreement with custom pricing.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 3 documented · 2 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

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.

Enterprise BYOC dashboard SSO; coordinate domain and IdP configuration with Estuary. · Source ↗ · Enterprise BYOC and SSO entitlement ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

SCIM provisioning
Not availableEvidence and scope for SCIM provisioning

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.

Documented Estuary dashboard provisioning flow for Enterprise BYOC. · Source ↗ · Reviewed 2026-11-21

Explicitly unsupported · Editor reviewed.

Deployment artifact / IaC
Not confirmedEvidence and scope for Deployment artifact / IaC

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.

Estuary-managed BYOC runtime deployment artifact unresolved. · Source ↗ · Azure onboarding permissions ↗ · Google Cloud onboarding permissions ↗ · Reviewed 2026-11-21

Sources checked — unresolved · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

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.

Dedicated Enterprise BYOC data plane; quantitative production sizing unresolved. · Source ↗ · Reviewed 2026-11-21

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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.

Enterprise managed BYOC commercial terms and separate cloud bill; request a quote. · Source ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

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.

Category fit

Data & analytics
Captures, transforms, and delivers data to analytical destinations through managed connectors.

Compare within Data & analytics

  • ActivityInfo (Self-Managed Server)Commercial self-managed data collection, relational records and program-reporting platform.
    • Azure
    Customer-operated · Commercial Only
  • Airbyte Self-ManagedSelf-managed data movement and ELT platform with customer-operated connectors and job execution.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Source Available
  • Apache Doris Self-HostedApache-licensed analytical database with upstream AWS EKS/Alibaba ACK/ACS guides and a separately packaged cloudimg Azure VM path.
    • AWS
    • Azure
    • Alibaba Cloud
    Customer-operated · Open Source / Open Core
  • Apache DruidColumn-oriented analytics database for interactive queries over streaming and historical event data.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Apache SupersetBusiness intelligence and data exploration platform for SQL analysis, visualizations and shared dashboards.
    • AWS
    Customer-operated · Open Source / Open Core
  • AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
    • AWS
    Customer-operated · Commercial Only
  • Azure Trusted Research EnvironmentOpen-source reference platform for isolated research workspaces and controlled data movement.
    • Azure
    Customer-operated · Open Source / Open Core
  • Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
    • Google Cloud
    Customer-operated · Open Source / Open Core

Showing 8 of 43 other listings in Data & analytics. These products address related workflows; read their category-fit notes before comparing scope. See all of Data & analytics →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Estuary BYOC on AWS ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.

      The documented cross-account IAM role uses an external ID and grants AmazonEC2FullAccess.

    • Estuary BYOC on Azure ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.

      The guide adds Estuary's deployment application and grants a role scoped to the customer's subscription.

    • Estuary BYOC on Google Cloud ↗ · Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.

      The guide asks for project-level Editor access for Estuary's controller principal.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory