Softwr

Machine Learning · head to head

Amazon Redshift ML vs Trino

Amazon Redshift ML logo

Amazon Redshift ML

Machine Learning

SQL statements in Redshift that train models on SageMaker and return them as functions

From
Free
Free plan
Yes
Trino logo

Trino

Databases

A distributed SQL engine that queries data where it already lives, across object storage, warehouses and operational databases.

From
Free
Free plan
Yes

The short version

  • Trino is free; Amazon Redshift ML starts at $0.25/mo.
  • Only Amazon Redshift ML lists CREATE MODEL in SQL; only Trino lists federated querying.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Amazon Redshift ML and Trino actually diverge.

Attributes where Amazon Redshift ML and Trino differ
AttributeAmazon Redshift MLTrino
Pricing modelUsage-basedOpen-source
CategoryMachine LearningDatabases

Identical on both: starting price (Free), free tier (Yes), platforms (Web).

Not yet recorded: founded for Trino.

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Amazon Redshift ML

  • CREATE MODEL in SQL
  • Automatic model selection
  • Local inference
  • Bring your own model
  • Algorithm selection
  • Cost ceiling controls
  • Existing warehouse security
  • Batch and interactive scoring

Only in Trino

  • Federated querying
  • Connector architecture
  • Predicate and aggregation pushdown
  • Massively parallel execution
  • Fault-tolerant execution
  • Resource groups
  • Iceberg and Delta table support
  • Standard client protocols

What people use each for

The jobs each tool is most often brought in to do.

Amazon Redshift ML

  • Adding a churn or propensity score to an existing dashboard where the data is already in Redshift and nobody needs a bespoke modelnot Trino
  • Letting an analytics team test whether a predictive column has any business value before asking for data science headcountnot Trino
  • Scoring rows inside a SQL pipeline where moving data out to a separate service would add fragility for little benefitnot Trino
  • Organisations committed to AWS whose main constraint is a data science backlog rather than modelling sophisticationnot Trino

Trino

  • Ad hoc analysis that spans a data lake and one or more operational databases, without building an ingestion pipeline firstnot Amazon Redshift ML
  • Serving a BI tool a single SQL endpoint over an estate that is actually several separate storage systemsnot Amazon Redshift ML
  • Querying Iceberg or Delta tables on object storage interactively, as the compute layer of a lakehousenot Amazon Redshift ML
  • Investigating whether a dataset is worth ingesting, by querying it in place before committing to a pipeline for itnot Amazon Redshift ML

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Amazon Redshift ML

  • Training is billed by SageMaker separately from Redshift, so a feature that looks like a free SQL statement produces a second line item on a different part of the bill that the analyst who ran it usually cannot see
  • Autopilot searches many candidate models by default and the duration and cost of CREATE MODEL scale with the data size and the MAX_CELLS setting, so an unconstrained statement against a large table is an expensive accident rather than an experiment
  • Local inference runs on the Redshift cluster itself, so scoring millions of rows competes for the resources the warehouse exists to provide, and the remote inference alternative adds a per-batch network call plus an hourly SageMaker endpoint charge that persists whether or not anyone queries it
  • The supported problem types are limited to what the exposed algorithms cover, so anything involving text, images, sequences, a custom loss function or a bespoke evaluation metric is out of scope and has to be built conventionally
  • There is no retraining schedule, drift detection or model registry, so a model created by a statement stays exactly as trained until somebody remembers to recreate it, and nothing in the warehouse will report that its accuracy has decayed

Trino

  • Trino stores nothing and computes no statistics of its own, so the plan it produces is only as good as the partitioning, file sizes and table statistics on the source; a Hive table of thousands of small files or a lake with no stats produces a slow query the engine cannot improve
  • Federated queries pull data out of the systems they touch, so a join between a lake table and a production Postgres can put a full table scan onto an OLTP database that other applications depend on, and the person who wrote the query will not see the incident it causes
  • Releases come roughly every one to two weeks with no community long-term support line, and deprecations arrive quickly, so you either dedicate someone to keeping current or you buy Starburst Enterprise for a supported long-term version
  • It is memory-based and disk spilling was deprecated in favour of fault-tolerant execution, so a query exceeding cluster memory fails outright rather than degrading; enabling fault-tolerant execution requires an external exchange store on object storage and makes queries measurably slower
  • It is a query engine and not a warehouse: there is no built-in job scheduling, no incremental materialised view maintenance and no transformation framework, so producing curated tables still needs dbt or an equivalent layer that somebody has to own
  • The 2020 fork split the ecosystem, so documentation, connectors, Stack Overflow answers and vendor material written before then describe PrestoDB, which is now a different project with different behaviour, and following the wrong one wastes real time

