E-Commerce · head to head
Mercari vs Turso

Mercari
E-Commerce
Japan-founded peer-to-peer resale marketplace with a flat seller commission
- From
- Free
- Free plan
- Yes

Turso
Databases
SQLite-lineage database platform for running very large numbers of small per-tenant databases, with an MIT-licensed engine.
- From
- Free
- Free plan
- Yes
The short version
- Mercari is free; Turso starts at $4.99/mo.
- Only Mercari lists flat seller commission; only Turso lists per-tenant databases.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which Mercari and Turso actually diverge.
Identical on both: starting price (Free), free tier (Yes).
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 Mercari
- Flat seller commission
- Prepaid shipping labels
- Local pickup and offers
- Smart pricing and price drops
- Mercari authenticity guarantee
- Instant or standard payout
Only in Turso
- Per-tenant databases
- MIT licence
- Embedded replicas
- SQLite compatibility
- HTTP access
- Branching
- Point-in-time restore
- In-process engine
What people use each for
The jobs each tool is most often brought in to do.
Mercari
- Someone clearing out a wide mix of household items, not just clothing, in one listing appnot Turso
- A casual seller who wants a flat, predictable commission rather than a tiered fee structurenot Turso
- A buyer looking for secondhand electronics or general goods alongside apparelnot Turso
- A seller using local pickup to avoid shipping costs on bulky itemsnot Turso
Turso
- Multi-tenant SaaS where each customer gets their own database for real isolation, per-tenant restore and clean deletionnot Mercari
- Agent or session infrastructure that creates a throwaway database per task and destroys it afterwardsnot Mercari
- Local-first and offline-capable applications where an embedded replica serves reads at file speed and syncs when connectivity returnsnot Mercari
- Embedding a SQLite-compatible engine in a product where the public domain original's closed contribution model is a problemnot Mercari
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
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
Turso
- SQLite allows one writer per database, so a single tenant's write throughput cannot be scaled horizontally and a busy tenant serialises against itself with no sharding option
- Per-tenant databases mean per-tenant migrations, so every schema change becomes a fan-out job that must be idempotent and resumable, and multi-database schemas, the feature meant to solve this, is deprecated
- There are no cross-database queries; ATTACH is deprecated on the cloud, so any report or analytic spanning tenants must be assembled in your application or in a separate warehouse you also operate
- Data Edge, the multi-region edge replication that was Turso's original positioning, is deprecated, so a large share of the tutorials and articles describing Turso as an edge database describe behaviour you can no longer rely on
- Three engine lineages share the name, SQLite, the libSQL fork and the Rust rewrite, and the Rust engine is still maturing, so SQLite compatibility needs verifying against your specific pragmas, extensions and query patterns; the cloud already restricts journal_mode and busy_timeout and makes user_version read-only
Pricing, plan by plan
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
Turso
Free- FreeFree
- 100 databases
- 5 GB storage
- 500M monthly rows read
- Developer$4.99/mo
- Unlimited databases
- 9 GB storage
- 2.5B monthly rows read
- Scaler$24.92/mo
- Unlimited databases
- 24 GB storage
- 100B monthly rows read
- Pro$416.58/mo
- Unlimited databases
- 50 GB storage
- 250B monthly rows read
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.
Choose Turso if
- You need per-tenant databases.
- You want to start without paying.
- You also want mit licence.
Questions people ask
- Is Mercari or Turso better?
- Neither clearly leads. Mercari starts at Free and Turso at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Mercari or Turso?
- Mercari starts at Free and Turso at Free.
- Does Mercari or Turso run on more platforms?
- Mercari runs on iOS, Android, Web. Turso runs on Web.
- Can I use Mercari for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Mercari best used for?
- Mercari is most often used for someone clearing out a wide mix of household items, not just clothing, in one listing app, a casual seller who wants a flat, predictable commission rather than a tiered fee structure, a buyer looking for secondhand electronics or general goods alongside apparel, a seller using local pickup to avoid shipping costs on bulky items. Of those, someone clearing out a wide mix of household items, not just clothing, in one listing app and a casual seller who wants a flat, predictable commission rather than a tiered fee structure are not what Turso is typically brought in for.
- What can Mercari do that Turso cannot?
- Mercari covers Flat seller commission, Prepaid shipping labels, Local pickup and offers, Smart pricing and price drops. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.
Answered from the vendors’ own pages
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.
Turso: Is Turso just hosted SQLite?
Not exactly. It hosts databases built on the SQLite lineage: libSQL, an MIT fork of SQLite, and Turso Database, a newer Rust rewrite. The platform adds branching, backups, an HTTP API and programmatic database creation.
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.
Turso: Can I really run a million databases?
That is the design goal and the platform API exists to make provisioning and deletion programmatic. The practical constraints are the ones that come with it: migrations fan out, and nothing can query across databases.
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.
Turso: How do embedded replicas handle read-after-write?
Reads come from the local replica and writes go to the primary, so a read immediately after a write can return stale data unless you wait for a sync. Application code has to account for that rather than assume it.
Turso: What licence is it under?
libSQL and Turso Database are both MIT. Turso Cloud is a commercial managed service built on them, so the engine is genuinely open even though the platform is not.
Turso: Is Turso still an edge database?
No. Data Edge, the multi-region edge replication feature, is deprecated. The current positioning is per-tenant and embedded databases, and older material describing edge replication is out of date.
Related pages
Other head to heads
- 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
- Mercari vs SurrealDB
- Mercari vs MotherDuck
- Mercari vs EMQX
- Mercari vs DuckDB
- Mercari vs Trino
- Mercari vs Nile
- Mercari vs SQLite
- Mercari vs Teradata
- Mercari vs Apache Kafka
- Mercari vs BigQuery
- Mercari vs Typesense
- Mercari vs Apache Spark
- Mercari vs IBM Db2
- Mercari vs Instaclustr
- Mercari vs Knack
- Mercari vs LanceDB
- Mercari vs Marqo
- Mercari vs MongoDB
- Turso vs Vinted
- Turso vs Depop
- Turso vs Poshmark
- Turso vs Temu
- Turso vs Instacart
- Turso vs Amazon Shopping
- Turso vs Shein
- Turso vs Wish
- Turso vs eBay
- Turso vs Algopix
- Turso vs Etsy
- Turso vs Gumroad
- Turso vs commercetools
- Turso vs Contentful
- Turso vs Erply
- Turso vs FastSpring
- Turso vs Medusa
- Turso vs Printful
- Turso vs SurrealDB
- Turso vs MotherDuck
- Turso vs EMQX
- Turso vs DuckDB
- Turso vs Trino
- Turso vs Nile
- Turso vs SQLite
- Turso vs Teradata
- Turso vs Apache Kafka
- Turso vs BigQuery
- Turso vs Typesense
- Turso vs Apache Spark
- Turso vs IBM Db2
- Turso vs Instaclustr
- Turso vs Knack
- Turso vs LanceDB
- Turso vs Marqo
- Turso vs MongoDB
