E-Commerce · head to head
Depop vs Turso

Depop
E-Commerce
Fashion resale marketplace popular with younger sellers, owned by Etsy, with a per-item plus percentage fee
- 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
- Depop is free; Turso starts at $4.99/mo.
- Only Depop lists curated seller shops; 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 Depop 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 Depop
- Curated seller shops
- Social discovery feed
- Per-order seller fee
- Depop Payments
- Offers and bundles
- Boost and promoted listings
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.
Depop
- A younger seller building a curated vintage or streetwear shop with a distinct aesthetic identitynot Turso
- A buyer who discovers items through a social-style feed rather than direct searchnot Turso
- A seller moving higher-priced individual pieces where the current fee structure is more favourable than the old flat ratenot Turso
- Someone who wants social features like likes and follows as part of the buying and selling experiencenot Turso
Turso
- Multi-tenant SaaS where each customer gets their own database for real isolation, per-tenant restore and clean deletionnot Depop
- Agent or session infrastructure that creates a throwaway database per task and destroys it afterwardsnot Depop
- Local-first and offline-capable applications where an embedded replica serves reads at file speed and syncs when connectivity returnsnot Depop
- Embedding a SQLite-compatible engine in a product where the public domain original's closed contribution model is a problemnot Depop
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Depop
- The 2024 shift away from a flat 10 percent fee increased the effective cost per sale for sellers moving high volumes of low-priced items, a group that was previously well served by the app
- Payment processing is a separate fee on top of the per-order seller fee, so the total deduction from a sale is not fully captured by the headline percentage alone
- Discovery leans heavily on an algorithmic social feed, so newer sellers without an existing following can find it harder to get visibility without paying for Boost promotion
- As an Etsy subsidiary since 2021, Depop's roadmap and fee decisions are set within a larger public company strategy rather than independently, and past fee changes reflect that broader commercial pressure
- Buyer protection and dispute resolution for item condition or authenticity issues rely on Depop's own policies, which are less standardised than the seller-rating-driven trust systems on some competitors
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
Depop
Free- SellingFree
- Percentage-based fee on sale price plus a small fixed per-order fee
- Separate payment processing fee applies on top
- Sellers should check current published rates, as the fee structure changed from a flat 10 percent in 2024
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 Depop if
- You need curated seller shops.
- You want to start without paying.
- You work on iOS, Android, Web.
- You also want social discovery feed.
Choose Turso if
- You need per-tenant databases.
- You want to start without paying.
- You also want mit licence.
Questions people ask
- Is Depop or Turso better?
- Neither clearly leads. Depop 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, Depop or Turso?
- Depop starts at Free and Turso at Free.
- Does Depop or Turso run on more platforms?
- Depop runs on iOS, Android, Web. Turso runs on Web.
- Can I use Depop for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Depop best used for?
- Depop is most often used for a younger seller building a curated vintage or streetwear shop with a distinct aesthetic identity, a buyer who discovers items through a social-style feed rather than direct search, a seller moving higher-priced individual pieces where the current fee structure is more favourable than the old flat rate, someone who wants social features like likes and follows as part of the buying and selling experience. Of those, a younger seller building a curated vintage or streetwear shop with a distinct aesthetic identity and a buyer who discovers items through a social-style feed rather than direct search are not what Turso is typically brought in for.
- What can Depop do that Turso cannot?
- Depop covers Curated seller shops, Social discovery feed, Per-order seller fee, Depop Payments. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.
Answered from the vendors’ own pages
Depop: Is Depop seller fee still a flat 10 percent?
No, Depop moved to a percentage plus small fixed per-order fee structure in 2024, replacing the earlier flat 10 percent rate.
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.
Depop: Who owns Depop?
Etsy, which acquired Depop in 2021 for 1.625 billion dollars.
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.
Depop: Does Depop charge for payment processing separately?
Yes, Depop Payments carries its own fee in addition to the per-order seller fee.
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
- Depop vs Poshmark
- Depop vs Vinted
- Depop vs Mercari
- Depop vs Instacart
- Depop vs Amazon Shopping
- Depop vs Shein
- Depop vs Temu
- Depop vs Wish
- Depop vs Gumroad
- Depop vs eBay
- Depop vs Shopkeep
- Depop vs NCR Voyix
- Depop vs Vendure
- Depop vs Volusion
- Depop vs Wix eCommerce
- Depop vs WooCommerce
- Depop vs Zendrop
- Depop vs Magento
- Depop vs SurrealDB
- Depop vs MotherDuck
- Depop vs EMQX
- Depop vs DuckDB
- Depop vs Trino
- Depop vs Nile
- Depop vs SQLite
- Depop vs Teradata
- Depop vs Apache Kafka
- Depop vs BigQuery
- Depop vs Typesense
- Depop vs Apache Spark
- Depop vs IBM Db2
- Depop vs Instaclustr
- Depop vs Knack
- Depop vs LanceDB
- Depop vs Marqo
- Depop vs MongoDB
- Turso vs Poshmark
- Turso vs Vinted
- Turso vs Mercari
- Turso vs Instacart
- Turso vs Amazon Shopping
- Turso vs Shein
- Turso vs Temu
- Turso vs Wish
- Turso vs Gumroad
- Turso vs eBay
- Turso vs Shopkeep
- Turso vs NCR Voyix
- Turso vs Vendure
- Turso vs Volusion
- Turso vs Wix eCommerce
- Turso vs WooCommerce
- Turso vs Zendrop
- Turso vs Magento
- 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
