Softwr

Databases · head to head

Chroma vs GitHub

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
Free plan
Yes
GitHub logo

GitHub

Developer Tools

Where the world builds software

From
Free
Free plan
Yes

The short version

  • GitHub is a development platform inspired.
  • Free plans on both; paid from $250/mo and $4/mo.
  • Only Chroma lists embedded mode; only GitHub lists git repositories.
  • Where GitHub falls short: acquired by Microsoft in 2018, reducing pure independence despite operational autonomy.
  • Prices and features on this page were last checked on 17 November 2026.

How do Chroma and GitHub differ?

Chroma and GitHub differ on pricing model (Usage-based against Subscription), platforms and category (Databases against Developer Tools). Only the attributes on which Chroma and GitHub actually diverge.

Attributes where Chroma and GitHub differ
AttributeChromaGitHub
Pricing modelUsage-basedSubscription
PlatformsWebWeb, Windows, macOS, iOS, Android
CategoryDatabasesDeveloper Tools

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

Not yet recorded: founded for Chroma.

Which features does each one have?

They share no listed features; 10 appear only for Chroma and 20 only for GitHub. 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 Chroma

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

Only in GitHub

  • Git repositories
  • Pull requests
  • Code review
  • Issues & projects
  • GitHub Actions CI/CD
  • GitHub Pages
  • Security scanning
  • Dependency management

What is each one used for?

GitHub is most often brought in for version control. The jobs each tool is most often brought in to do.

Chroma

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

GitHub

  • Version controlnot Chroma
  • Code collaborationnot Chroma
  • CI/CD pipelinesnot Chroma
  • Project managementnot Chroma
  • Documentation hostingnot Chroma

Where do Chroma and GitHub fall short?

GitHub's most cited limit: acquired by Microsoft in 2018, reducing pure independence despite operational autonomy. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

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

GitHub

  • Acquired by Microsoft in 2018, reducing pure independence despite operational autonomy
  • Primary focus on source control differs from purpose-built project management tools like Jira
  • Pricing for enterprise features and private repositories adds up compared to some self-hosted alternatives

How much do Chroma and GitHub cost?

Chroma has a free plan, with paid plans from $250/mo; GitHub has a free plan, with paid plans from $4/mo. Plan by plan below, from each vendor's own pricing page.

Chroma

Free
  • StarterFree
    • 10 databases
    • 10 team members
    • Community Slack access
  • Team$250/mo
    • 100 databases
    • 30 team members
    • $100 in included credits
  • EnterpriseOn request
    • Unlimited databases
    • Unlimited team members
    • Dedicated support

GitHub

Free
  • FreeFree
    • Unlimited public/private repos
    • 2,000 CI/CD minutes/month
    • 500MB package storage
  • Team$4/mo
    • Everything in Free
    • 3,000 CI/CD minutes/month
    • 2GB package storage
  • Enterprise$21/mo
    • Everything in Team
    • 50,000 CI/CD minutes/month
    • 50GB package storage

Which should you pick?

Choose Chroma if

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

Choose GitHub if

  • You need git repositories.
  • You want to start without paying.
  • You work on Web, Windows, macOS, iOS, Android.
  • You also want pull requests.

Questions people ask

Is Chroma or GitHub better?
Neither clearly leads. Chroma starts at Free and GitHub at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Chroma or GitHub?
Chroma starts at Free and GitHub at Free.
Does Chroma or GitHub run on more platforms?
Chroma runs on Web. GitHub runs on Web, Windows, macOS, iOS, Android.
Can I use Chroma for free?
Both have a free tier, so you can try either at no cost before committing.
What is Chroma best used for?
Chroma is most often used for prototyping retrieval-augmented generation where the priority is having a working index in minutes rather than choosing a permanent store, agent memory in a single application process, where an embedded store avoids adding a network dependency, a departmental search application under roughly ten million records where one server is sufficient and simplicity is worth more than headroom, local and ci testing of retrieval code with the same client library used in production. Of those, prototyping retrieval-augmented generation where the priority is having a working index in minutes rather than choosing a permanent store and agent memory in a single application process, where an embedded store avoids adding a network dependency are not what GitHub is typically brought in for.
What can Chroma do that GitHub cannot?
Chroma covers Embedded mode, Single-node server, Distributed architecture, Vector search. GitHub covers Git repositories, Pull requests, Code review, Issues & projects.

Answered from the vendors’ own pages

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.

GitHub: What is a Git repository and how does GitHub use it?

A repository is the centralized database that stores the complete collection of files and folders for a codebase, along with the revision history. GitHub uses Git to provide distributed version control access to repositories with version tracking, branching, and collaboration features.

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

GitHub: How does GitHub authentication work?

When you connect to a GitHub repository from Git, you need to authenticate with GitHub using either HTTPS or SSH. GitHub supports multiple authentication methods including passwords, personal access tokens, SSH keys, and GitHub Apps.

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

GitHub: How long has GitHub been operating?

GitHub was founded in 2008 and launched publicly on April 10, 2008, making it the dominant git hosting platform for nearly two decades.

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

GitHub: Who owns GitHub and when did the acquisition occur?

Microsoft acquired GitHub for $7.5 billion USD, with the deal announced June 4, 2018 and completed October 26, 2018. GitHub operates as an independent subsidiary within Microsoft.

Source
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

Other head to heads