A web application firewall for Envoy Gateway, written in Rust.
A WAF you can switch on, and leave on.
Revetment runs the OWASP Core Rule Set inside Envoy Gateway. It starts each new route in shadow, shows you the rule, the parameter and the value that matched, and promotes the route to blocking in stages you set.
helm install revetment \
oci://registry.revetment.io/charts/revetment \
--version 0.1.0 \
-n revetment-system \
--create-namespaceStep-by-step guides for EKS, GKE and DigitalOcean. AKS hasn't been tested yet.
Capabilities
A WAF for the gateway you already run.
It keeps the evidence and the controls in one place, so a rule change can be inspected before it is enforced.
The OWASP Core Rule Set
The rules you already trust, running in Envoy Gateway, with the CRS compatibility under Apache-2.0.
Inside the gateway
A dynamic module in Envoy Gateway. No sidecar, no extra network hop, and one Helm install.
Scoped exceptions
An exception names a rule, a route and a parameter. There is no single click that disables a rule across the cluster.
Evidence for every match
By default, each match records the rule, the route and the parameter, plus a bounded, redacted excerpt of the value that matched. Auth headers are never recorded.
CRDs and a console
Policies and exceptions are Kubernetes CRDs. Blocking runs in the data plane, so it does not depend on the console being up.
Priced per cluster
No per-request pricing. Detection is never held back for a paid plan; the free tier decides block or allow exactly as the paid one does.
We run Revetment on our own production. The numbers and the commands behind them are onthe proof page; the limits are onwhat it cannot stop.
How a route gets to blocking
Nothing is refused until you've seen what would be.
Plenty of WAFs get installed and never leave detect-only, because switching them on is a guess about what will break. Revetment gives you the evidence first, one route at a time.
Shadow
New routes start in shadow mode. When a request would have been blocked, you get the rule that matched, the parameter, and the part of the value it matched on. The request still goes through.
Triage
Hits are grouped by rule, route and parameter, with a plain explanation of each. Before you add an exception, you see how much traffic it would let through.
Promote
Blocking goes out to 1% of matching traffic, then 10%, then all of it. If the block rate passes the threshold you set, it rolls back on its own.
Pricing
Priced per cluster. Never per request.
Everything that decides whether a request gets blocked is free and Apache-2.0, on as many clusters as you like. Pro is for running it across a fleet.
Free
The whole WAF. No feature that affects blocking is held back from this tier.
- The Revetment engine with the OWASP Core Rule Set
- Attaches to Envoy Gateway in-process; your routes, TLS and listeners stay as they are
- Shadow mode and the full false-positive triage workflow
- Every rule update and security fix, the same day Pro gets it
- Prometheus metrics and OTLP export
- Hosted console for one cluster, 7 days of history, on request
Pro
Founding price, locked for 12 months from the day you sign up. After that the list price applies: $149 a month or $1,490 a year.
The same WAF run across many clusters, by a team, with history you can show an auditor.
- Everything in Free
- One console for every cluster
- 13 months of event history and audit-log export
- Rule updates rolled out cluster by cluster, with automatic rollbackplanned · Q1 2027
- Single sign-on (SAML, OIDC) and rolesplanned · Q1 2027
- Tuning suggestions from your own false-positive historyplanned · Q1 2027
Support is best effort, from the maintainer, with no SLA.
Start ProEnterprise
For clusters with no route to the internet, or an auditor who wants evidence on paper.
- Everything in Pro
- Rule bundles for air-gapped clusters
- Evidence packs for SOC 2 and PCI DSS 6.4.2
- Migration and rollout work, scoped and priced up front
- FIPS build of the data planeplanned
Support is best effort on every tier, with no SLA. See who builds this, below.
Talk to usWe don't charge by traffic, rules, routes or seats, and security fixes are never held back for a paid tier. A bill that grows with traffic is biggest in the middle of an attack.
Who builds it
One person builds Revetment.
That's a real risk if you're about to depend on it, so here's what you'd have if I stopped tomorrow. The licence is Apache-2.0. The chart and images are public, so you can mirror them. Blocking runs inside your cluster and doesn't need our console to be up. The source repository is private for now. The licence covers what you install.
- Report a flaw
- Privately, to the maintainer. How to reach us
- Acknowledged
- Within 48 hours, by a person
- Fixes
- Free, on every tier
- Your traffic
- Inspected inside your cluster. If you connect a console, it receives event records, not your traffic.
- This site
- Makes no requests to third parties. No analytics scripts, no fonts from a CDN.