Technology · head to head
Envoy vs Height
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
- Rated
- -
Height
Technology
A project management tool from a small independent vendor that uses AI agents to handle routine ticket maintenance.
- From
- Free
- Rated
- -
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.; Height it is one product from one small venture-funded company with no second line of business underwriting it, so adopting it as your system of record is a bet on that company's funding, and the tool holds work history you would have to reconstruct elsewhere if the bet fails.
- They diverge on capability: Envoy covers xDS dynamic configuration, Height covers Autonomous triage.
- Prices and features above were last checked on 30 August 2026.
Where they differ
Only the attributes on which Envoy and Height actually diverge.
Identical on both: starting price (Free), free tier (Yes), platforms (Web), user rating (Not yet rated), category (Technology).
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 Height
- Autonomous triage
- Duplicate detection
- Attribute maintenance
- Per-task chat
- Multiple views
- Developer integrations
- Custom fields and filters
- Public API
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 Height
- An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Height
- Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Height
- 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 Height
Height
- A product or engineering team with no dedicated project manager, where backlog upkeep currently falls on whoever has timenot Envoy
- Teams leaving Jira because its configuration and administration cost more attention than the tracking is worthnot Envoy
- A support or intake queue where incoming requests need categorising and deduplicating before anyone can plan themnot Envoy
- Startups that want tasks, chat and progress tracking in one tool rather than stitching a tracker to a chat appnot 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.
Height
- It is one product from one small venture-funded company with no second line of business underwriting it, so adopting it as your system of record is a bet on that company's funding, and the tool holds work history you would have to reconstruct elsewhere if the bet fails.
- The 2024 relaunch as Height 2.0 reoriented the product around AI agents and changed workflows customers had already built on, which is the clearest available evidence of how much the product may be re-shaped again under you.
- The ecosystem is small next to Jira, Linear and Asana: fewer third-party integrations, no consultancy market, and far less written material to search when something behaves unexpectedly, so support questions go to the vendor and wait.
- The automation only pays off if tasks contain enough substance for a model to work with; on a team whose tickets are two-word titles, the agents have nothing to triage or deduplicate and the product reduces to an ordinary tracker at a premium.
- Task content is processed by hosted large language models, so a security review becomes a question about subprocessors and data handling, and there is no self-hosted or on-premises deployment to fall back on if the answer is unacceptable.
- There is no widely used two-way synchronisation with Jira, so an organisation where one team adopts Height and the rest stay on Jira ends up with two systems of record and manual reconciliation between them.
Pricing, plan by plan
Envoy
FreeNo published plan breakdown. See the Envoy review.
Height
FreeNo published plan breakdown. See the Height review.
Which should you pick?
Choose Envoy if
- You need xds dynamic configuration.
- You want to start without paying.
- You also want protocol breadth.
Choose Height if
- You need autonomous triage.
- You want to start without paying.
- You also want duplicate detection.
Questions people ask
- Is Envoy or Height better?
- Neither clearly leads. Envoy starts at Free and Height at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Envoy or Height?
- Envoy starts at Free and Height at Free.
- Does Envoy or Height run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- 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 Height is typically brought in for.
- What can Envoy do that Height cannot?
- Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default. Height covers Autonomous triage, Duplicate detection, Attribute maintenance, Per-task chat.
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.
Height: How is this different from Jira automation?
Jira automation is rule-based: you define a trigger and an action. Height's agents read the content of tasks and act on judgement, such as recognising that two tickets describe the same bug, which no rule can express.
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.
Height: Can we self-host it?
No. It is software as a service only, with no on-premises or private-cloud deployment. If your requirements rule out a hosted tracker, this is not a candidate.
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.
Height: What happens to our data if the company fails?
You would need an export and a migration to another tool. This is the standard risk with a single-product startup, and it is worth confirming the export path covers task history, comments and custom fields before committing to it.
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.
Height: Does it work for non-engineering teams?
Yes, the views and custom fields are generic enough for marketing, operations or support queues. Its integrations, though, are aimed at software teams, so a non-engineering team gets less of the surrounding value.
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.
Height: Do the AI features need our tickets to be well written?
In practice, yes. Triage, deduplication and attribute maintenance work from what is written in the task, so the return is much higher on a team that already writes descriptive tickets than on one that does not.
Related pages
Other head to heads
- Envoy vs ClickUp
- Envoy vs Linear
- Envoy vs Asana
- Envoy vs Figma
- Envoy vs Istio
- Envoy vs Finxact
- Envoy vs Jenkins
- Envoy vs Mozilla Firefox
- Envoy vs Thought Machine
- Envoy vs Alkami
- Envoy vs Heap
- Envoy vs Personetics
- Envoy vs Lovable
- Envoy vs Miro
- Envoy vs Plane
- Envoy vs Postman
- Envoy vs Monday.com
- Envoy vs Shortcut
- Envoy vs Coda
- Envoy vs Intercom
- Envoy vs Attio
- Envoy vs Kubernetes
- Envoy vs Notion
- Envoy vs Site24x7
- Envoy vs StatusCake
- Envoy vs Storybook
- Envoy vs WebStorm
- Envoy vs Zabbix Cloud
- Height vs ClickUp
- Height vs Linear
- Height vs Asana
- Height vs Figma
- Height vs Istio
- Height vs Finxact
- Height vs Jenkins
- Height vs Mozilla Firefox
- Height vs Thought Machine
- Height vs Alkami
- Height vs Heap
- Height vs Personetics
- Height vs Lovable
- Height vs Miro
- Height vs Plane
- Height vs Postman
- Height vs Monday.com
- Height vs Shortcut
- Height vs Coda
- Height vs Intercom
- Height vs Attio
- Height vs Kubernetes
- Height vs Notion
- Height vs Site24x7
- Height vs StatusCake
- Height vs Storybook
- Height vs WebStorm
- Height vs Zabbix Cloud