Frequently Asked Questions

EnRoute is an Ingress Controller API Gateway built using Envoy Proxy. EnRoute is completely cloud-native and can be configured using it's easy-to-use interface. CRDs can be used to setup EnRoute. Using the configuration provided by the user, EnRoute computes Envoy configuration to program it.

EnRoute combines the functionality of both an Ingress Controller and API Gateway in one unified platform, making it the only solution that provides complete traffic management for Kubernetes environments.

Enterprise Trial: 30-day free trial of the Enterprise version with full features and support. Contact our sales team to get started.

Demo Environment: Schedule a personalized demo with our team to see EnRoute in action with your specific use cases.

No, EnRoute is not a Service Mesh. EnRoute is an API Gateway and Ingress Controller that handles north-south traffic (traffic coming into your cluster).

However, EnRoute integrates seamlessly with Service Mesh technologies like Istio and LinkerD to provide end-to-end mTLS and complete security coverage for both north-south and east-west traffic.

Yes, we provide a FIPS ready image for each EnRoute Enterprise version. Our FIPS 140-2 compliant build is specifically designed for government and highly regulated environments.

The FIPS compliant version includes validated cryptographic modules and meets all federal requirements for secure cryptographic implementations. Contact us if you need more information about FIPS deployment and certification.

The name Saaras comes from a crane, that is found in the Indian sub-continent. It has an ability to surmount heights while it takes a flight over the clouds.

This represents our mission to help organizations rise above the complexity of cloud-native infrastructure and achieve new heights in their digital transformation journey. Just like the Saaras crane soars effortlessly above challenges, our EnRoute Gateway helps you navigate and overcome the complexities of modern API and traffic management.