MTE Relay Server v4.6 builds on the v4.5 Go rewrite with flexible cloud-marketplace billing, first-class Azure Kubernetes Service (AKS) marketplace packaging, and outbound-proxy reliability fixes.
This release focuses on how the relay is deployed and metered across cloud marketplaces and on-prem, without changing application traffic flow.
MTE Relay Server v4.5 is a ground-up rewrite of the relay in Go. Releases through v4.4 ran on Node.js; v4.5 reimplements the entire proxy as a single, statically compiled Go service.
The rewrite delivers lower memory use, faster request handling, and a smaller, hardened container image, while keeping the MTE/MKE encryption and Kyber pairing protocol intact so existing clients keep working. It also introduces a new multi-tenant configuration model that becomes the preferred way to run the relay.
MTE Relay Server v4.4 adds more flexible logging controls, better request-level observability, and improved upstream connection handling.
This release is aimed at making production behavior easier to tune and diagnose without changing application traffic flow.
MTE Relay Server v4.3 adds stronger server-to-server pairing controls and clearer startup warnings for non-production trial builds.
This update focuses on safer deployment behavior and better visibility into unsupported runtime configurations.
MTE Relay Server v4.2 expands request-handling flexibility, improves default concurrency, and tightens proxy and cache adapter behavior.
The release includes streaming controls, Redis TLS support, and several fixes that improve compatibility under real traffic conditions.
MTE Relay Server v4.1 improves deployment flexibility and makes proxy behavior more reliable across both successful and error responses.
The release also simplifies configurations that do not need browser CORS support and improves request tracing while debugging.