Pinned Tweet
Protect every site you run, without touching a server. OpenWAF puts a managed WAF, AI-bot control, a proof-of-work check and DNS in front of every domain, on an EU edge. Run it from a dashboard or your AI assistant. Free for up to 100 domains: openwaf.dev
OpenWAF Browsers is now a verified bot in Cloudflare Radar's Bots Directory: Intermediary access, Immediate content use, Web Bot Auth verification.
Our browsers sign requests by default, one Ed25519 key per customer org.
openwaf.dev/news/openwaf-bro…
21
termediary access, Immediate content use, Web Bot Auth verification.
Our browsers sign requests by default, one Ed25519 key per customer org.
openwaf.dev/news/openwaf-bro…
10
OpenWAF Deploy is free during the beta: turn it on from the dashboard and deploy up to 2 apps on your own server, behind our edge.
The agent is open source (Apache-2.0) and only dials out.
openwaf.dev/deploy
3
Our first edge node now runs a kernel with the upstream fix for CVE-2026-98432. Rebooted, serving again in under 30 seconds.
The nftables rule stays on every host until each one runs a fixed kernel:
ip protocol tcp ip hdrlength != 5 drop
1
1
117
openwaf-sensor 0.3.1 checks NFS and SMB mounts without hanging on them: probes run off the sampler thread, and a mount that doesn't answer in 60 seconds becomes an alert instead of a frozen agent.
Also new: software RAID checks from /proc/mdstat.
16
"Zero-downtime deploys" is easy to write. So our test suite redeploys an app under a constant request loop and fails on a single dropped request.
Last run: 54,540 requests, 0 failed.
22
When a deploy fails, OpenWAF Deploy now names the cause instead of handing you a log: a closed list of causes, each with its details and what to do about it.
The app header also shows what is really running, not just what you asked for: restart loops and exit codes included.
18
OpenWAF Deploy: managed deployment for agencies, integrated with managed edge security.
Your servers. Your infrastructure. An open-source agent (Apache-2.0), outbound-only, with signed, reproducible releases and verifiable provenance.
github.com/openwaf-dev/deplo…
2
47
OpenWAF Deploy is in public beta. git push, and a Rust agent on your own server builds and runs the app. It dials out with Ed25519-signed messages, so we hold no SSH keys, and app ports open only to our edge. First site moved off Coolify: 532/532 requests 200 at the DNS cutover.
3
114
How it works, what the beta does not do yet, and a live demo: openwaf.dev/news/openwaf-dep…
25
Two bots, same IP, same second: Googlebot-Image asked for /env.txt, Twitterbot for /config.json. Neither checked out: not Google's reverse DNS, not in X's IP ranges.
OpenWAF verifies every bot claim. On openwaf.dev this week: 4,463 crawler requests verified.
1
29
Per bot: published IP ranges, reverse DNS or a Web Bot Auth signature. Never the user agent alone. Then your policy decides: allow, challenge or block.
openwaf.dev/ai-agents/
1
16
New: vulnerability briefings. One page per critical CVE with status, what to do now, what our edge covers and what it doesn't, sources and a dated chronology. Check your own sites from your agent with our vuln_exposure MCP tool. JSON and Atom feed.
openwaf.dev/briefings/
47
Agents get stuck on logins, 2FA and CAPTCHAs. We don't solve CAPTCHAs.
Instead an admin takes control for that step: a 10-minute link, logged in the audit trail, and the agent keeps its CDP session.
Beta, hosted in Germany, 20 free browser-hours a month: developers.openwaf.dev/brows…
1
1
72
An agent's browser shouldn't be able to reach your cloud metadata.
Every request from OpenWAF Browsers leaves through a proxy: ports 80 and 443 only, never private, loopback, CGNAT or 169.254.169.254. Every request is logged.
developers.openwaf.dev/brows…
42
Each org on OpenWAF Browsers signs with its own Ed25519 key under one Signature-Agent.
A site can allow all our browsers, or rate-limit or block one customer by keyid without touching others. Orgs can't rotate their own key, so they can't shed a block.
developers.openwaf.dev/brows…
25
OpenWAF Browsers is real Chrome for AI agents, and it doesn't hide.
No stealth patches, no fingerprint spoofing, no residential proxies, no CAPTCHA solving. Requests are signed with Web Bot Auth by default, so sites know an agent is visiting.
Why: developers.openwaf.dev/brows…
1
40
A User-Agent is just text. Anyone can type "Googlebot".
Web Bot Auth adds a signature: the agent signs each request with an Ed25519 key it publishes in a public directory, and the edge checks it before the app sees anything.
How our edge verifies: developers.openwaf.dev/ai-cr…
19
Any credential that has been in a contaminated environment, in a log or in a temp file counts as exposed. Rotate it, revoke the sessions, and check the access audit for use from somewhere it should not have been. Rotating costs an afternoon; not rotating costs an incident.
28
