head to head · open source

frp vs node-dns

frp has 110,686 GitHub stars, 15,330 forks, 48 open issues and last shipped 11 days ago. node-dns has 591 stars, 80 forks, 1 open issues and last shipped 5 days ago. frp leads on adoption by 18,629% (110,686 vs 591 stars). frp is written in Go under Apache-2.0; node-dns is written in JavaScript under MIT. frp has attracted 14% as many forks as stars, node-dns 14%. node-dns 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.

frp ★ 111K node-dns ★ 591 category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

frp node-dns
GitHub stars ★ 111K ★ 591
License Apache-2.0 MIT
Written in Go JavaScript
Last push 2026-11-10 2026-11-16
Forks ⑂ 15K ⑂ 80
Self-hosting Yes Yes
Data ownership Your server Your server

pick frp if

  • You weight community size — 111K stars and counting
  • You want the Apache-2.0 license terms
  • Your stack matches Go
  • You value the larger contributor base for long-term maintenance

full frp profile →

pick node-dns if

  • You want the node-dns feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches JavaScript
  • You evaluated both and node-dns fits your workflow better

full node-dns profile →

About frp

frp README 中文文档 Sponsors frp is an open source project with its ongoing development made possible entirely by the support of our awesome sponsors. If you'd like to join them, please consider sponsoring frp's development. Gold Sponsors High performance residential and ISP proxies for developers 90M+ residential IPs worldwide. Rotating IPs, sticky sessions, and traffic that never expires. From $0.55/GB. Use RAPID10 for 10% off. Try it for free. The complete IDE crafted for professional Go developers The sovereign cloud that puts you in control An open source, self hosted alternative to public clouds, built for…

read the full frp overview →

About node-dns

dns2 ![NPM version][npm img] [![Build Status][ci img]][ci url] A DNS Server and Client Implementation in Pure JavaScript with no dependencies. Features Server and Client Lot of Type Supported Extremely lightweight DNS over UDP, TCP, HTTPS Supported Installation DNS Client (default UDP) Lookup any records available for the domain lsong.org . DNS client will use UDP by default. The high level DNS class exposes convenience methods for common record types: For any record type not listed above, use dns.resolve(domain, 'TYPE') directly. Every name server is queried in parallel and the first successful reply wins. If…

read the full node-dns 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 frp or node-dns more popular?

frp has 110,686 GitHub stars and node-dns has 591. frp has the larger community by that measure.

Are frp and node-dns free?

Both are open source. frp is licensed under Apache-2.0 and node-dns under MIT. Neither carries a licence fee.

What is the difference between frp and node-dns?

frp is written in Go and node-dns in JavaScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, frp or node-dns?

Choose frp if you want the larger community (110,686 stars) or its Apache-2.0 licence terms. Choose node-dns if its feature set, stack or MIT licence fits better. Both are self-hostable.