Softwr

E-Commerce · head to head

Depop vs LanceDB

Depop logo

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
LanceDB logo

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

The short version

  • LanceDB is a library, not a server.
  • Depop is free; LanceDB prices on request.
  • Only Depop lists curated seller shops; only LanceDB lists embedded operation.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Depop and LanceDB actually diverge.

Attributes where Depop and LanceDB differ
AttributeDepopLanceDB
Starting priceFreeOn request
Pricing modelFree to list; percentage plus per-order seller fee, separate payment processing feeQuote
Free tierYesNo
PlatformsiOS, Android, WebWeb
CategoryE-CommerceDatabases

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 LanceDB

  • Embedded operation
  • Lance columnar format
  • Object storage native
  • Multimodal storage
  • Vector indexes
  • Full-text and hybrid search
  • Scalar filtering
  • Dataset versioning

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 LanceDB
  • A buyer who discovers items through a social-style feed rather than direct searchnot LanceDB
  • A seller moving higher-priced individual pieces where the current fee structure is more favourable than the old flat ratenot LanceDB
  • Someone who wants social features like likes and follows as part of the buying and selling experiencenot LanceDB

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 Depop
  • A training and retrieval pipeline that must read the same rows for both purposes without maintaining two copies and a sync jobnot Depop
  • Prototyping search locally with the same code path that later runs against S3, with no local server to installnot Depop
  • Keeping a large, mostly cold vector corpus on object storage rather than paying to hold it in memory in a conventional vector databasenot 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

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

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

LanceDB

On request

No published plan breakdown. See the LanceDB review.

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 LanceDB if

  • You need embedded operation.
  • You also want lance columnar format.

Questions people ask

Is Depop or LanceDB better?
Neither clearly leads. Depop starts at Free and LanceDB at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Depop or LanceDB?
Depop has a free tier; the other does not. Paid plans start at Free for Depop and On request for LanceDB.
Does Depop or LanceDB run on more platforms?
Depop runs on iOS, Android, Web. LanceDB runs on Web.
Can I use Depop for free?
Yes. Depop has a free tier, so you can try it without paying. LanceDB starts at On request.
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 LanceDB is typically brought in for.
What can Depop do that LanceDB cannot?
Depop covers Curated seller shops, Social discovery feed, Per-order seller fee, Depop Payments. LanceDB covers Embedded operation, Lance columnar format, Object storage native, Multimodal storage.

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.

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.

Depop: Who owns Depop?

Etsy, which acquired Depop in 2021 for 1.625 billion dollars.

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.

Depop: Does Depop charge for payment processing separately?

Yes, Depop Payments carries its own fee in addition to the per-order seller fee.

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.

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.

Share

Related pages

Other head to heads