koigrid vs Cloudflare WAF
Allow/block rules for your traffic — the built-in alternative to Cloudflare WAF and Vercel Firewall.
Cloudflare WAF set the bar for rule-based traffic filtering. koigrid gives you the core — allow/block by IP, CIDR, country, path, method or user-agent — as a fast rule engine your edge or agent calls to decide, with no per-request fee and right next to your apps.
| Feature | koigrid | Cloudflare WAF |
|---|---|---|
| Pricing | Included (no per-use fee) | Per plan / request |
| IP / CIDR / country | Yes | Yes |
| Path / method / UA | Yes | Yes |
| Allow-list overrides (priority) | Yes | Yes |
| Decision API | Yes | Partial |
| Manage by AI agent | Native | API |
What koigrid improves
One platform
Rules live next to the apps they protect.
No per-use fee
Included — no per-request WAF bill.
Agent-native
An agent blocks abuse the moment it sees it.
Frequently asked questions
Is koigrid cheaper than Cloudflare WAF?
It depends on the workload. koigrid charges for the RAM and disk you reserve, by the hour, shared vCPU included, from a public price list — with bandwidth included and no per-request fees. Egress-heavy setups usually come out well ahead; see the estimate above.
Can I migrate from Cloudflare WAF without lock-in?
Yes. koigrid runs on portable primitives — standard PostgreSQL, S3-compatible storage and containers — so you can move in (or out) whenever you want.
Where is my data hosted?
In data centers in the EU, on servers we run ourselves. The privacy policy says exactly where.
Can I run everything from an API or an AI agent?
Yes — koigrid is API-first and agent-native: every action has an API and a scoped token, with llms.txt and OpenAPI so an LLM can operate it end to end.