What PathWise is
PathWise is an AI network and access troubleshooting engine. It reasons across the full access path, device to destination, and hands back an evidence-backed answer.
The problem it solves
A user cannot reach something: a site, a server, a shared drive, an internal app. Someone on the help desk has to work out which layer broke: DNS, routing, the firewall, the certificate, the app itself. That usually means bouncing between five consoles and running the same handful of checks by hand, one ticket at a time.
PathWise walks that same path in one pass and shows its work.
What it does
Point PathWise at a ticket. It runs the cheapest checks first, such as a DNS lookup or a ping, and keeps going deeper only as far as the evidence justifies. Each step is a probe: a small, targeted check with a real result attached.
From that evidence it builds a diagnosis: which layer broke, how confident it is, and what it could not test. It recommends a fix in plain language that a technician can act on or paste into a ticket.
It does not wait for a complete ticket before it starts working. If some details are missing, it runs what it can and reports at the confidence the evidence supports, then asks for whatever is still needed.
You work in PathWise's web interface. Sign in, paste the ticket into New Investigation, watch the checks stream live, and read the diagnosis, plain summary first with the technical detail one click deeper. Past investigations stay under History and can be reopened when new evidence arrives. Admins manage the model, users, modules, and the license from one Settings page.
The hard line: it never remediates
PathWise gathers evidence and recommends a fix. It never runs, applies, changes, or executes anything on the network or on a device, even if the operator tells it to. That capability is left out of the toolset by design, not switched off by a setting.
A human runs the fix. See Diagnose, never remediate for how that boundary is enforced and logged.
Who it is for
PathWise is built for the help desk and network teams who triage access tickets, and for the people who approve what runs on their infrastructure. It is self-hosted, vendor-neutral, and runs in your own environment.
Where to go next
- How it works: the probe-and-diagnose loop in more detail.
- Quick start: get PathWise running.
- The reasoning engine: which model does the reasoning, and how to choose one.
Under the hood technical detail
PathWise's safety boundary is enforced by an effect gate in code, below the reasoning step, so the model cannot bypass it by being asked to. Every operation it attempts is recorded in a persistent audit log, and modules that extend PathWise's reach are built to the Open Module Standard.