Databases · head to head
LanceDB vs Mercari

LanceDB
Databases
Embedded retrieval library over the Apache 2.0 Lance columnar format, with proprietary Cloud and Enterprise tiers for serving at scale.
- From
- On request
- Free plan
- No

Mercari
E-Commerce
Japan-founded peer-to-peer resale marketplace with a flat seller commission
- From
- Free
- Free plan
- Yes
The short version
- LanceDB is a library, not a server.
- Mercari is free; LanceDB prices on request.
- Only LanceDB lists embedded operation; only Mercari lists flat seller commission.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which LanceDB and Mercari actually diverge.
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 LanceDB
- Embedded operation
- Lance columnar format
- Object storage native
- Multimodal storage
- Vector indexes
- Full-text and hybrid search
- Scalar filtering
- Dataset versioning
Only in Mercari
- Flat seller commission
- Prepaid shipping labels
- Local pickup and offers
- Smart pricing and price drops
- Mercari authenticity guarantee
- Instant or standard payout
What people use each for
The jobs each tool is most often brought in to do.
LanceDB
- Retrieval over a dataset that includes images, audio or video, where keeping the embeddings and the source media in one format avoids a second storage systemnot Mercari
- A training and retrieval pipeline that must read the same rows for both purposes without maintaining two copies and a sync jobnot Mercari
- Prototyping search locally with the same code path that later runs against S3, with no local server to installnot Mercari
- Keeping a large, mostly cold vector corpus on object storage rather than paying to hold it in memory in a conventional vector databasenot Mercari
Mercari
- Someone clearing out a wide mix of household items, not just clothing, in one listing appnot LanceDB
- A casual seller who wants a flat, predictable commission rather than a tiered fee structurenot LanceDB
- A buyer looking for secondhand electronics or general goods alongside apparelnot LanceDB
- A seller using local pickup to avoid shipping costs on bulky itemsnot LanceDB
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
LanceDB
- The open source build is a library with no network endpoint, authentication or tenancy model, so exposing it to more than one application means writing your own service in front of it and handing every consumer credentials to the bucket
- Queries that miss the cache pay object storage round trips, so interactive latency depends on local SSD caching or the Enterprise serving tier rather than on the library itself
- Concurrent writers to the same dataset coordinate through commits on the object store, so multi-writer setups can conflict and the safe pattern is a single writer per table, which is an architectural constraint on your ingest design
- Newly written rows are not in the index until the index is rebuilt or updated, and until then they are searched by brute force, so recall and latency drift between reindexing jobs that you have to schedule and pay for
- The capabilities that make it operable at scale, distributed index building, managed caching and hosted serving, live in the proprietary Cloud and Enterprise tiers, so the open licence protects the data but not the production deployment
Mercari
- The flat 10 percent commission plus payment processing fees applies even to very low-value items, so selling something for a few dollars can leave the seller with proportionally little after fees and packaging
- Shipping is the seller's responsibility to arrange and package correctly, and disputes over item condition or damage in transit are common friction points in buyer-seller resolution
- Instant payout carries its own fee on top of the selling and processing fees already deducted, so getting money out quickly costs more than waiting for standard transfer
- Buyer protection and authenticity verification are limited outside the specific luxury authentication programme, so counterfeit risk on unverified categories rests largely on buyer judgement of listing photos and seller ratings
- Market depth and typical sale prices vary significantly between the Japan and US versions of the app, and the two operate as largely separate marketplaces despite the shared brand
Pricing, plan by plan
LanceDB
On requestNo published plan breakdown. See the LanceDB review.
Mercari
Free- SellingFree
- 10 percent selling fee on final sale price
- Separate payment processing fee, roughly 2.9 percent plus a fixed amount
- Instant payout carries an additional fee versus standard bank transfer
Which should you pick?
Choose Mercari if
- You need flat seller commission.
- You want to start without paying.
- You work on iOS, Android, Web.
- You also want prepaid shipping labels.
Questions people ask
- Is LanceDB or Mercari better?
- Neither clearly leads. LanceDB starts at On request and Mercari at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, LanceDB or Mercari?
- Mercari has a free tier; the other does not. Paid plans start at On request for LanceDB and Free for Mercari.
- Does LanceDB or Mercari run on more platforms?
- LanceDB runs on Web. Mercari runs on iOS, Android, Web.
- Can I use Mercari for free?
- Yes. Mercari has a free tier, so you can try it without paying. LanceDB starts at On request.
- What is LanceDB best used for?
- LanceDB is most often used for retrieval over a dataset that includes images, audio or video, where keeping the embeddings and the source media in one format avoids a second storage system, a training and retrieval pipeline that must read the same rows for both purposes without maintaining two copies and a sync job, prototyping search locally with the same code path that later runs against s3, with no local server to install, keeping a large, mostly cold vector corpus on object storage rather than paying to hold it in memory in a conventional vector database. Of those, retrieval over a dataset that includes images, audio or video, where keeping the embeddings and the source media in one format avoids a second storage system and a training and retrieval pipeline that must read the same rows for both purposes without maintaining two copies and a sync job are not what Mercari is typically brought in for.
- What can LanceDB do that Mercari cannot?
- LanceDB covers Embedded operation, Lance columnar format, Object storage native, Multimodal storage. Mercari covers Flat seller commission, Prepaid shipping labels, Local pickup and offers, Smart pricing and price drops.
Answered from the vendors’ own pages
LanceDB: Is LanceDB open source?
The LanceDB library and the underlying Lance format are Apache 2.0. LanceDB Cloud and LanceDB Enterprise are proprietary managed products built on top of them.
Mercari: How much does Mercari charge sellers?
A flat 10 percent selling fee on the final sale price in the US, plus a separate payment processing fee, both deducted from the seller payout.
LanceDB: Do I need the managed service?
Not for development or for embedded use in a single application. You typically need it when many clients must query concurrently with predictable latency, or when index builds outgrow one machine.
Mercari: Does the buyer pay any extra platform fee?
No separate platform fee is added at buyer checkout the way Vinted adds a buyer protection fee; the buyer pays the listed price plus shipping if not included.
LanceDB: Can other tools read my data?
Yes. Lance datasets are readable from DuckDB, Polars, Pandas, PyArrow and PyTorch, which is the main practical difference from a vector database that owns its own storage.
Mercari: Is Mercari the same marketplace in Japan and the US?
No, they operate as separate marketplaces under the same brand, with different inventory, pricing and fee history.
LanceDB: How does it compare to pgvector?
pgvector keeps vectors next to relational data in a database you already run. LanceDB keeps them in object storage in a format built for random access and multimodal payloads, and scales storage independently of any server.
LanceDB: What happens to updates and deletes?
Writes append new fragments and mark old rows deleted, with compaction reclaiming space later, so a workload with heavy in-place updates accumulates overhead until compaction runs.
Related pages
Other head to heads
- LanceDB vs DuckDB
- LanceDB vs BigQuery
- LanceDB vs DynamoDB
- LanceDB vs Trino
- LanceDB vs Chroma
- LanceDB vs Convex
- LanceDB vs Dremio
- LanceDB vs Teradata
- LanceDB vs turbopuffer
- LanceDB vs Zilliz
- LanceDB vs Apache Druid
- LanceDB vs Elasticsearch
- LanceDB vs PlanetScale
- LanceDB vs Redis
- LanceDB vs Supabase
- LanceDB vs Meilisearch
- LanceDB vs Apache Pulsar
- LanceDB vs Apache Airflow
- LanceDB vs Vinted
- LanceDB vs Depop
- LanceDB vs Poshmark
- LanceDB vs Temu
- LanceDB vs Instacart
- LanceDB vs Amazon Shopping
- LanceDB vs Shein
- LanceDB vs Wish
- LanceDB vs eBay
- LanceDB vs Algopix
- LanceDB vs Etsy
- LanceDB vs Gumroad
- LanceDB vs commercetools
- LanceDB vs Contentful
- LanceDB vs Erply
- LanceDB vs FastSpring
- LanceDB vs Medusa
- LanceDB vs Printful
- Mercari vs DuckDB
- Mercari vs BigQuery
- Mercari vs DynamoDB
- Mercari vs Trino
- Mercari vs Chroma
- Mercari vs Convex
- Mercari vs Dremio
- Mercari vs Teradata
- Mercari vs turbopuffer
- Mercari vs Zilliz
- Mercari vs Apache Druid
- Mercari vs Elasticsearch
- Mercari vs PlanetScale
- Mercari vs Redis
- Mercari vs Supabase
- Mercari vs Meilisearch
- Mercari vs Apache Pulsar
- Mercari vs Apache Airflow
- Mercari vs Vinted
- Mercari vs Depop
- Mercari vs Poshmark
- Mercari vs Temu
- Mercari vs Instacart
- Mercari vs Amazon Shopping
- Mercari vs Shein
- Mercari vs Wish
- Mercari vs eBay
- Mercari vs Algopix
- Mercari vs Etsy
- Mercari vs Gumroad
- Mercari vs commercetools
- Mercari vs Contentful
- Mercari vs Erply
- Mercari vs FastSpring
- Mercari vs Medusa
- Mercari vs Printful
