E-Commerce · head to head
eBay vs turbopuffer
eBay
E-Commerce
Global marketplace where sellers list into eBay's audience under eBay's fee schedule and rules
- From
- On request
- Free plan
- No

turbopuffer
Databases
Closed-source vector and full-text search service built directly on object storage, with cold queries measured in seconds rather than milliseconds.
- From
- $16/month
- Free plan
- No
The short version
- turbopuffer starts at $16/mo; eBay prices on request.
- Only eBay lists auction and fixed price listings; only turbopuffer lists object storage architecture.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which eBay and turbopuffer actually diverge.
| Attribute | eBay | turbopuffer |
|---|---|---|
| Starting price | On request | $16/month |
| Category | E-Commerce | Databases |
Identical on both: pricing model (Subscription), free tier (No), platforms (Web).
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 eBay
- Auction and fixed price listings
- Managed payments
- eBay Stores
- Promoted Listings
- Bulk listing tools
- International selling programmes
- Money Back Guarantee
- Seller performance standards
Only in turbopuffer
- Object storage architecture
- Namespaces
- Vector search
- Full-text search
- Attribute filtering
- Documented limits
- Configurable consistency
- Durable writes
What people use each for
The jobs each tool is most often brought in to do.
eBay
- Selling used, refurbished or one-off stock that has no natural search demand on its own sitenot turbopuffer
- Parts and spares catalogues where buyers search by fitment rather than by brandnot turbopuffer
- Liquidating returns or excess inventory without building an audience for itnot turbopuffer
- Testing whether demand exists for a product line before investing in a standalone storefrontnot turbopuffer
turbopuffer
- A product with one search index per customer and thousands of customers, most of whose data is idle on any given daynot eBay
- Very large corpora where holding every vector in memory is the dominant cost and occasional cold-query latency is acceptablenot eBay
- Hybrid retrieval combining BM25 and vector search where running and synchronising two separate systems is the problem being solvednot eBay
- Retrieval for agent and assistant products where indexes are created and destroyed frequently and per-index overhead must be near zeronot eBay
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
eBay
- The final value fee applies to the total the buyer pays including postage and tax rather than to the item price, so a low value item with expensive shipping loses a much larger share of its margin than the headline percentage implies
- Fees stack rather than substitute, since a Store subscription, a per order fixed fee, Promoted Listings and cross-border percentages all apply on top of the category rate, and the effective take rate is only visible after a full month of settlement reports
- eBay controls search placement, so as a category gets competitive the practical cost of visibility becomes the Promoted Listings rate, and that is an auction against other sellers that only goes one way
- You do not get the customer relationship, because eBay mediates messaging and does not supply a marketing list, so repeat business depends on eBay showing your listing again rather than on anything you own
- The account is the entire asset and it is governed by policies eBay enforces unilaterally, so a suspension or a category restriction ends the revenue immediately with no portable equivalent of a domain, a theme or a customer database to move elsewhere
turbopuffer
- A cold namespace pays object storage latency on the first query, with a documented p90 around 1,214 ms on a million documents, so any interactive search box needs the data kept warm or the user waits about a second
- Queries are eventually consistent by default, and after roughly 128 MiB of outstanding writes new data is invisible until indexed, which the vendor puts at tens of seconds for small namespaces and tens of minutes for large ones, so a bulk re-index is not immediately queryable
- It is closed source with no community edition, so single-tenant or bring-your-own-cloud deployment is a commercial negotiation rather than a deployment choice, and there is no path to running it yourself if the relationship ends
- Per-namespace ceilings, roughly 10,000 writes per second, 32 MB/s and 500 million documents per shard, mean a single enormous index has to be sharded across namespaces by your application rather than by the service
- It is a search engine, not a database: there are no joins, no cross-document transactions and no SQL, so it sits beside a primary datastore and keeping the two in step is work that belongs to you
Pricing, plan by plan
eBay
On requestNo published plan breakdown. See the eBay review.
turbopuffer
$16/month- Launch$16/mo
- All database features
- Multi-tenancy deployment
- SOC2 & GDPR-ready DPA
- Scale$256/mo
- Everything in Launch
- HIPAA-ready BAA
- Single Sign-On (SSO)
- Enterprise$4,096/mo
- Everything in Scale
- Single-tenancy & BYOC deployment options
- Private networking
Which should you pick?
Choose turbopuffer if
- You need object storage architecture.
- You also want namespaces.
Questions people ask
- Is eBay or turbopuffer better?
- Neither clearly leads. eBay starts at On request and turbopuffer at $16/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, eBay or turbopuffer?
- eBay starts at On request and turbopuffer at $16/month.
- Does eBay or turbopuffer run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- What is eBay best used for?
- eBay is most often used for selling used, refurbished or one-off stock that has no natural search demand on its own site, parts and spares catalogues where buyers search by fitment rather than by brand, liquidating returns or excess inventory without building an audience for it, testing whether demand exists for a product line before investing in a standalone storefront. Of those, selling used, refurbished or one-off stock that has no natural search demand on its own site and parts and spares catalogues where buyers search by fitment rather than by brand are not what turbopuffer is typically brought in for.
- What can eBay do that turbopuffer cannot?
- eBay covers Auction and fixed price listings, Managed payments, eBay Stores, Promoted Listings. turbopuffer covers Object storage architecture, Namespaces, Vector search, Full-text search.
Answered from the vendors’ own pages
eBay: What does selling on eBay actually cost?
A category-dependent percentage of the total buyer payment including postage, plus a fixed fee per order, plus any Store subscription, advertising rate and international fees. Model all of them together, not the first one alone.
turbopuffer: Can I self-host turbopuffer?
There is no open source or community edition. Single-tenant and bring-your-own-cloud deployments exist as commercial arrangements, but there is no way to run it independently of the vendor.
eBay: Can I use my own payment provider?
No. Payments run through eBay and settle to your bank account on eBay's payout schedule, so you do not choose the processor and you do not control settlement timing.
turbopuffer: How fast is it really?
Warm queries perform comparably to in-memory search engines. Cold queries, where data is not cached, have a documented p90 around 1,214 ms on a million documents. Write p90 is around 248 ms for a 512 KB upsert because writes go straight to object storage.
eBay: Do I get my customers' email addresses?
Not for marketing. eBay mediates buyer contact, which is why sellers who rely on it have no list to fall back on if the channel changes.
turbopuffer: Is it consistent?
Eventually consistent by default, with the vendor reporting that over 99.8% of queries return consistent data. Strong consistency can be requested per query at a latency cost. Large write bursts have a longer visibility delay while indexing catches up.
eBay: Is eBay an alternative to having my own store?
It is a channel, not a substitute. Sellers who use it well treat it as demand they rent while building something they own in parallel.
turbopuffer: What is it best at?
Large numbers of namespaces where most are idle. The architecture makes cold data cheap to keep, which is exactly the shape of a multi-tenant product with a long tail of inactive customers.
turbopuffer: What are the hard limits?
Up to 128 billion documents and 256 TB per namespace, 500 million documents per shard, 64 MiB per document, 10,752 dense vector dimensions, roughly 10,000 writes per second per namespace and a maximum result set of 10,000.
Related pages
More on turbopuffer
Other head to heads
- eBay vs Amazon Shopping
- eBay vs Gumroad
- eBay vs Mercari
- eBay vs Heartland Retail
- eBay vs Depop
- eBay vs Poshmark
- eBay vs Etsy
- eBay vs Wish
- eBay vs Vinted
- eBay vs NCR Voyix
- eBay vs Algopix
- eBay vs Namecheap
- eBay vs PrestaShop
- eBay vs Razorpay
- eBay vs Retail Pro
- eBay vs Saleor
- eBay vs SamCart
- eBay vs Sellfy
- eBay vs Chroma
- eBay vs BigQuery
- eBay vs Dremio
- eBay vs DuckDB
- eBay vs Trino
- eBay vs Typesense
- eBay vs Dragonfly
- eBay vs LanceDB
- eBay vs Readyset
- eBay vs TIBCO Enterprise Message Service
- eBay vs Vespa
- eBay vs Xata
- eBay vs EMQX
- eBay vs FaunaDB
- eBay vs Firebase Realtime Database
- eBay vs Memcached
- eBay vs MotherDuck
- eBay vs Firestore
- turbopuffer vs Amazon Shopping
- turbopuffer vs Gumroad
- turbopuffer vs Mercari
- turbopuffer vs Heartland Retail
- turbopuffer vs Depop
- turbopuffer vs Poshmark
- turbopuffer vs Etsy
- turbopuffer vs Wish
- turbopuffer vs Vinted
- turbopuffer vs NCR Voyix
- turbopuffer vs Algopix
- turbopuffer vs Namecheap
- turbopuffer vs PrestaShop
- turbopuffer vs Razorpay
- turbopuffer vs Retail Pro
- turbopuffer vs Saleor
- turbopuffer vs SamCart
- turbopuffer vs Sellfy
- turbopuffer vs Chroma
- turbopuffer vs BigQuery
- turbopuffer vs Dremio
- turbopuffer vs DuckDB
- turbopuffer vs Trino
- turbopuffer vs Typesense
- turbopuffer vs Dragonfly
- turbopuffer vs LanceDB
- turbopuffer vs Readyset
- turbopuffer vs TIBCO Enterprise Message Service
- turbopuffer vs Vespa
- turbopuffer vs Xata
- turbopuffer vs EMQX
- turbopuffer vs FaunaDB
- turbopuffer vs Firebase Realtime Database
- turbopuffer vs Memcached
- turbopuffer vs MotherDuck
- turbopuffer vs Firestore
