Alternatives
Products that do what VeloGuardian does
Your Network, Your Shield
- 1

- 2

- 3

- 4

- 5DA
Tired of companies snooping through your DNS traffic? Don't you wish you could get advertisements with your DNS records? Today we're introducing the innovative, privacy-focused, ad-supported DNS resolver - DN$! Traditional DNS resolvers provided by your internet service provider, cloudflare, or google could be tracking your internet activity and selling it to third-party data vendors. We at DN$ want to fix that and cut out these nefarious actors (until we've amassed a critical number of users to exploit). In order to support such a radically new business model, our service needs to serve…
2024 · github.com
- 6

- 7

- 8
- 9

- 10

- 11RT
Every privacy-focused DNS service requires an account: NextDNS, Cloudflare for Families, Apple's iCloud Private Relay (paid, iOS-only). The protocol that doesn’t require one - ODoH - had basically one well-known public relay operator (Frank Denis on Fastly Compute, default in dnscrypt-proxy). I built a second one and the client to talk to it.
May 2026 · numa.rs
- 12DA
2020 · github.com
- 13AV
2014 · tinfoilsecurity.com
- 14NA
I'm the founder at Netrinos. I built a WireGuard-based mesh VPN because remote access has always been a pain. After years of SSH tunnels, IPsec headaches, and the ssh log horror movie, I wanted something simpler: install, sign in, get work done. Netrinos creates a LAN-like overlay network across your devices. Connections are direct P2P via WireGuard, with no central server routing traffic. Each device gets a stable IP and DNS name (pc.you.netrinos.com). When direct connections fail, they fall back to a relay server that's still encrypted end-to-end. We can't see your traffic. The most…
Dec 2025 · netrinos.com
- 15

- 16NL
To power the firewalling for our agents so that they couldn't contact arbitrary services, I build netfence. It's like Envoy but for eBPF filters. It allows you to define different DNS-based rules that are resolved in a local daemon to IPs, then pushed to the eBPF filter to allow traffic. By doing it this way, we can still allow DNS-defined rules, but prevent contacting random IPs. There's also no network performance penalty, since it's just DNS lookups and eBPF filters referencing memory. It also means you don't have to tamper with the base image, which the agent could potentially manipulate…
Jan 2026 · github.com
- 17

- 18

- 19

- 20OA
2021 · github.com
- 21

- 22

- 23

- 24

Ranked by how close each launch is in meaning, then by votes. Refine with a description →