Managing APIs has never been just a technical challenge. For organizations in finance, healthcare, and government, it is also a compliance challenge. Routing API traffic through a cloud gateway works well for many organizations, but for those operating under data residency regulations or with infrastructure distributed across cloud and private cloud systems, that model creates constraints.
Today, we’re introducing the API Edge Gateway, a new deployment option that lets you process and manage API traffic directly within your own infrastructure, without routing requests through the cloud.
Centralized Control with Local Containment
The Edge Gateway runs inside your infrastructure as a containerized data plane. It handles API traffic locally while remaining connected to Workato’s cloud control plane for configuration, policy management, and observability. Only observability data leaves your environment. Request and response data never do.
This split architecture gives your team the governance and centralized management you need, with the data containment your compliance requirements demand.
Where the Edge Gateway Makes a Difference
Keep Sensitive API Traffic Compliant and Under Control
When your industry requires that data stay within specific boundaries, routing API traffic through the cloud is not always an option. The Edge Gateway keeps all traffic within your private cloud while giving your team centralized control through Workato. You do not have to choose between compliance and unified API management.
Built for: organizations subject to data residency regulations, and enterprises in finance or healthcare operating under laws that restrict sensitive data from traversing public cloud infrastructure.
Enforce Consistent Policies Across Your Entire API Landscape
Managing APIs across cloud and private cloud environments often leads to fragmented policy enforcement and gaps in observability. The Edge Gateway brings private cloud execution under the same Workato control plane as your cloud-deployed APIs, so your team works from a single source of truth regardless of where APIs run.
Built for: enterprises managing APIs across private cloud and public cloud environments, and teams with APIs that cannot be routed through a cloud gateway due to network or security restrictions that want to enforce consistent security and governance across their entire API landscape.
Reduce Latency for High-Throughput Workloads
For latency-sensitive workloads, processing traffic locally makes a measurable difference. Keeping traffic close to the systems it serves removes unnecessary distance from the critical path.
Built for: real-time order management and fulfillment systems, and customer-facing applications where API response time directly affects user experience.
Production-Ready From Day One
The Edge Gateway comes with request proxying, rate and concurrency limits, response caching, authentication support (Token, JWT, OIDC, OAuth), mutual TLS (mTLS), JSON request validation, and OpenTelemetry integration for streaming metrics, traces, and logs to platforms including Datadog and Splunk.
Getting started is straightforward. Deploy the container in Docker or Kubernetes, authenticate with a one-time token, and select it as a deployment target for any API collection directly from the Workato interface. Cloud and Edge Gateway deployments can coexist, so you can target an API collection to the cloud, the Edge Gateway, or both.
Get Started
To deploy the Edge Gateway, visit the docs for more details, or contact your account team to discuss whether it is the right fit for your team.