Databases · head to head
DuckDB vs Mercari

DuckDB
Databases
MIT-licensed analytical SQL database that runs inside your process, with no server, no dependencies and one writer at a time.
- From
- Free
- Free plan
- Yes

Mercari
E-Commerce
Japan-founded peer-to-peer resale marketplace with a flat seller commission
- From
- Free
- Free plan
- Yes
The short version
- Both are free.
- Only DuckDB lists in-process execution; 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 DuckDB and Mercari actually diverge.
Identical on both: starting price (Free), free tier (Yes).
Not yet recorded: founded for Mercari.
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 DuckDB
- In-process execution
- Vectorised columnar engine
- Direct file querying
- Zero dependencies
- Larger-than-memory queries
- MIT licence
- Postgres-flavoured SQL
- Extension ecosystem
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.
DuckDB
- Transformation steps in a data pipeline that would otherwise need Spark, replaced by SQL over Parquet in a single processnot Mercari
- Analytical queries embedded in an application or a dashboard where shipping a database server alongside it is not acceptablenot Mercari
- Local exploration of files that are too large for a pandas dataframe but far too small to justify a warehousenot Mercari
- Continuous integration and testing of analytical SQL, where a real engine can run in the test process without provisioning anythingnot Mercari
Mercari
- Someone clearing out a wide mix of household items, not just clothing, in one listing appnot DuckDB
- A casual seller who wants a flat, predictable commission rather than a tiered fee structurenot DuckDB
- A buyer looking for secondhand electronics or general goods alongside apparelnot DuckDB
- A seller using local pickup to avoid shipping costs on bulky itemsnot DuckDB
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
DuckDB
- A database file accepts one read-write process at a time; other processes must open it read-only and will not see subsequent writes, so DuckDB cannot be the shared database behind several services
- There is no network protocol, authentication or user management, so exposing it to remote clients means writing and securing your own service around it
- It is built for scans and aggregations, not for many small transactions, so a workload of high-frequency single-row inserts and updates performs badly compared with SQLite or Postgres
- Storage files are backwards compatible but not forwards compatible, so a file written by a newer version cannot be read by an older one and every consumer of a shared file must be upgraded together
- Query memory settings matter: some operations still need to hold significant state, so an under-configured memory limit turns a large join or a high-cardinality aggregation into a spill-heavy query or an out-of-memory failure rather than a slow success
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
DuckDB
FreeNo published plan breakdown. See the DuckDB 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 DuckDB if
- You need in-process execution.
- You want to start without paying.
- You work on Linux, macOS, Windows, Web.
- You also want vectorised columnar engine.
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 DuckDB or Mercari better?
- Neither clearly leads. DuckDB starts at Free and Mercari at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, DuckDB or Mercari?
- DuckDB starts at Free and Mercari at Free.
- Does DuckDB or Mercari run on more platforms?
- DuckDB runs on Linux, macOS, Windows, Web. Mercari runs on iOS, Android, Web.
- Can I use DuckDB for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is DuckDB best used for?
- DuckDB is most often used for transformation steps in a data pipeline that would otherwise need spark, replaced by sql over parquet in a single process, analytical queries embedded in an application or a dashboard where shipping a database server alongside it is not acceptable, local exploration of files that are too large for a pandas dataframe but far too small to justify a warehouse, continuous integration and testing of analytical sql, where a real engine can run in the test process without provisioning anything. Of those, transformation steps in a data pipeline that would otherwise need spark, replaced by sql over parquet in a single process and analytical queries embedded in an application or a dashboard where shipping a database server alongside it is not acceptable are not what Mercari is typically brought in for.
- What can DuckDB do that Mercari cannot?
- DuckDB covers In-process execution, Vectorised columnar engine, Direct file querying, Zero dependencies. Mercari covers Flat seller commission, Prepaid shipping labels, Local pickup and offers, Smart pricing and price drops.
Answered from the vendors’ own pages
DuckDB: Can multiple applications share one DuckDB database?
Not for writing. One process holds the database read-write; others may attach read-only and will not see later writes. Shared multi-writer access needs a different database or a table format with a catalogue.
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.
DuckDB: Is it a replacement for a data warehouse?
For single-node analytical workloads up to a few hundred gigabytes it very often is. It is not a replacement when many concurrent users need a shared, governed, always-on service.
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.
DuckDB: Do I have to load data into it?
No. It queries Parquet, CSV, JSON and Arrow in place, including on object storage. Its own storage format is optional and mainly useful when you want indexes, constraints and faster repeated access.
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.
DuckDB: What is MotherDuck's relationship to it?
MotherDuck is a separate company offering a managed and hybrid service built on the DuckDB engine. DuckDB itself remains MIT-licensed and independent of it, with the IP held by the DuckDB Foundation.
DuckDB: Is it suitable for OLTP?
No. It is designed for analytical scans. For transactional workloads with frequent small writes, SQLite or Postgres is the right tool.
Related pages
Other head to heads
- DuckDB vs SingleStore
- DuckDB vs SQLite
- DuckDB vs ClickHouse
- DuckDB vs Apache Druid
- DuckDB vs Firebolt
- DuckDB vs OpenSearch
- DuckDB vs StarRocks
- DuckDB vs QuestDB
- DuckDB vs BigQuery
- DuckDB vs Elasticsearch
- DuckDB vs Materialize
- DuckDB vs Oracle Database
- DuckDB vs TimescaleDB
- DuckDB vs Trino
- DuckDB vs Turso
- DuckDB vs Amazon RDS
- DuckDB vs Apache Pinot
- DuckDB vs Apache Flink
- DuckDB vs Vinted
- DuckDB vs Depop
- DuckDB vs Poshmark
- DuckDB vs Temu
- DuckDB vs Instacart
- DuckDB vs Amazon Shopping
- DuckDB vs Shein
- DuckDB vs Wish
- DuckDB vs eBay
- DuckDB vs Algopix
- DuckDB vs Etsy
- DuckDB vs Gumroad
- DuckDB vs commercetools
- DuckDB vs Contentful
- DuckDB vs Erply
- DuckDB vs FastSpring
- DuckDB vs Medusa
- DuckDB vs Printful
- Mercari vs SingleStore
- Mercari vs SQLite
- Mercari vs ClickHouse
- Mercari vs Apache Druid
- Mercari vs Firebolt
- Mercari vs OpenSearch
- Mercari vs StarRocks
- Mercari vs QuestDB
- Mercari vs BigQuery
- Mercari vs Elasticsearch
- Mercari vs Materialize
- Mercari vs Oracle Database
- Mercari vs TimescaleDB
- Mercari vs Trino
- Mercari vs Turso
- Mercari vs Amazon RDS
- Mercari vs Apache Pinot
- Mercari vs Apache Flink
- 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
