OpenWAF developer documentation
Guides, references and the API for the firewall, DNS and AI controls at the OpenWAF edge.
Start here
FundamentalsStart here: create your account, add your first site and learn how OpenWAF organizations, zones, roles and API tokens fit together.DNSAuthoritative DNS on your own nameserver pair, or keep your DNS provider and point sites with a CNAME. Every record change is versioned.API referenceManage zones, DNS records, edge settings, rules, analytics, AI agents and egress through the OpenWAF REST API.MCP serverThe OpenWAF Cloud remote MCP server lets an AI assistant manage zones, DNS records, edge settings and rules through the same API, roles and audit log.
Product directory
Get started
Network
Application security
AI
- AI Crawl ControlClassify each request as AI training, AI search, AI assistant, search engine, unverified automation, spoofed or human, and decide what each may do.
- MCP ShieldMCP Shield checks your MCP server's traffic at the OpenWAF edge: method and tool policy, prompt-injection and credential-leak checks, per-token limits.
- OpenWAF EgressA zero-trust outbound gateway for AI agents that checks every request and injects the provider key, self-hosted or hosted by OpenWAF Cloud.
Performance
Operations
Developer platform
- CLIopenwaf-cloud ctl manages zones, DNS records, edge settings, rules and certificates from the command line, with simulation and confirmation on every change.
- MCP serverThe OpenWAF Cloud remote MCP server lets an AI assistant manage zones, DNS records, edge settings and rules through the same API, roles and audit log.
- SDKsTyped TypeScript and Python clients for the OpenWAF API, generated from its OpenAPI contract, one file each, with no dependencies.
- API referenceManage zones, DNS records, edge settings, rules, analytics, AI agents and egress through the OpenWAF REST API.