Pricing, plan by plan

Amazon Redshift ML

Free
  • Free TrialFree
    • 2-month trial
    • 750 DC2.Large hours
  • On-Demand$0.25/hour
    • Per-node pricing
    • SageMaker training

Trino

Free

No published plan breakdown. See the Trino review.

Which should you pick?

Choose Amazon Redshift ML if

  • You need create model in sql.
  • You want to start without paying.
  • You also want automatic model selection.

Choose Trino if

  • You need federated querying.
  • You want to start without paying.
  • You also want connector architecture.

Questions people ask

Is Amazon Redshift ML or Trino better?
Neither clearly leads. Amazon Redshift ML starts at Free and Trino at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Amazon Redshift ML or Trino?
Amazon Redshift ML starts at Free and Trino at Free.
Does Amazon Redshift ML or Trino run on more platforms?
Both run on Web, so platform support will not decide this one for you.
Can I use Amazon Redshift ML for free?
Both have a free tier, so you can try either at no cost before committing.
What is Amazon Redshift ML best used for?
Amazon Redshift ML is most often used for adding a churn or propensity score to an existing dashboard where the data is already in redshift and nobody needs a bespoke model, letting an analytics team test whether a predictive column has any business value before asking for data science headcount, scoring rows inside a sql pipeline where moving data out to a separate service would add fragility for little benefit, organisations committed to aws whose main constraint is a data science backlog rather than modelling sophistication. Of those, adding a churn or propensity score to an existing dashboard where the data is already in redshift and nobody needs a bespoke model and letting an analytics team test whether a predictive column has any business value before asking for data science headcount are not what Trino is typically brought in for.
What can Amazon Redshift ML do that Trino cannot?
Amazon Redshift ML covers CREATE MODEL in SQL, Automatic model selection, Local inference, Bring your own model. Trino covers Federated querying, Connector architecture, Predicate and aggregation pushdown, Massively parallel execution.

Answered from the vendors’ own pages

Amazon Redshift ML: Does it require SageMaker?

Yes. Redshift ML is an interface; the training happens in SageMaker and needs an IAM role and an S3 bucket for the intermediate data.

Trino: What is the difference between Trino and Presto?

They share an origin. The original creators left Meta and renamed their fork from PrestoSQL to Trino in December 2020; PrestoDB continues separately under the Linux Foundation. They have diverged in features, connectors and SQL behaviour, so material written for one may not apply to the other.

Amazon Redshift ML: Is there an extra charge?

The SQL interface is part of Redshift, but the training runs as a SageMaker job charged at SageMaker rates, and a remote inference endpoint is billed for as long as it exists.

Trino: Does Trino replace my data warehouse?

Not on its own. It is compute without storage, scheduling or transformation. Paired with Iceberg or Delta on object storage and something like dbt for modelling it can serve as a lakehouse; used alone it is a query layer over what you already have.

Amazon Redshift ML: What kinds of model can it build?

Regression, binary and multiclass classification through the automatic path, plus direct use of XGBoost, linear learner, multilayer perceptron and K-means. Anything beyond structured tabular prediction is out of scope.

Trino: Why is my federated query slow?

Usually because a connector could not push a filter or aggregation down, so Trino is pulling whole tables across the network to join them itself. The fix is usually better source-side partitioning or statistics, or ingesting that source rather than federating it.

Amazon Redshift ML: Can I use a model I trained myself?

Yes, through the bring-your-own-model path, either compiled into the cluster for local inference or called as a remote SageMaker endpoint.

Trino: What happens when a query runs out of memory?

It fails. Disk spilling was deprecated in favour of fault-tolerant execution, which checkpoints to an external exchange store such as S3 and lets long queries survive memory pressure and worker loss, at the cost of noticeably slower execution.

Amazon Redshift ML: Does it retrain automatically?

No. Retraining means running CREATE MODEL again, on a schedule you build yourself, and nothing in the product monitors whether it is needed.

Trino: Is there commercial support?

Yes, from Starburst, which offers Starburst Enterprise with long-term supported releases and Starburst Galaxy as a managed service. The open source project itself has no long-term support line.

Share

Related pages

Other head to heads