Softwr

Databases · head to head

Apache Doris vs StarRocks

Apache Doris logo

Apache Doris

Databases

MPP analytical database with a MySQL wire protocol and sub-second aggregation on wide tables

From
Free
Rated
-
StarRocks logo

StarRocks

Databases

Apache 2.0 MPP analytical database built for joins on open table formats

From
Free
Rated
-

The short version

  • Each has a real cost: Apache Doris two competing commercial vendors, VeloDB and SelectDB, were founded by overlapping core contributors, which makes the long-term governance and roadmap of the project harder to predict than a single-sponsor project.; StarRocks self-hosting is a genuine operations job: frontend and backend node roles, tablet distribution, compaction and materialised view refresh all need an owner, and there is no small-team-friendly single-binary mode.
  • They diverge on capability: Apache Doris covers Aggregate and unique key models, StarRocks covers Cost-based optimiser.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Apache Doris and StarRocks actually diverge.

Attributes where Apache Doris and StarRocks differ
AttributeApache DorisStarRocks

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), platforms (Linux, Docker, Kubernetes), 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 Apache Doris

  • Aggregate and unique key models
  • Multi-catalogue federation
  • Routine load from Kafka
  • Compute storage separation
  • Inverted indexes
  • Workload groups

Only in StarRocks

  • Cost-based optimiser
  • Lakehouse query engine
  • Primary key tables
  • Shared-data mode

Both cover

  • MySQL wire protocol
  • Materialised views

What people use each for

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

Apache Doris

  • A team whose MySQL read replica can no longer serve reporting queries and wants an OLAP engine its existing drivers already speaknot StarRocks
  • A real-time dashboard backend needing sub-second aggregation over billions of rows with hundreds of concurrent usersnot StarRocks
  • An ad or ecommerce platform that needs updates and deletes on analytical tables, which append-only OLAP engines handle badlynot StarRocks
  • A data team that wants one SQL endpoint over both internal tables and existing Hive or Iceberg tables in the lakenot StarRocks

StarRocks

  • Customer-facing analytics where queries join a fact table to several dimensions and must return in well under a secondnot Apache Doris
  • Querying an Iceberg lakehouse directly without copying data into a proprietary warehouse formatnot Apache Doris
  • Replacing a ClickHouse deployment that has become unmanageable because every new question needs another denormalised tablenot Apache Doris
  • Real-time analytics fed by change data capture where rows must be updated in place rather than appendednot Apache Doris

Where each one falls short

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

Apache Doris

  • Two competing commercial vendors, VeloDB and SelectDB, were founded by overlapping core contributors, which makes the long-term governance and roadmap of the project harder to predict than a single-sponsor project.
  • A large share of design discussion, issue reports and documentation detail originates in Chinese, so teams that do not read it get a thinner picture of known problems and workarounds.
  • Operating a cluster means managing frontend and backend node roles, tablet balancing and compaction tuning, and compaction backlogs under heavy upsert load are a recurring production complaint.
  • The MySQL protocol compatibility is at the wire level, not full MySQL semantics, so queries and functions still need porting and the familiarity can mislead.
  • Managed cloud availability outside China and major clouds is limited compared with ClickHouse or Snowflake, so many Western adopters end up self-hosting whether they wanted to or not.

StarRocks

  • Self-hosting is a genuine operations job: frontend and backend node roles, tablet distribution, compaction and materialised view refresh all need an owner, and there is no small-team-friendly single-binary mode.
  • CelerData is by far the dominant contributor despite Linux Foundation stewardship, so the practical roadmap risk is the same as any single-vendor open source project.
  • It inherits a MySQL-flavoured SQL dialect from its Doris ancestry, so queries written for PostgreSQL, Snowflake or Trino need rewriting rather than porting.
  • Ecosystem support is thinner than ClickHouse or Trino: fewer client libraries, fewer managed hosting options and a much smaller pool of engineers who have run it in production.
  • Memory pressure under concurrent large joins is a common production failure, and the tuning knobs for query memory limits are unforgiving compared with a cloud warehouse that just scales.

Pricing, plan by plan

Apache Doris

Free
  • Apache DorisFree
    • Apache 2.0 licence with no usage restrictions
    • All engine features included
    • Community support via mailing list and Slack

StarRocks

Free
  • StarRocksFree
    • Apache 2.0 licence
    • Linux Foundation governance
    • No usage or node limits
  • CelerData Cloud$undefined/year
    • Managed StarRocks from the primary contributor
    • BYOC and serverless deployment options
    • Enterprise support and SLAs

Which should you pick?

Choose Apache Doris if

  • You need aggregate and unique key models.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes.
  • You also want multi-catalogue federation.

Choose StarRocks if

  • You need cost-based optimiser.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes.
  • You also want lakehouse query engine.

Questions people ask

Is Apache Doris or StarRocks better?
Neither clearly leads. Apache Doris starts at Free and StarRocks at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Apache Doris or StarRocks?
Apache Doris starts at Free and StarRocks at Free.
Does Apache Doris or StarRocks run on more platforms?
Both run on Linux, Docker, Kubernetes, so platform support will not decide this one for you.
Can I use Apache Doris for free?
Both have a free tier, so you can try either at no cost before committing.
What is Apache Doris best used for?
Apache Doris is most often used for a team whose mysql read replica can no longer serve reporting queries and wants an olap engine its existing drivers already speak, a real-time dashboard backend needing sub-second aggregation over billions of rows with hundreds of concurrent users, an ad or ecommerce platform that needs updates and deletes on analytical tables, which append-only olap engines handle badly, a data team that wants one sql endpoint over both internal tables and existing hive or iceberg tables in the lake. Of those, a team whose mysql read replica can no longer serve reporting queries and wants an olap engine its existing drivers already speak and a real-time dashboard backend needing sub-second aggregation over billions of rows with hundreds of concurrent users are not what StarRocks is typically brought in for.
What can Apache Doris do that StarRocks cannot?
Apache Doris covers Aggregate and unique key models, Multi-catalogue federation, Routine load from Kafka, Compute storage separation. StarRocks covers Cost-based optimiser, Lakehouse query engine, Primary key tables, Shared-data mode. Both handle MySQL wire protocol, Materialised views.

Answered from the vendors’ own pages

Apache Doris: Is Apache Doris really free?

Yes, it is Apache 2.0 with no usage restrictions. The commercial products are managed services from VeloDB and SelectDB.

StarRocks: Is StarRocks open source?

Yes, Apache 2.0, governed under the Linux Foundation since 2023.

Apache Doris: Can I use my MySQL tools with it?

Yes, it implements the MySQL wire protocol, so clients and BI connectors attach without a new driver, though SQL semantics differ.

StarRocks: How does it differ from ClickHouse?

StarRocks is built for joins across a star schema with a cost-based optimiser; ClickHouse is fastest on denormalised single tables.

Apache Doris: How does it compare with ClickHouse?

Doris handles updates and high concurrency more comfortably; ClickHouse is generally faster on raw single-query scan throughput and has far wider Western support.

StarRocks: Who maintains it?

CelerData, formerly StarRocks Inc, is the dominant contributor and sells the managed service.

Apache Doris: Who maintains it?

The Apache Software Foundation project, with most committers employed by VeloDB or SelectDB.

StarRocks: Can it query Iceberg tables directly?

Yes, along with Hudi, Delta Lake, Hive and Paimon, with a local cache for repeat queries.

Share

Related pages

Other head to heads