Changelog

Changes to OpenWAF Egress, newest first.

OpenWAF Egress, open source

OpenWAF Egress is now open source under the Apache License 2.0. Agents hold a placeholder token instead of the provider key; the gateway checks every request against the agent's allowed targets, an SSRF check, 27 prompt-injection detectors and data-leak patterns, and only then injects the real key from OpenBao or HashiCorp Vault. It ships as a container for linux/amd64 and linux/arm64 and as Linux and macOS binaries.

See the OpenWAF Egress overview and the quickstart.

Hosted AI egress in early access

OpenWAF Cloud now runs the egress gateway for you at https://egress.openwaf.dev, in early access. From the new AI egress page, the API or the MCP server, an organization admin creates one agent per app with its own token (shown once), stores provider keys that can only be replaced, never read back, and adds custom HTTPS targets next to a catalog of 13 providers. Every refused call appears in Blocked requests, live. Write to [email protected] to join.

See get started with hosted egress.

Last updated:

↑↓ to navigate↵ to openesc to close