Softwr

Databases · head to head

Apache Doris vs Chroma

Apache Doris logo

Apache Doris

Databases

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

From
Free
Rated
-
Full reviewWebsite
Chroma logo

Chroma

Databases

Apache 2.0 vector and full-text search engine that runs as an embedded library, a single server or a distributed cloud service.

From
Free
Rated
-
Full reviewWebsite

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.; Chroma on a single node, available memory sets a hard upper bound on collection size, roughly 245,000 records per gigabyte of RAM at 1024 dimensions, so capacity planning is a memory purchase and the ceiling arrives without warning.
  • They diverge on capability: Apache Doris covers MySQL wire protocol, Chroma covers Embedded mode.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

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

Attributes where Apache Doris and Chroma differ
AttributeApache DorisChroma
Pricing modelOpen source, no licence feeusage-based
PlatformsLinux, Docker, KubernetesWeb

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 Apache Doris

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

Only in Chroma

  • Embedded mode
  • Single-node server
  • Distributed architecture
  • Vector search
  • Full-text search
  • Metadata filtering
  • Consistent API across modes
  • Multi-language clients

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 Chroma
  • A real-time dashboard backend needing sub-second aggregation over billions of rows with hundreds of concurrent usersnot Chroma
  • An ad or ecommerce platform that needs updates and deletes on analytical tables, which append-only OLAP engines handle badlynot Chroma
  • A data team that wants one SQL endpoint over both internal tables and existing Hive or Iceberg tables in the lakenot Chroma

Chroma

  • Prototyping retrieval-augmented generation where the priority is having a working index in minutes rather than choosing a permanent storenot Apache Doris
  • Agent memory in a single application process, where an embedded store avoids adding a network dependencynot Apache Doris
  • A departmental search application under roughly ten million records where one server is sufficient and simplicity is worth more than headroomnot Apache Doris
  • Local and CI testing of retrieval code with the same client library used in productionnot 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.

Chroma

  • On a single node, available memory sets a hard upper bound on collection size, roughly 245,000 records per gigabyte of RAM at 1024 dimensions, so capacity planning is a memory purchase and the ceiling arrives without warning.
  • Single-node queries parallelise only up to the number of vCPUs, after which requests queue and latency rises linearly with concurrency, so throughput problems appear as a slow application rather than as errors.
  • The distributed deployment behind Chroma Cloud is a different architecture from the embedded library, so latency, consistency and failure behaviour observed in a local prototype do not predict production behaviour.
  • The open source server has no built-in authentication or multi-tenancy worth relying on, so a self-hosted deployment needs its own auth proxy and network controls before anything untrusted can reach it.
  • The project has moved quickly through major internal rewrites and version changes, so upgrades have historically involved data migrations and client changes, and pinning versions is necessary rather than cautious.

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

Chroma

Free
  • StarterFree
    • 10 databases
    • 10 team members
    • Community Slack access
  • Team$250/month
    • 100 databases
    • 30 team members
    • $100 in included credits
  • Enterprise$null/month
    • Unlimited databases
    • Unlimited team members
    • Dedicated support

Which should you pick?

Choose Apache Doris if

  • You need mysql wire protocol.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes.
  • You also want aggregate and unique key models.
Apache Doris review

Choose Chroma if

  • You need embedded mode.
  • You want to start without paying.
  • You also want single-node server.
Chroma review

Questions people ask

Is Apache Doris or Chroma better?
Neither clearly leads. Apache Doris starts at Free and Chroma at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Apache Doris or Chroma?
Apache Doris starts at Free and Chroma at Free.
Does Apache Doris or Chroma run on more platforms?
Apache Doris runs on Linux, Docker, Kubernetes. Chroma runs on Web.
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 Chroma is typically brought in for.
What can Apache Doris do that Chroma cannot?
Apache Doris covers MySQL wire protocol, Aggregate and unique key models, Materialised views, Multi-catalogue federation. Chroma covers Embedded mode, Single-node server, Distributed architecture, Vector search.

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.

Chroma: Do I need to run a server?

No. Chroma runs embedded in your process with persistence to a local directory, which is how most projects start. The server and distributed modes exist for when multiple clients or larger collections require them.

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.

Chroma: How large can a single node get?

The project puts single-node deployments at fewer than about ten million records across a handful of collections, with collection size bounded by system memory at roughly 245,000 records per gigabyte at 1024 dimensions.

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.

Chroma: Is Chroma Cloud the same software?

It is the same API and project, but the distributed deployment is a different architecture, using independent services, object storage and SSD caches rather than a single process. Behaviour under load differs accordingly.

Apache Doris: Who maintains it?

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

Chroma: How does it compare with pgvector?

pgvector keeps vectors in a Postgres database you already operate, with SQL, joins and transactions. Chroma is a dedicated retrieval engine with a lower setup cost and a retrieval-shaped API. If you already run Postgres, pgvector removes a system; if you do not, Chroma removes a decision.

Chroma: What licence is it under?

Apache 2.0, which permits self-hosting and embedding in commercial products without a competing-use restriction.

Share

Related pages

More on Apache Doris

More on Chroma

Keep looking

Other head to heads