Built by operators, for operators
ispforge exists because running BGP policy across a real, multi-vendor network shouldn't mean maintaining the same intent by hand in four different CLIs.
The big suites are shaped for carriers
Small and mid-size ISPs run serious networks — multiple upstreams, IX fabrics, customer policy, IRR and RPKI obligations — usually with a small team and a pile of bespoke scripts. We wanted the routing-hygiene discipline of a large operator, in a tool a two-person NOC can actually run.
Policy once, filtering by default, diffs always
Policy should be defined once, in terms of intent, and rendered correctly for whatever hardware you happen to run. Filtering — IRR, RPKI, max-prefix, bogons — should be on by default, not a checklist you hope you remembered. And no change should ever reach a router without a diff you can read first.
If you run BGP on more than one router
Regional ISPs
Multiple upstreams, peering at one or more IXPs, customer downstreams with their own policy needs.
WISPs & edge operators
Running a mix of vendors — MikroTik, Junos, FRR — and wanting one consistent policy model across all of them.
Network engineers
Anyone who cares about routing hygiene, repeatable change, and not hand-editing the same filter in four places.
Running real production traffic — and shipping continuously
ispforge is built in the open by a team that runs its own network on it. New platforms, features, and integrations ship continuously. If you run BGP in production and want to shape where it goes, we'd genuinely like to hear from you.
ispforge. is a product of Kerfuffle, LLC · hello@ispforge.com