{"catalog":"https://launchinyourcloud.com/api/v1/catalog.json","catalogRevision":"170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde","kind":"listing","listing":{"architecture":"Dedicated customer-cloud instances run task brokers and reactors. Estuary's control plane starts connectors and applies task configurations.","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Captures, transforms, and delivers data to analytical destinations through managed connectors."},"cloudEvidence":[{"clouds":["aws"],"notes":"The documented cross-account IAM role uses an external ID and grants AmazonEC2FullAccess.","reviewed":"2026-11-21","sourceType":"vendor-documentation","title":"Estuary BYOC on AWS","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The guide adds Estuary's deployment application and grants a role scoped to the customer's subscription.","reviewed":"2026-11-21","sourceType":"vendor-documentation","title":"Estuary BYOC on Azure","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The guide asks for project-level Editor access for Estuary's controller principal.","reviewed":"2026-11-21","sourceType":"vendor-documentation","title":"Estuary BYOC on Google Cloud","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-21","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"vendor-hosted","evidence":[0],"operator":"vendor"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"vendor-hosted","evidence":[1],"operator":"vendor"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"vendor-hosted","evidence":[2],"operator":"vendor"}],"description":"Managed data capture, transformation, and delivery with a dedicated data plane in the customer's cloud account.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Dedicated Enterprise BYOC data plane; quantitative production sizing unresolved.","source":"https://docs.estuary.dev/private-byoc/networking/","status":"inconclusive","summary":"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."},"iac":{"reviewed":"2026-11-21","scope":"Estuary-managed BYOC runtime deployment artifact unresolved.","source":"https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/","status":"inconclusive","summary":"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.","supportingSources":[{"title":"Azure onboarding permissions","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/"},{"title":"Google Cloud onboarding permissions","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/"}]},"licensePricing":{"reviewed":"2026-11-21","scope":"Enterprise managed BYOC commercial terms and separate cloud bill; request a quote.","source":"https://docs.estuary.dev/getting-started/pricing/","status":"documented","summary":"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."},"scim":{"availability":"unavailable","reviewed":"2026-11-21","scope":"Documented Estuary dashboard provisioning flow for Enterprise BYOC.","source":"https://docs.estuary.dev/getting-started/sso-setup/","status":"documented","summary":"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."},"sso":{"availability":"available","reviewed":"2026-11-21","scope":"Enterprise BYOC dashboard SSO; coordinate domain and IdP configuration with Estuary.","source":"https://docs.estuary.dev/getting-started/sso-setup/","status":"documented","summary":"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.","supportingSources":[{"title":"Enterprise BYOC and SSO entitlement","url":"https://docs.estuary.dev/getting-started/pricing/"}]}},"id":"estuary-byoc","infrastructure":["servers"],"infrastructureNotes":"Dedicated customer-cloud instances run task brokers and reactors. Estuary's control plane starts connectors and applies task configurations.","infrastructureReviewed":"2026-11-21","infrastructureSources":["https://docs.estuary.dev/private-byoc/networking/"],"install":"Arrange Enterprise BYOC onboarding and grant the documented permissions in a separate AWS account, Azure subscription, or Google Cloud project.","installMethods":["vendor-assisted"],"kind":"platform","license":"Commercial BYOC under an annual Enterprise agreement with custom pricing.","licenseModel":"commercial-only","licenseModelNotes":"Commercial BYOC under an annual Enterprise agreement with custom pricing.","licenseModelSources":["https://docs.estuary.dev/getting-started/pricing/"],"licenseReviewed":"2026-11-21","model":"BYOC","modelLabel":"Vendor-operated BYOC","name":"Estuary BYOC","notes":"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.","operationReview":{"controlPlane":"vendor-hosted","modelLabel":"Vendor-operated BYOC","operator":"vendor","reviewed":"2026-11-21","source":"https://docs.estuary.dev/private-byoc/byoc-deployments/","summary":"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.","supportingSources":[{"title":"Control-plane and management connectivity","url":"https://docs.estuary.dev/private-byoc/networking/"}]},"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.","publisher":false,"reviewed":"2026-11-21","sources":[{"title":"BYOC operating model","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/"},{"title":"Data-plane network requirements","url":"https://docs.estuary.dev/private-byoc/networking/"},{"title":"Enterprise BYOC pricing","url":"https://docs.estuary.dev/getting-started/pricing/"},{"title":"Pull published specifications","url":"https://docs.estuary.dev/guides/flowctl/edit-specification-locally/"},{"title":"Estuary BYOC on AWS","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/"},{"title":"Estuary BYOC on Azure","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/"},{"title":"Estuary BYOC on Google Cloud","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/"}],"url":"https://launchinyourcloud.com/directory/estuary-byoc/","website":"https://estuary.dev/"},"schemaVersion":1,"url":"https://launchinyourcloud.com/directory/estuary-byoc/"}