head to head · open source
AdGuardHome vs xfrpc
AdGuardHome has 37,680 GitHub stars, 2,560 forks, 1,253 open issues and last shipped 3 days ago. xfrpc has 842 stars, 127 forks, 30 open issues and last shipped 2 months ago. AdGuardHome leads on adoption by 4,375% (37,680 vs 842 stars). AdGuardHome is written in TypeScript under GPL-3.0; xfrpc is written in C under GPL-3.0. AdGuardHome has attracted 7% as many forks as stars, xfrpc 15%. AdGuardHome was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| AdGuardHome | xfrpc | |
|---|---|---|
| GitHub stars | ★ 38K | ★ 842 |
| License | GPL-3.0 | GPL-3.0 |
| Written in | TypeScript | C |
| Last push | 2026-10-23 | 2026-09-08 |
| Forks | ⑂ 2.6K | ⑂ 127 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick AdGuardHome if
- You weight community size — 38K stars and counting
- You want the GPL-3.0 license terms
- Your stack matches TypeScript
- You value the larger contributor base for long-term maintenance
pick xfrpc if
- You want the xfrpc feature set and don't need the biggest community
- You prefer the GPL-3.0 license terms
- Your stack matches C
- You evaluated both and xfrpc fits your workflow better
About AdGuardHome
Privacy protection center for you and your devices Free and open source, powerful network wide ads & trackers blocking DNS server. AdGuard.com Wiki Reddit Twitter Telegram AdGuard Home is a network wide software for blocking ads and tracking. After you set it up, it'll cover ALL your home devices, and you don't need any client side software for that. It operates as a DNS server that re routes tracking domains to a “black hole”, thus preventing your devices from connecting to those servers. It's based on software we use for our public [AdGuard DNS] servers, and both share a lot of code. [AdGuard DNS]: Getting…
read the full AdGuardHome overview →
About xfrpc
What is xfrpc The xfrpc project is an implementation of frp client written in C language for OpenWRT and IOT system. The main motivation of this project is to provide a lightweight solution for devices with limited resources such as OpenWRT devices which often have limited ROM and RAM space. The project aims to provide a frp client that uses less space and memory than other available options. Development Status xfrpc partially compitable with latest frp release feature, It targets to fully compatible with latest frp release. the following table is detail compatible feature (vs official frpc / frp v0.71)…
read the full xfrpc overview →
More in Infrastructure & Operations
Related comparisons
More Networking & Connectivity projects
Compare either of these against the rest of the Networking & Connectivity field.
Frequently asked questions
Is AdGuardHome or xfrpc more popular?
AdGuardHome has 37,680 GitHub stars and xfrpc has 842. AdGuardHome has the larger community by that measure.
Are AdGuardHome and xfrpc free?
Both are open source. AdGuardHome is licensed under GPL-3.0 and xfrpc under GPL-3.0. Neither carries a licence fee.
What is the difference between AdGuardHome and xfrpc?
AdGuardHome is written in TypeScript and xfrpc in C. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, AdGuardHome or xfrpc?
Choose AdGuardHome if you want the larger community (37,680 stars) or its GPL-3.0 licence terms. Choose xfrpc if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.