Work with PathMRI
Three ways to work together: get your platform read properly, deliver PathMRI to the networks you look after, or build on top of it. All three start with the same conversation.
Three kinds of partnership
Vendors
You make a firewall, an NGFW or a cloud policy engine, and you want PathMRI to read it correctly rather than approximately.
What that takes is below — and it is not documentation.
Integrators and MSPs
You run other people's networks and need to prove connectivity — before a migration, after a change, or when an application team says "the firewall is blocking us" and the firewall team disagrees.
PathMRI is free and on-premise, so it can go into a client's environment without a licence conversation.
Builders
You want verification results inside your own pipeline or dashboard. Every screen in the console is built on a documented API, and API keys are first-class.
The API guide ships with every package.
What "supported" has to mean
Adding a vendor is not a matter of reading a manual and writing a parser. A policy engine only counts as supported once PathMRI reads it correctly — including the cases that are easy to get wrong.
Real equipment
A device or a cloud instance we can reach — physical, virtual or a trial tenant. A parser written from a manual alone is not enough to call a vendor supported.
The awkward cases
Not the happy path. Shadowed rules, ordering, NAT that changes the address the far end sees, a policy that says allow while the wire says no. That is where models are wrong.
A written record
Each vendor gets a document stating what is read, what is evaluated, and what is deliberately not asserted.
Already covered
If your platform is here, it is read and evaluated today. If it is not, that is the conversation to have.
| Category | Platforms |
|---|---|
| Firewall appliances | Cisco ASA · Cisco FTD / Firepower · Fortinet FortiGate · Palo Alto PAN-OS · Check Point (CloudGuard / Gaia) · Juniper SRX (Junos) · pfSense / OPNsense · VyOS |
| Cloud providers | Amazon Web Services — Security Groups, Network ACLs, AWS Network Firewall Microsoft Azure — Network Security Groups, Azure Firewall Google Cloud — VPC firewall rules |
| Container platforms | Kubernetes — NetworkPolicy, Calico, Cilium · Docker |
| Host firewalls | iptables · ufw · firewalld · Windows Firewall |
Getting in touch
Bring the platform, the access, and the cases you think will break it. That last one is the most useful thing in the conversation.