Starburst Enterprise
Commercial distributed SQL and analytics platform deployed by Helm into customer-operated Kubernetes.
6 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Starburst Enterprise Brotli security update
Starburst documents fixed builds for critical Brotli CVE-2026-111497.
Scope: Fixed in 482-e.6, 480-e.13, 479-e.20, and 477-e.24; branch-specific affected ranges follow the vendor advisory.
Exposure depends on the bundled Brotli decoder and reachable processing paths.
Action: Upgrade the installed maintained branch to its fixed or later patch.
Primary source · Reviewed 2026-11-18
What lands where
Supplied by
Vendor or project
Authenticated Starburst Enterprise Helm charts on EKS, AKS or GKE
Runs in
Documented customer environment
Coordinator, worker and supporting services on Kubernetes with external service database and data-source connections.
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Your team
Customer manages Kubernetes, dedicated node capacity, storage, networking, service database, catalogs, secrets, backups and upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Starburst Enterprise Kubernetes deployment on EKS, AKS and GKE ↗ · Source checked 2026-11-17
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Starburst Enterprise Kubernetes deployment on EKS, AKS and GKE ↗ · Source checked 2026-11-17
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Starburst Enterprise Kubernetes deployment on EKS, AKS and GKE ↗ · Source checked 2026-11-17
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Authenticated Starburst Enterprise Helm charts on EKS, AKS or GKE |
|---|---|
| Infrastructure | Servers / containers Starburst Enterprise runs persistent coordinator, worker and supporting containers on Kubernetes and requires an external service database plus production capacity planning. |
| Licensing model | Commercial Only Starburst Enterprise requires a commercial license and access to authenticated container and Helm registries. The open-source Trino project is separate. |
| License | Commercial Starburst Enterprise license and entitled registry access required. |
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.
12 of 12 fields researched (100%) · 8 documented · 4 unresolved. Evidence coverage is not a feature score.
- Marketplace delivery
AvailableEvidence and scope for Marketplace delivery
SEP documents AWS EKS Marketplace deployment and Google Cloud Marketplace subscriptions. The Google Click to Deploy path is recommended only for small proofs of concept; prefer the documented command-line customization path.
Starburst Enterprise Marketplace, not Galaxy SaaS · Source ↗ · Google Cloud Marketplace limits and support ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
- Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility
SEP Marketplace deployment is documented, but the reviewed procurement guides do not establish qualifying fees and contract-specific commitment treatment. Galaxy claims were excluded.
Reviewed public evidence for Starburst Enterprise; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17
Sources checked — unresolved · Editor reviewed.
- Single sign-on
AvailableEvidence and scope for Single sign-on
SEP supports SAML 2.0 SSO configured on the coordinator. TLS is required; authentication is separate from the access-control rules that grant data permissions.
Starburst Enterprise, not Galaxy or upstream Trino · Source ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
- SCIM provisioning
AvailableEvidence and scope for SCIM provisioning
SEP documents SCIM user/group synchronization with its internal group provider and a configured secret token. Configure a supported external provider and network reachability; authorization to data remains separate.
SEP self-managed SCIM configuration · Source ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
- Compliance attestations
Not confirmedEvidence and scope for Compliance attestations
The reviewed Starburst Enterprise material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage.
Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited · Source ↗ · Reviewed 2026-11-17
Sources checked — unresolved · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
Authentication requires TLS/HTTPS and a shared secret. Apply the selected authenticator plus access-control system and restrict coordinator exposure; provisioning identities does not grant unrestricted data access. Current advisory review: Starburst documents fixed builds for critical Brotli CVE-2026-111497. Upgrade the installed maintained branch to its fixed or later patch.
Starburst Enterprise authentication requirements Fixed in 482-e.6, 480-e.13, 479-e.20, and 477-e.24; branch-specific affected ranges follow the vendor advisory. · Source ↗ · Prior security-controls source ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- Air-gapped operation
Not confirmedEvidence and scope for Air-gapped operation
SEP requires entitled images/charts and a licence. The reviewed Kubernetes requirements do not establish complete isolated licence renewal, connector dependencies and upgrades.
Reviewed public evidence for Starburst Enterprise; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
SEP supplies licensed Helm charts and images in its Harbor registry. Obtain customer credentials and configure the coordinator, workers and backend database; the legacy AWS CloudFormation path is deprecated.
Supported Kubernetes SEP installation · Source ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The Kubernetes guide specifies identical dedicated nodes with 16–64 cores and 64–256 GB RAM, one coordinator/worker per node, plus an externally managed service database. This is substantially more than a small general-purpose app cluster.
SEP Kubernetes node requirements; workload and HA counts still need design · Source ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Starburst Enterprise requires a commercial license and access to authenticated container and Helm registries. The open-source Trino project is separate.
Starburst Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate · Source ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
- Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate
Confirm coordinator failover, worker concurrency, backend database, data-source storage and licensed cores. The documented dedicated-node minimum does not by itself establish the required HA query architecture. A complete monthly operating estimate is not established.
Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit · Source ↗ · Reviewed 2026-11-17
Sources checked — unresolved · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The version policy distinguishes LTS and STS. The reviewed table lists 482-e.x LTS through 2027-08-31 and 483-e STS from October 2026 until the next release; select a supported line and review breaking changes.
SEP support policy and month-level release table; not a patch timestamp · Source ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
Scope & considerations
This entry covers Starburst Enterprise, not Starburst Galaxy or the upstream Trino project. Production Kubernetes deployment requires entitled images and charts, a Starburst license, dedicated adequately sized nodes and an external service database. The older AWS CloudFormation path is deprecated and is not presented as the current installation method. Starburst's November advisory fixes critical Brotli CVE-2026-111497 in 482-e.6, 480-e.13, 479-e.20, and 477-e.24. Upgrade the installed maintained branch to its fixed or later patch.
Category fit
- Data & analytics
- Distributed SQL query, federation and governed analytics across cloud data stores and lakehouse systems.
Compare within Data & analytics
- ActivityInfo (Self-Managed Server)Commercial self-managed data collection, relational records and program-reporting platform.
- Azure
- Airbyte Self-ManagedSelf-managed data movement and ELT platform with customer-operated connectors and job execution.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- 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
- Apache DruidColumn-oriented analytics database for interactive queries over streaming and historical event data.
- AWS
- Azure
- Google Cloud
- Apache SupersetBusiness intelligence and data exploration platform for SQL analysis, visualizations and shared dashboards.
- AWS
- AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
- AWS
- Azure Trusted Research EnvironmentOpen-source reference platform for isolated research workspaces and controlled data movement.
- Azure
- Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
- Google Cloud
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
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Starburst Enterprise on Kubernetes ↗docs.starburst.io
- Kubernetes requirements ↗docs.starburst.io
- AWS ecosystem and deployment ↗docs.starburst.io
- Microsoft Azure ecosystem ↗docs.starburst.io
- Google Cloud ecosystem ↗docs.starburst.io
- Starburst security advisories ↗docs.starburst.io
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Starburst Enterprise Kubernetes deployment on EKS, AKS and GKE ↗ · AWS, Azure, Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
Starburst documents its Enterprise Helm deployment on customer Kubernetes and explicitly supports Amazon EKS, Azure AKS and Google GKE with provider-specific ecosystem guidance. Customers operate the cluster and data services.
- Starburst Enterprise Kubernetes deployment on EKS, AKS and GKE ↗ · AWS, Azure, Google Cloud
- Infrastructure evidenceChecked
- Licensing evidenceChecked