Documentation
Start here for installation, configuration, and API reference guides.
Read Documentation →SUPPORT
We're Here to Help
Have questions? We are a small team, but we aim to stay responsive and technically useful.
GitHub Issues
Report bugs, request features, or start technical discussions. We actively review new issues.
Open GitHub →Email Support
For more specific or sensitive questions. We aim to respond within 48 hours.
Send Email →Frequently Asked Questions
Fast answers for teams getting started.
Short answers to the most common questions before deploying WAFio in production, staging, or a small lab environment.
WAFio is free for small infrastructure: 1 control plane, 1 WAF agent, and 1 host agent per license. That makes it a practical starting point for SMBs, schools, individual operators, and software engineers. If you need larger deployments later, start with the free tier and expand from there.
Because small teams still face real attacks. The free tier lowers the barrier to adoption while keeping the self-hosted model intact: you run it on your own servers, keep control of your own traffic, and can evaluate real protection without procurement friction.
You need a Linux server, root access, and enough resources for your workload. For small environments, one control plane plus one WAF agent and one host agent is enough to get started with the free license.
Yes. WAFio is fully self-hosted, so your request data does not need to pass through WAFio-operated cloud infrastructure. You keep control over traffic, logs, and deployment.
Yes. WAFio is designed for smaller operators that need meaningful protection without enterprise complexity. The free tier is intentionally sized for compact infrastructure and early deployments.
WAFio is actively developed and updated. Detection logic and supporting components evolve over time, including improvements around OWASP CRS coverage and operational tooling.
Start with the documentation, then use GitHub Issues or email support for anything specific. We prefer clear, technical guidance over vague support promises.
Still have questions?
Contact us directly.
If the documentation does not cover everything, send an email or open an issue. We prefer direct technical conversations over unrealistic support promises.