
# Trino

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

Canonical page: https://launchinyourcloud.com/directory/trino/
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.


## Trino

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

- Listing: https://launchinyourcloud.com/directory/trino/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Trino.
- Licensing model: open-source
- Installation: Deploy the official server tarball on Linux hosts and configure coordinator, worker and catalog settings.
- Architecture: Customer-operated Java coordinator and worker processes connected to configured data sources
- Operations: Customer manages worker capacity, catalogs, credentials, TLS, query policies, logs and version compatibility.
- Product website: https://trino.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

Apache License 2.0 for upstream Trino. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

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.


### 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.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://trino.io/episodes/31.html (checked 2026-11-12). 


### Cloud deployment evidence

- Trino project deployment walkthrough on Amazon EKS (aws): https://trino.io/episodes/31.html
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and 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.

Reviewed 2026-11-10.

- Foundation and governance: https://trino.io/docs/current/appendix/legal-notices.html

- Current release history: https://trino.io/docs/current/release.html

- Named user directory: https://trino.io/users.html

### Sources

- Official installation and runtime: https://trino.io/docs/current/installation/deployment.html

- Upstream project and capabilities: https://github.com/trinodb/trino

- Current upstream license: https://trino.io/docs/current/appendix/legal-notices.html

- Coordinator, workers and catalogs: https://trino.io/docs/current/overview/concepts.html

### Licensing sources

- https://trino.io/docs/current/appendix/legal-notices.html

### Infrastructure sources

- https://trino.io/docs/current/installation/deployment.html


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 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. 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. Scope: Trino coordinator authentication; connector authorization remains separate. Source: https://trino.io/docs/current/security/oauth2.html (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://trino.io/docs/current/installation/deployment.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. 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. Scope: Trino 484 node/JVM guidelines; topology and workload require sizing. Source: https://trino.io/docs/current/installation/deployment.html (reviewed 2026-11-20).

- License pricing: Documented. 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. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/trinodb/trino/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: Upstream trinodb/trino release record; commercial editions and deployment packages may differ. Source: https://github.com/trinodb/trino/releases/tag/484 (reviewed 2026-11-14).






