Trino

Distributed SQL engine for querying data lakes and federated enterprise data sources.

4 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

    Deploy the official server tarball on Linux hosts and configure coordinator, worker and catalog settings.

  2. Operated by

    Your team

    Customer manages worker capacity, catalogs, credentials, TLS, query policies, logs and version compatibility.

Deployment boundaries by provider

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

Install methodDeploy the official server tarball on Linux hosts and configure coordinator, worker and catalog settings.
InfrastructureServers / containers
Customer-operated Java coordinator and worker processes connected to configured data sources. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.
Licensing modelOpen Source / Open Core
Apache License 2.0 for upstream Trino. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.
LicenseApache License 2.0 for upstream Trino.

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%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.

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

The coordinator supports OAuth 2.0 authentication with OIDC discovery configuration. Configure HTTPS, client credentials and the compatible browser/CLI flow; this is not automatic identity propagation to every connected database.

Trino coordinator authentication; connector authorization remains separate · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The server tarball is installed on supported Linux hosts with separate coordinator/worker/catalog configuration. The current guide requires a specific supported Java runtime; matching the Trino release and Java version is essential.

Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The current deployment guide recommends production memory allocations above 32 GB per node and typically assigns 70–85% of node RAM to the JVM. Coordinators, workers, query concurrency, connectors and spill storage determine the cluster size. The sample 16-GB heap configuration is not a total production or HA minimum.

Trino 484 node/JVM guidelines; topology and workload require sizing · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate.

Upstream core licence; commercial features, support and hosting priced separately · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

The publisher-designated GitHub release checked was 484, published 2026-10-16. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.

Upstream trinodb/trino release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14

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.
SCIM provisioning
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.

Scope & considerations

The reviewed current deployment documentation requires a supported Java runtime. Data stays in its configured source systems; querying a remote catalog can cross account or network boundaries.

Community & maintenance

The Trino Software Foundation supports a volunteer-contributed project. The official release index records multiple 2026 releases, and its user directory describes named production users.

Category fit

Data & analytics
Distributed SQL query engine that analyzes data across configured catalogs and data sources; it does not replace those databases or object stores.

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.

    • Trino project deployment walkthrough on Amazon EKS ↗ · AWS

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

      The project walkthrough creates an EKS cluster and installs the Trino Helm chart into it. The published example includes older Kubernetes and tooling versions; use currently supported versions and review production configuration. This is self-operated Trino, not an EMR or Starburst service.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory