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.
In distributed systems today, secure and resilient communication is everything. As both cyber threats and future quantum risks continue to evolve, architectures must prepare now for quantum-resistant data transport. Two technologies — MTE API Relay from Eclypses and Envoy Proxy — can work together to achieve exactly that.
Envoy is a high-performance L4/L7 proxy designed for service-to-service communication, load balancing, observability, and traffic management. It powers many modern service meshes, such as Istio and Consul.
MTE API Relay is a lightweight, containerized proxy that provides end-to-end encryption using Eclypses’ MicroToken Exchange (MTE) technology. It protects every byte of data that moves between trusted server components, ensuring that no untrusted network or intermediary can access or alter sensitive information. MTE encryption is designed with Quantum Resistant Enforcement (QRE) in mind — protection not only for current threats but also for attacks possible in the quantum era.
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.
The Eclypses MTE API Relay Container-type product is now available in the AWS Marketplace.
Eclypses MTE API Relay Server is a proxy server deployed through a docker container. Due to the success of the MTE Relay Server container for Client/Server use-cases, the decision was made to publish the MTE API Relay through the AWS marketplace for Server-to-Server network level communication for HTTP Requests between API Services.
Network-level protection for HTTP Requests between AWS and another AWS Region, account, etc. As the product evolves, the "3rd Party Environment" could be another cloud service like Azure, or an on-premise container.
Big changes:
The Eclypses MTE Relay Server Container-type product is now available in the AWS Marketplace.
Big changes:
More information is available here.
The license key has NOT changed
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.