// Compare
ingressd vs frp.
frp is a fast reverse proxy: frps on a public server and frpc next to your services, set up with config files. ingressd covers the same ground and adds what frp leaves to you: certificates, failover across nodes, sign-in, a WAF and a management panel.
// Which to choose
Both are good at different things.
Pick the one that matches where you want your traffic to run.
Choose frp if
- You want a small, well-known tool and are happy editing config files.
- You need peer-to-peer modes such as XTCP.
- One public server is enough, and you handle TLS and auth yourself.
Choose ingressd if
- You want certificates issued and shared across nodes for you.
- You want several nodes with failover DNS.
- You want sign-in, a WAF and a browser panel without building them yourself.
// Side by side
The differences that matter.
Taken from the full comparison of ingressd with the alternatives.
| Feature | ingressd | frp |
|---|---|---|
| Public edge runs on | Your own VPS nodes | Your server |
| TLS for web apps ends at | Your node | Your server or your app |
| Open source | Node, edge and connector: Apache-2.0. The hosted panel is optional and proprietary. | Apache-2.0 |
| No inbound ports at the origin | Yes | Yes |
| HTTP and HTTPS apps | Yes | Yes |
| Public TCP | Yes | Yes |
| Public UDP (game servers, VoIP) | Yes | Yes |
| Your own domain | Yes | Yes |
| Failover across several edges | Yes: failover DNS across your nodes | No; load balancing across clients only |
| Sign-in in front of apps | Email code, Google, Microsoft, Discord, Steam or passkey | HTTP basic auth |
| Web application firewall | Coraza with the OWASP Core Rule Set, per app | No |
| Managed from | A free hosted panel, or one config file and the CLI | Config files, with a status dashboard |
| Cost | Free and open source; you pay for your VPS | Free; you pay for your server |
Checked against each product’s own docs in November 2026. Plans and features change; if something here is out of date, tell us on GitHub. Sources: frp on GitHub.