Databases · head to head
Chroma vs Razorpay

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

Razorpay
E-Commerce
Indian payment gateway for domestic and international card, UPI and wallet acceptance
- From
- On request
- Free plan
- No
The short version
- Chroma starts at $250/mo; Razorpay prices on request.
- Only Chroma lists embedded mode; only Razorpay lists domestic payment methods.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which Chroma and Razorpay actually diverge.
Identical on both: platforms (Web).
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 Chroma
- Embedded mode
- Single-node server
- Distributed architecture
- Vector search
- Full-text search
- Metadata filtering
- Consistent API across modes
- Multi-language clients
Only in Razorpay
- Domestic payment methods
- International cards
- Payment links and pages
- Route
- RazorpayX
- Subscriptions
- Smart Collect
- Dashboard and reporting
What people use each for
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 Razorpay
- Agent memory in a single application process, where an embedded store avoids adding a network dependencynot Razorpay
- A departmental search application under roughly ten million records where one server is sufficient and simplicity is worth more than headroomnot Razorpay
- Local and CI testing of retrieval code with the same client library used in productionnot Razorpay
Razorpay
- An Indian D2C brand needing UPI acceptance alongside cards in a single checkoutnot Chroma
- An Indian SaaS business billing domestic customers on recurring mandatesnot Chroma
- A marketplace that must split each payment between the platform and its sellersnot Chroma
- A business that needs to take payment without building a website, using links and pagesnot Chroma
Where each one falls short
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
Razorpay
- It requires an Indian legal entity and settles only to Indian bank accounts, so it is not an option for a business incorporated elsewhere no matter how many Indian customers it has
- The transaction percentage applies to the full order value including shipping and tax rather than to the product price, so low margin categories with heavy shipping give up more of their margin than the quoted rate suggests
- Payment aggregator authorisation sits with the Reserve Bank of India and has been withheld from aggregators before while applications were reviewed, so a dependency exists that no commercial contract term protects you from
- Default settlement runs on a delayed cycle with faster settlement sold as a paid add-on, so a business that buys stock from its takings either waits for cash or pays extra for it, and that cost belongs in the effective rate
- International card acceptance is priced higher and requires separate approval rather than being a configuration change, so cross-border revenue takes longer to switch on and earns less per order than a domestic sale
Pricing, plan by plan
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
Razorpay
On request- Domestic PaymentsOn request
- 2% platform fee per successful transaction across all payment instruments
- GST: 18% applies on the platform fee
- No setup fees, annual maintenance charges, or refund fees
- Corporate CardsOn request
- 2.15% platform fee per transaction
- International Payments - CardsOn request
- Up to 3% per successful transaction
- International Payments - Bank TransfersOn request
- 1% per transaction with zero forex markup
Which should you pick?
Choose Chroma if
- You need embedded mode.
- You want to start without paying.
- You also want single-node server.
Choose Razorpay if
- You need domestic payment methods.
- You also want international cards.
Questions people ask
- Is Chroma or Razorpay better?
- Neither clearly leads. Chroma starts at Free and Razorpay at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Chroma or Razorpay?
- Chroma has a free tier; the other does not. Paid plans start at Free for Chroma and On request for Razorpay.
- Does Chroma or Razorpay run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- Can I use Chroma for free?
- Yes. Chroma has a free tier, so you can try it without paying. Razorpay starts at On request.
- 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 Razorpay is typically brought in for.
- What can Chroma do that Razorpay cannot?
- Chroma covers Embedded mode, Single-node server, Distributed architecture, Vector search. Razorpay covers Domestic payment methods, International cards, Payment links and pages, Route.
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.
Razorpay: Can I use Razorpay if my company is not in India?
No. It requires an Indian entity and an Indian bank account for settlement. Overseas businesses selling into India need a different arrangement.
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.
Razorpay: What is the real effective rate?
The domestic percentage on the full order value including shipping and tax, plus higher international rates, plus any charge for faster settlement and dispute handling. Compute it from a month of settlement reports, not the pricing page.
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.
Razorpay: How quickly do I get paid?
On a delayed settlement cycle by default, with faster settlement available as a paid feature. Plan working capital around the default, not the add-on.
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.
Razorpay: What is the main structural risk?
Regulatory. Indian payment aggregators operate under RBI authorisation and have previously been barred from onboarding new merchants. Keep a second processor integrated if payments are business-critical.
Chroma: What licence is it under?
Apache 2.0, which permits self-hosting and embedding in commercial products without a competing-use restriction.
Razorpay: Does it support recurring billing?
Yes, built on India's mandate and e-mandate framework, which has its own rules on authentication and notification that differ from card-on-file recurring elsewhere.
Related pages
Other head to heads
- Chroma vs DuckDB
- Chroma vs turbopuffer
- Chroma vs Vespa
- Chroma vs Qdrant
- Chroma vs SQLite
- Chroma vs Timeplus
- Chroma vs EMQX
- Chroma vs LanceDB
- Chroma vs Presto
- Chroma vs Zilliz
- Chroma vs Elasticsearch
- Chroma vs Redis
- Chroma vs Apache Pinot
- Chroma vs DataGrip
- Chroma vs Estuary
- Chroma vs Apache Pulsar
- Chroma vs Cassandra
- Chroma vs CouchDB
- Chroma vs Klarna
- Chroma vs BigCommerce
- Chroma vs Heartland Retail
- Chroma vs Authorize.net
- Chroma vs Braintree
- Chroma vs Mollie
- Chroma vs Stripe
- Chroma vs Square
- Chroma vs Poshmark
- Chroma vs NCR Voyix
- Chroma vs Checkout.com
- Chroma vs eBay
- Chroma vs Bluepark
- Chroma vs Drip
- Chroma vs Ecwid
- Chroma vs Etsy
- Chroma vs Gumroad
- Chroma vs Inventory Lab
- Razorpay vs DuckDB
- Razorpay vs turbopuffer
- Razorpay vs Vespa
- Razorpay vs Qdrant
- Razorpay vs SQLite
- Razorpay vs Timeplus
- Razorpay vs EMQX
- Razorpay vs LanceDB
- Razorpay vs Presto
- Razorpay vs Zilliz
- Razorpay vs Elasticsearch
- Razorpay vs Redis
- Razorpay vs Apache Pinot
- Razorpay vs DataGrip
- Razorpay vs Estuary
- Razorpay vs Apache Pulsar
- Razorpay vs Cassandra
- Razorpay vs CouchDB
- Razorpay vs Klarna
- Razorpay vs BigCommerce
- Razorpay vs Heartland Retail
- Razorpay vs Authorize.net
- Razorpay vs Braintree
- Razorpay vs Mollie
- Razorpay vs Stripe
- Razorpay vs Square
- Razorpay vs Poshmark
- Razorpay vs NCR Voyix
- Razorpay vs Checkout.com
- Razorpay vs eBay
- Razorpay vs Bluepark
- Razorpay vs Drip
- Razorpay vs Ecwid
- Razorpay vs Etsy
- Razorpay vs Gumroad
- Razorpay vs Inventory Lab
