Softwr

Developer Tools · head to head

Envoy vs Timeplus

Envoy logo

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

Timeplus

Databases

Streaming SQL engine built on ClickHouse internals, shipping as one small binary

From
Free
Free plan
Yes

The short version

  • Envoy is free; Timeplus starts at $199/mo.
  • Only Envoy lists xDS dynamic configuration; only Timeplus lists streaming SQL.
  • Prices and features on this page were last checked on 13 November 2026.

How do Envoy and Timeplus differ?

Envoy and Timeplus differ on pricing model, platforms and category (Developer Tools against Databases). Only the attributes on which Envoy and Timeplus actually diverge.

Attributes where Envoy and Timeplus differ
AttributeEnvoyTimeplus
Pricing modelOpen-sourcePer month for cloud, quoted for self-hosted
PlatformsWebLinux, macOS, Self-hosted, Web
CategoryDeveloper ToolsDatabases

Identical on both: starting price (Free), free tier (Yes).

Which features does each one have?

They share no listed features; 8 appear only for Envoy and 6 only for Timeplus. 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 Timeplus

  • Streaming SQL
  • Unified streaming and historical
  • ClickHouse-based engine
  • Single binary deployment
  • External streams
  • Materialised views

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

Timeplus

  • Real-time alerting on Kafka topics where standing up a Flink cluster is more work than the use case justifiesnot Envoy
  • Fraud or anomaly detection that must join a live event stream against recent history in one querynot Envoy
  • Streaming ETL from Kafka or MySQL change data capture into ClickHouse without writing Javanot Envoy
  • A small data team that needs continuous aggregation but has no platform engineers to operate JVM infrastructurenot Envoy

Where do Envoy and Timeplus fall 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

Timeplus

  • Proton, the free version, is single-node by design, so any requirement for high availability or horizontal scale forces the commercial licence; the open source edition is a trial in practical terms
  • It is a young project against Apache Flink’s decade of production history, so the hiring pool, the connector library and the body of known failure modes are all much smaller
  • Inheriting ClickHouse internals also inherits ClickHouse constraints: memory-hungry queries, awkward updates and a SQL dialect that is not portable to other engines
  • Exactly-once semantics and state recovery guarantees are less battle-tested than Flink checkpointing, which matters if the pipeline moves money
  • Cloud pricing is by provisioned instance size rather than usage, so a bursty workload pays for peak capacity around the clock or has to be resized by hand

How much do Envoy and Timeplus cost?

Envoy is free to use; Timeplus has a free plan, with paid plans from $199/mo. Plan by plan below, from each vendor's own pricing page.

Envoy

Free

No published plan breakdown. See the Envoy review.

Timeplus

Free
  • Timeplus ProtonFree
    • Apache 2.0 licence
    • Single node only
    • Full streaming SQL engine
  • Timeplus Cloud$199/mo
    • One to thirty-two CPUs
    • 4 GB to 128 GB memory
    • From 250 GB SSD storage
  • Self-hosted or BYOCOn request
    • Multi-node clustering
    • Kubernetes or bare metal
    • Customisable compute and storage

Which should you pick?

Choose Envoy if

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

Choose Timeplus if

  • You need streaming sql.
  • You want to start without paying.
  • You work on Linux, macOS, Self-hosted, Web.
  • You also want unified streaming and historical.

Questions people ask

Is Envoy or Timeplus better?
Neither clearly leads. Envoy starts at Free and Timeplus at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Envoy or Timeplus?
Envoy starts at Free and Timeplus at Free.
Does Envoy or Timeplus run on more platforms?
Envoy runs on Web. Timeplus runs on Linux, macOS, Self-hosted, Web.
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 Timeplus is typically brought in for.
What can Envoy do that Timeplus cannot?
Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Timeplus covers Streaming SQL, Unified streaming and historical, ClickHouse-based engine, Single binary deployment.

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.

Timeplus: Is Timeplus open source?

The core engine, Timeplus Proton, is Apache 2.0. Timeplus Enterprise and Cloud are commercial.

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.

Timeplus: What is the difference from Flink?

Timeplus is one binary with SQL as the only interface; Flink is a JVM cluster with a Java and SQL API and far more operational surface.

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.

Timeplus: Can Proton run in production?

It can, but it is single-node only, so there is no high availability without the commercial edition.

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.

Timeplus: How much is the cloud?

From 199 US dollars a month, sized by CPU and memory, with a fourteen day trial.

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

Other head to heads