Softwr

Databases · head to head

CosmosDB vs Presto

CosmosDB logo

CosmosDB

Databases

Globally distributed, multi-model database service from Azure

From
Free
Rated
-
Full reviewWebsite
Presto logo

Presto

Databases

The Meta-lineage distributed SQL query engine, distinct from the Trino fork

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: CosmosDB autoscale provisioned throughput enforces a minimum of 1,000 RU/s, billed hourly whether or not the database is used; Presto the original creators and most of the active contributor base left for Trino in 2020, so Presto has the smaller community, fewer connectors and slower feature delivery of the two branches.
  • They diverge on capability: CosmosDB covers Global Distribution, Presto covers Federated querying.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which CosmosDB and Presto actually diverge.

Attributes where CosmosDB and Presto differ
AttributeCosmosDBPresto
Pricing modelusage-basedOpen source, no licence fee
PlatformsWeb, AzureLinux, Docker, Kubernetes
Founded1975Unknown

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Databases).

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 CosmosDB

  • Global Distribution
  • Multi-model APIs
  • Elastic Scaling
  • Five Consistency Levels
  • SLA-backed Latency
  • Automatic Indexing
  • Serverless
  • Azure Functions

Only in Presto

  • Federated querying
  • In-memory execution
  • Open table format support
  • Presto C++ workers
  • ANSI SQL
  • Pluggable connectors

What people use each for

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

CosmosDB

  • Running a globally distributed multi model database on Azurenot Presto
  • Serving low latency reads and writes from multiple Azure regionsnot Presto
  • Storing document, key value and graph data behind a managed servicenot Presto

Presto

  • An existing PrestoDB estate that needs continued upgrades rather than a migration to Trinonot CosmosDB
  • A team buying IBM watsonx.data, where Presto is the underlying query enginenot CosmosDB
  • Joining a Hive or Iceberg lake to an operational PostgreSQL database in one query without an ETL stepnot CosmosDB
  • Very large scale interactive SQL where the Meta-tested branch is a specific requirementnot CosmosDB

Where each one falls short

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

CosmosDB

  • Autoscale provisioned throughput enforces a minimum of 1,000 RU/s, billed hourly whether or not the database is used
  • Provisioned throughput is charged in every region the account is replicated to, so multi region accounts multiply the RU bill
  • Storage charges cover data, indexes and backups in each replicated region
  • Egress out of Azure and between regions is charged, though ingress is free
  • The free allowance is one account per Azure subscription, limited to 1,000 RU/s and 25 GB
  • RU/s rates vary by region and are only shown through the pricing calculator rather than a flat published rate

Presto

  • The original creators and most of the active contributor base left for Trino in 2020, so Presto has the smaller community, fewer connectors and slower feature delivery of the two branches.
  • Documentation, tutorials and Stack Overflow answers for the two projects are frequently mixed up, and a solution written for Trino often does not apply, which costs real debugging time.
  • It is a query engine with no storage of its own, so query performance is dictated by your file layout, partitioning and statistics, and a badly organised lake makes Presto look slow.
  • Memory-bound execution means a single large join can fail the whole query rather than spilling gracefully, and tuning cluster memory settings is a persistent operational chore.
  • Commercial support has consolidated into IBM since the Ahana acquisition, so the independent vendor market that once existed around Presto is largely gone.

Pricing, plan by plan

CosmosDB

Free
  • Free TierFree
    • 1000 RU/s
    • 25GB storage
    • First 12 months
  • ServerlessFree
    • Pay per request
    • Auto-scaling
    • Event-driven workloads

Presto

Free
  • PrestoFree
    • Apache 2.0 licence
    • Presto Foundation governance under the Linux Foundation
    • No node or query limits

Which should you pick?

Choose CosmosDB if

  • You need global distribution.
  • You want to start without paying.
  • You work on Web, Azure.
  • You also want multi-model apis.
CosmosDB review

Choose Presto if

  • You need federated querying.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes.
  • You also want in-memory execution.
Presto review

Questions people ask

Is CosmosDB or Presto better?
Neither clearly leads. CosmosDB starts at Free and Presto at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, CosmosDB or Presto?
CosmosDB starts at Free and Presto at Free.
Does CosmosDB or Presto run on more platforms?
CosmosDB runs on Web, Azure. Presto runs on Linux, Docker, Kubernetes.
Can I use CosmosDB for free?
Both have a free tier, so you can try either at no cost before committing.
What is CosmosDB best used for?
CosmosDB is most often used for running a globally distributed multi model database on azure, serving low latency reads and writes from multiple azure regions, storing document, key value and graph data behind a managed service. Of those, running a globally distributed multi model database on azure and serving low latency reads and writes from multiple azure regions are not what Presto is typically brought in for.
What can CosmosDB do that Presto cannot?
CosmosDB covers Global Distribution, Multi-model APIs, Elastic Scaling, Five Consistency Levels. Presto covers Federated querying, In-memory execution, Open table format support, Presto C++ workers.

Answered from the vendors’ own pages

CosmosDB: Is there a free tier for Azure Cosmos DB?

Yes, Cosmos DB offers a free tier with 1,000 RU/s of throughput and 25 GB of storage per month for the lifetime of the account, available to new accounts.

Source
Presto: Is this Presto or Trino?

This is PrestoDB, the branch that stayed at Facebook and moved to the Linux Foundation. Trino is the 2020 fork by the original creators.

CosmosDB: How is Cosmos DB priced after the free tier?

Cosmos DB uses three billing models: provisioned throughput billed per request unit per second, vCore pricing for certain APIs, or serverless consumption pricing where you pay only for requests processed. Reserved capacity offers 20% discount for one year or 30% for three years.

Source
Presto: Which should I choose for a new project?

Trino, in most cases. It has the larger community, more connectors and more commercial options.

CosmosDB: Can I change my pricing model after choosing one?

No. Once you select a compute pricing model and API, they cannot be changed. This choice is permanent for that database.

Source
Presto: Who maintains Presto now?

Principally Meta, Uber and IBM, which acquired the Presto vendor Ahana in 2023.

CosmosDB: Is there a trial period for Cosmos DB beyond the free tier?

Azure offers a 30-day free trial account for all Azure services. Additionally, Azure AI customers may be eligible for a 90-day free Cosmos DB subscription through the Azure AI Advantage program.

Source
Presto: Is it still actively released?

Yes, releases continue on a regular cadence under the Presto Foundation.

Share

Related pages

More on CosmosDB

More on Presto

Keep looking

Other head to heads