Softwr

Technology · head to head

Envoy vs PartyKit

Envoy logo

Envoy

Technology

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
Full reviewWebsite
P

PartyKit

Developer Tools

Platform for building and deploying realtime multiplayer servers on the edge

From
Free
Free plan
Yes
Full reviewWebsite

The short version

  • Each has a real cost: 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.; PartyKit documentation and FAQ material on the marketing site is sparse compared to larger realtime platforms.
  • They diverge on capability: Envoy covers xDS dynamic configuration, PartyKit covers Stateful edge servers.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Envoy and PartyKit actually diverge.

Attributes where Envoy and PartyKit differ
AttributeEnvoyPartyKit
Pricing modelopen-sourcefreemium
PlatformsWebweb, api
CategoryTechnologyDeveloper Tools

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

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 PartyKit

  • Stateful edge servers
  • WebSocket-first API
  • CRDT library compatibility
  • Framework integrations
  • Global edge deployment
  • Custom domains

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 PartyKit
  • An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot PartyKit
  • Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot PartyKit
  • 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 PartyKit

PartyKit

  • Multiplayer collaborative appsnot Envoy
  • Realtime AI agent backendsnot Envoy
  • Live cursors and presencenot Envoy
  • Collaborative whiteboards and documentsnot 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.

PartyKit

  • Documentation and FAQ material on the marketing site is sparse compared to larger realtime platforms.
  • Commercial free tier requires deploying to the user's own Cloudflare account, adding setup complexity.
  • Storage on the free Individual plan clears every 24 hours, limiting it to prototyping rather than persistent production data.
  • Smaller ecosystem and community than more established realtime infrastructure providers.

Pricing, plan by plan

Envoy

Free

No published plan breakdown. See the Envoy review.

PartyKit

Free
  • IndividualFree
    • Up to 10 live projects
    • Deploy to the global edge platform
    • Storage clears every 24 hours
  • CommercialFree
    • Unlimited projects
    • Custom domains
    • Runs on your own Cloudflare account; pay only Cloudflare usage

Which should you pick?

Choose Envoy if

  • You need xds dynamic configuration.
  • You want to start without paying.
  • You also want protocol breadth.
Envoy review

Choose PartyKit if

  • You need stateful edge servers.
  • You want to start without paying.
  • You work on web, api.
  • You also want websocket-first api.
PartyKit review

Questions people ask

Is Envoy or PartyKit better?
Neither clearly leads. Envoy starts at Free and PartyKit at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or PartyKit?
Envoy starts at Free and PartyKit at Free.
Does Envoy or PartyKit run on more platforms?
Envoy runs on Web. PartyKit runs on web, api.
Can I use Envoy for free?
Both have a free tier, so you can try either at no cost before committing.
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 PartyKit is typically brought in for.
What can Envoy do that PartyKit cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. PartyKit covers Stateful edge servers, WebSocket-first API, CRDT library compatibility, Framework integrations.

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.

PartyKit: How much does PartyKit cost?

PartyKit is completely free. Both the Individual and Commercial plans have no upfront costs.

Source
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.

PartyKit: What is PartyKit's Individual plan?

The Individual plan is free and includes deployment to a global edge platform, support for up to 10 live projects, and is suitable for small projects. Storage is cleared every 24 hours.

Source
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.

PartyKit: What is PartyKit's Commercial plan?

The Commercial plan is free but requires deploying to your own Cloudflare account. It includes custom domains, unlimited projects, and you pay only your Cloudflare usage costs.

Source
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.

PartyKit: Can I upgrade from Individual to Commercial plan?

Yes, both plans are free but offer different feature sets. The Commercial plan removes project restrictions but requires managing your own Cloudflare infrastructure.

Source
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.

Share

Related pages

More on Envoy

More on PartyKit

Keep looking

Other head to heads