Alternatives
Products that do what FwChange does
Stop managing firewall rules in spreadsheets
- 1
- 2
- 3LP
OP here. I built this because I recently caught myself almost pasting a block of logs containing AWS keys into Claude. The Problem: I need the reasoning capabilities of cloud models (GPT/Claude/Gemini), but I can't trust myself not to accidentally leak PII or secrets. The Solution: A Chrome extension that acts as a local middleware. It intercepts the prompt and runs a local BERT model (via a Python FastAPI backend) to scrub names, emails, and keys before the request leaves the browser. A few notes up front (to set expectations clearly): Everything runs 100% locally. Regex detection…
Dec 2025 · github.com
- 4DJ
2020 · github.com
- 5SF
2015 · github.com
- 6CE
We just open-sourced CargoWall - a lightweight eBPF firewall for GitHub Actions. We originally built it to stop LLM agents from connecting to untrusted domains. After recent GitHub Actions supply chain compromises like the Trivy attack, we realized it'd work well for blocking untrusted connections from CI runners too. It uses iptables DNAT to redirect all outbound port 53 traffic to a local DNS proxy, which checks each query against a hostname allowlist before forwarding. Resolved IPs from allowed responses are inserted into eBPF LPM trie maps, and a TC egress classifier attached to the…
Mar 2026 · github.com
- 7PA
PFELK is a pfSense/OPNsense firewall traffic visualization solution based on ELK stack. It is a highly customizable tool that let’s you have extensive insight into your network traffic. Key points: - pfSense/OPNsense support - openVPN support - pfSense/Suricata/Snort dashboards with interactive Maps support (MaxMind GeoIp fields, src -> dest locations, Heatmap, etc.) - deploy with ansible-playbook, docker or script. https://github.com/3ilson/pfelk
2020
- 8
- 9
- 10NL
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
- 11
- 12DA
2021 · relaypro-open.github.io
- 13RE
2016 · radiosilenceapp.com
- 14AF
2018 · github.com
- 15
- 16OS
Hey Everyone! Avi and I (in the current YC S25 Batch) noticed how fragmented crypto compliance is with rules changing constantly, vary by region, and force developers and legal teams into a scramble. So we hacked together a prototype framework that generates a “guardrail” smart contract which: - Hooks into your KYC provider - Enforces rules defined a simple compliance.yaml file - Automatically blocks users you can't legally serve When regulations shift (new blocked country, updated KYC threshold, etc.), just update your YAML and redeploy with no smart contract rewrites. Audit prep also…
2025 · github.com
- 17DE
2020 · blog.zeet.co
- 18
- 19
- 20
- 21
- 22
- 23
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →