A public hostname changes what a homelab service is. A notes app, a media index, or an admin panel that answers from outside the house is no longer a LAN convenience. It is a web application on the internet, and it can be probed for the same injection, traversal, and abuse patterns aimed at any other site. I place a self-hosted WAF in front of those services when, and only when, I can publish them as HTTP or HTTPS through a reverse proxy. I do not treat that choice as a blanket rule for every container on the network.
SafeLine is a self-hosted web application firewall meant to protect web apps by filtering and monitoring HTTP traffic between the application and the internet. Deployed in front of the app, it works as a reverse proxy: clients pass through it before they reach the server, and it blocks malicious HTTP and HTTPS traffic while forwarding what its policies treat as safe. The same description says it also aims to prevent unauthorized data from leaving the app. Those statements are the product model I rely on, and they come from the project documentation at https://docs.waf.chaitin.com/en/home.
The attack list is specific enough to use as a decision filter. The introduction names SQL injection, XSS, code injection, OS command injection, CRLF injection, LDAP injection, XPath injection, RCE, XXE, SSRF, path traversal, backdoor, brute force, HTTP flood, and bot abuse. Core capabilities listed alongside that coverage are defenses for web attacks, proactive bot-abuse defense, HTML and JS code encryption, IP-based rate limiting, and a web access control list. Rate limiting throttles traffic above defined limits to defend against DoS attacks, brute-force attempts, traffic surges, and other abuse. A CAPTCHA challenge is documented as allowing human users while blocking crawlers and bots. An authentication challenge blocks visitors who do not enter the required password. Dynamic protection, when turned on, encrypts HTML and JS from the web server on each visit. I cite that feature set from https://docs.waf.chaitin.com/en/home rather than assuming extra homelab plugins.
That scope also tells me what not to expect. The configuration guide says SafeLine is developed on nginx and acts as an HTTP and HTTPS reverse proxy: it receives traffic for the original site, cleans malicious traffic, and forwards the rest to the upstream application, as described at https://docs.waf.chaitin.com/en/GetStarted/AddApplication. A database port or an SSH listener is not that kind of application. Putting a WAF hostname in front of them is not a documented protection path, so I leave them off this design.
Before I move a self-hosted service, I run a short go or no-go list.
The app must be reachable as a web origin. In the console, Add Application asks for a domain, hostname, or IP, a listen port such as 80 or 443, and an upstream address. HTTPS apps need the SSL option checked. After saving, the domain must resolve to the IP of the SafeLine server. If I cannot make that DNS change, I do not pretend the app is protected.
The host must meet the install floor in https://docs.waf.chaitin.com/en/GetStarted/Deploy. That guide requires Linux, x86_64 or arm64, Docker 20.10.14 or above, Docker Compose 2.0.0 or above, and at least 1 CPU core, 1 GB of memory, and 5 GB of disk. The CPU must support ssse3. I confirm those facts with the documented commands: uname -m, docker version, docker compose version, cat /proc/cpuinfo | grep "processor", free -h, df -h, and lscpu | grep ssse3. A homelab node that fails any line is not a candidate, even if the web app itself is small.
Architecture has a license constraint I do not skip. For ARM, the guide sets ARCH_SUFFIX to -arm and uses the ARM Postgres image. It also states that SafeLine on ARM requires a Pro license to work properly, and that the Personal Edition is not supported on ARM. An ARM box can look ideal for a quiet homelab and still be the wrong edition.
Release choice is part of the same checklist. Setting RELEASE to -lts selects the LTS build, but the deploy guide says the LTS version will no longer be maintained starting from 9.1.0-LTS on 14 August 2025, and it strongly recommends upgrading to the latest version. I stay on the current release unless I have a concrete reason not to.
The recommended install is the automated English command from that same deploy page, and it needs root: bash -c "$(curl -fsSLk https://waf.chaitin.com/release/latest/manager.sh)" -- --en. Manual setup is also documented: create /data/safeline with at least 5 GB free, download the compose file, write .env, generate a 64-character hex detector management token, a 64-character hex management internal token, and a 16-character alphanumeric detector AES key, lock down permissions, then start with docker compose up -d. The console opens at https://<safeline-ip>:9443/. The initial administrator account comes from docker exec safeline-mgt resetadmin, and the printed username and password have to be saved then. The deploy page remains the source for SAFELINE_DIR, IMAGE_TAG, MGT_PORT, POSTGRES_PASSWORD, SUBNET_PREFIX, and the remaining variables.
Once the console is up, I add one application, point DNS at the SafeLine host, and test with the sample requests in the application guide: a SQL injection query string, an XSS payload, a path traversal payload, a code injection payload, and an XXE payload, with my domain in place of the example host. A blocking page means the request was stopped. I then open the attack list and click detail so the event is confirmed in the console, not only in the browser.
Published evaluation numbers are a policy warning, not a promise about my apps. On 33,669 samples, https://docs.waf.chaitin.com/en/home reports SafeLine Balance at 71.65 percent detection, 0.07 percent false positives, and 99.45 percent accuracy, and SafeLine Strict at 76.17 percent detection, 0.22 percent false positives, and 99.38 percent accuracy. Strict handling detects more and also raises the false-positive figure. After I enable stricter handling, I retest ordinary actions such as login and upload before I call the site done. The docs call the product production-ready; I still watch the first real clients.
I also keep the management plane boring. MGT_PORT defaults to 9443 in the sample environment, and MGT_PROXY is only for extra proxy layers in front of the console. It should stay at 0 unless I am actually configuring that proxy. If I retire the install, the documented path is to enter the SafeLine directory, run docker compose down, and remove that directory. Community support is Discord, including the #FAQ channel, plus GitHub issues, as noted at https://docs.waf.chaitin.com/en/home.
The decision is narrow. Use this WAF when a self-hosted web service must be reached from outside, when DNS can target the reverse proxy, and when the host matches the documented platform rules. Do not use it as a reason to publish services that should stay private, and do not describe it as an integration with a specific tunnel, panel, or orchestrator. The supported path is the one in the application guide: domain, port, upstream, and a domain that resolves to SafeLine.
Which self-hosted services should sit behind a WAF?
Only web apps you can publish as HTTP or HTTPS. SafeLine receives traffic for the original site, cleans malicious requests, and forwards the rest to the upstream, which is the model in https://docs.waf.chaitin.com/en/GetStarted/AddApplication. Non-web listeners are outside that guide.
Is a small homelab host enough?
The documented minimum is 1 CPU core, 1 GB of memory, and 5 GB of disk, on Linux with Docker 20.10.14 or newer, Docker Compose 2.0.0 or newer, and a CPU with ssse3, per https://docs.waf.chaitin.com/en/GetStarted/Deploy. ARM also requires a Pro license. The Personal Edition is not supported on ARM.
What do I enter for one public site?
Add an application with the domain, hostname, or IP, the listen port, and the upstream address. Check SSL for HTTPS. Resolve that domain to the SafeLine server IP, as described at https://docs.waf.chaitin.com/en/GetStarted/AddApplication. Rate limiting, CAPTCHA, authentication challenge, and dynamic HTML or JS encryption are separate controls from https://docs.waf.chaitin.com/en/home.
How can I verify that a probe was blocked?
Send the documented SQL injection, XSS, path traversal, code injection, and XXE examples to your own domain. A blocking page means the defense fired. Open the attack list and click detail to confirm the record.
Does this replace private networking or app login?
No. It filters traffic for web apps you choose to expose. It does not patch the upstream or justify publishing a service that should remain private. If you remove the install, use docker compose down and delete the install directory, following https://docs.waf.chaitin.com/en/GetStarted/Deploy.
SafeLine has surpassed 700,000 installations worldwide as of September 30, 2026. SafeLine Pro annual promotional pricing is $650-$880, compared with the regular $1,000 per year.