Developer Tools · head to head
Envoy vs turbopuffer

Envoy
Developer Tools
A high-performance L7 proxy written in C++ that is configured by an API rather than a config file, and is usually deployed under a control plane.
- From
- Free
- Free plan
- Yes

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
- Envoy is free; turbopuffer starts at $16/mo.
- Only Envoy lists xDS dynamic configuration; only turbopuffer lists vector search.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which Envoy and turbopuffer actually diverge.
| Attribute | Envoy | turbopuffer |
|---|---|---|
| Starting price | Free | $16/month |
| Pricing model | Open-source | Subscription |
| Free tier | Yes | No |
| Category | Developer Tools | Databases |
Identical on both: 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 Envoy
- xDS dynamic configuration
- Protocol breadth
- Filter chain architecture
- Observability by default
- Outlier detection
- Traffic shaping
- mTLS termination and origination
- Hot restart
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.
Envoy
- Acting as the data plane under a service mesh or Gateway API implementation, which is how the overwhelming majority of deployments use itnot turbopuffer
- An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot turbopuffer
- Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot turbopuffer
- Standardising observability across a polyglot estate, so that latency, error rates and tracing look the same regardless of the language a service is written innot turbopuffer
turbopuffer
- A product with one search index per customer and thousands of customers, most of whose data is idle on any given daynot Envoy
- Very large corpora where holding every vector in memory is the dominant cost and occasional cold-query latency is acceptablenot Envoy
- Hybrid retrieval combining BM25 and vector search where running and synchronising two separate systems is the problem being solvednot Envoy
- Retrieval for agent and assistant products where indexes are created and destroyed frequently and per-index overhead must be near zeronot Envoy
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Envoy
- The configuration surface is very large and hand-written bootstrap YAML runs to hundreds of lines for routing that Nginx expresses in twenty, which is why nearly every production deployment sits under a control plane and inherits that control plane's constraints as well
- xDS is the real API and it is not stable in the comfortable sense; the v2 API set was removed outright, resource types continue to be deprecated, and your control plane and Envoy binaries have to be upgraded roughly in step or the proxies stop accepting configuration
- Extending it properly means writing a C++ filter and building and maintaining your own Envoy binary; the alternatives are Lua, which adds per-request overhead, and proxy-wasm, whose ABI has remained effectively experimental for years with a real performance cost
- At sidecar density the per-proxy memory and CPU footprint is a measurable share of cluster capacity, since thousands of workloads each carry a full proxy, and this is precisely the cost that has pushed mesh projects towards node-level or ambient architectures
- There is no single vendor selling support for Envoy itself; you get the community plus control-plane vendors such as Solo.io and Tetrate, so an Envoy-level production bug is your own engineers in a C++ codebase unless a support contract happens to cover it
- Diagnosing why a request got a particular response involves reading config dumps, the stats endpoint and the RESPONSE_FLAGS codes in access logs rather than a readable error, which is a specific skill you must hire or spend months growing
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
Envoy
FreeNo published plan breakdown. See the Envoy 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 Envoy if
- You need xds dynamic configuration.
- You want to start without paying.
- You also want protocol breadth.
Choose turbopuffer if
- You need object storage architecture.
- You also want namespaces.
Questions people ask
- Is Envoy or turbopuffer better?
- Neither clearly leads. Envoy starts at Free and turbopuffer at $16/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Envoy or turbopuffer?
- Envoy has a free tier; the other does not. Paid plans start at Free for Envoy and $16/month for turbopuffer.
- Does Envoy or turbopuffer run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- Can I use Envoy for free?
- Yes. Envoy has a free tier, so you can try it without paying. turbopuffer starts at $16/month.
- What is Envoy best used for?
- Envoy is most often used for acting as the data plane under a service mesh or gateway api implementation, which is how the overwhelming majority of deployments use it, an edge or api gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxying, migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow traffic, standardising observability across a polyglot estate, so that latency, error rates and tracing look the same regardless of the language a service is written in. Of those, acting as the data plane under a service mesh or gateway api implementation, which is how the overwhelming majority of deployments use it and an edge or api gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxying are not what turbopuffer is typically brought in for.
- What can Envoy do that turbopuffer cannot?
- Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. turbopuffer covers Object storage architecture, Namespaces, Vector search, Full-text search.
Answered from the vendors’ own pages
Envoy: Should I run Envoy on its own, or under a control plane?
Almost always under one. Directly authoring xDS or static bootstrap configuration is viable for a handful of routes and becomes unmanageable beyond that. Envoy Gateway, Istio, Contour, Gloo and Consul all exist to generate that configuration for you.
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.
Envoy: How does it compare with Nginx or HAProxy?
Envoy is dynamically configured over an API and instrumented far more heavily; Nginx and HAProxy are faster to configure and lighter for straightforward reverse proxying. If you never need to change routing without a reload, Envoy is more machinery than the problem requires.
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.
Envoy: What does it cost?
Nothing to licence; it is Apache 2.0 and there is no paid edition. The cost is engineering time and, for most organisations, a commercial control plane or cloud service that packages it.
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.
Envoy: Can I write extensions without C++?
You can write Lua filters or proxy-wasm modules in Rust, Go, C++ or AssemblyScript. Both carry per-request overhead compared with a native filter, and the Wasm path has been slower to stabilise than the project originally projected.
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.
Envoy: Is it a CNCF project?
Yes, it is a graduated CNCF project licensed under Apache 2.0, which means the trademark and governance sit with the foundation rather than with Lyft or any vendor.
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
- Envoy vs Istio
- Envoy vs Ona (formerly Gitpod)
- Envoy vs Spacelift
- Envoy vs Atlantis
- Envoy vs Jenkins
- Envoy vs Hookdeck
- Envoy vs Restate
- Envoy vs Helix
- Envoy vs Turborepo
- Envoy vs StackBlitz
- Envoy vs Webpack
- Envoy vs Backstage
- Envoy vs OpsLevel
- Envoy vs PartyKit
- Envoy vs PhpStorm
- Envoy vs Pieces for Developers
- Envoy vs RAD Studio
- Envoy vs Refact
- Envoy vs Chroma
- Envoy vs BigQuery
- Envoy vs Dremio
- Envoy vs DuckDB
- Envoy vs Trino
- Envoy vs Typesense
- Envoy vs Dragonfly
- Envoy vs LanceDB
- Envoy vs Readyset
- Envoy vs TIBCO Enterprise Message Service
- Envoy vs Vespa
- Envoy vs Xata
- Envoy vs EMQX
- Envoy vs FaunaDB
- Envoy vs Firebase Realtime Database
- Envoy vs Memcached
- Envoy vs MotherDuck
- Envoy vs Firestore
- turbopuffer vs Istio
- turbopuffer vs Ona (formerly Gitpod)
- turbopuffer vs Spacelift
- turbopuffer vs Atlantis
- turbopuffer vs Jenkins
- turbopuffer vs Hookdeck
- turbopuffer vs Restate
- turbopuffer vs Helix
- turbopuffer vs Turborepo
- turbopuffer vs StackBlitz
- turbopuffer vs Webpack
- turbopuffer vs Backstage
- turbopuffer vs OpsLevel
- turbopuffer vs PartyKit
- turbopuffer vs PhpStorm
- turbopuffer vs Pieces for Developers
- turbopuffer vs RAD Studio
- turbopuffer vs Refact
- 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
