Map the write paths.
Audit every role.
Pathix builds one graph of your Dynamics 365 and Dataverse environment, deterministic at its core: what writes every field, what each plugin is built to do, who can touch what. Whether a number moved and you need to trace it, or you're scoping a migration, the answer starts with the same map.
What do you want to do with it?
Pick the work in front of you. Every door draws from the same graph; the difference is the job, and the words for it.
Answer the questions you get every day, in seconds.
- What changed since the last scan, even what you didn't change
- Who can really write this field
- What writes and reads a column, both directions
- Field-level security gaps
Change a table without breaking production.
- Everything bound to a table, in one call
- Cascade blast radius before you touch it
- Plugin and flow disposition
- A sequenced, reversible migration plan
Make your environment safe for agents to rebuild.
- The Pathix MCP, callable by any agent
- AI-derived edges and plain-English narration
- Ground truth for agent-built custom UIs
- The road to headless Dynamics
Find the security risk in your config, and prove it's handled.
- Privilege exposure: roles shared across humans and integrations
- Over-broad and write-capable grants, surfaced and ranked
- Every finding mapped to a control and tracked to mitigated
- A new-since-last-scan delta on every finding type
AI is optional and off by default. How Pathix uses AI →
Severity, salience, and confidence stay on separate axes.
Most tools collapse everything into one number. Pathix keeps three questions apart: how severe a security finding is (severity), how prominent a field or component is in your dependency graph (salience), and how each edge was established (confidence). Severity and salience are ranked in separate lanes that never merge; confidence rides every row. Blend them into one score and all three read wrong.
The security verdict
A deterministic check that fired, ranked Critical to Info. Findings only. Salience never enters this ordering.
Graph prominence, 0 to 100
How many things write a field, whether it is sensitive, whether unverified edges touch it, whether it sits next to a finding. It ranks what is noisy, not what is risky. A low score is not a safety verdict.
How Pathix knows each edge
Declared, pinned by platform structure. Parsed, resolved from the component logic. AI-derived, an evidence-coupled reading of your own plugin code that never overrides a deterministic edge.
“Two axes, never merged into one list. Severity is the security verdict (findings only). Salience is computed graph prominence: noisiest first, not a risk ranking; a low salience score is not a safety verdict. Confidence rides every row as its own dimension.”
Shown on the Pathix console.
One place for every environment.
Every scan rolls up into one console. Findings ranked by severity and hotspots ranked by salience sit side by side but never blend: the riskiest finding and the top hotspot each get their own spotlight. You also see what changed since the last scan and an honest read on coverage and blind spots. The same graph the doors above draw from, in the view you open first.
Your edge on every engagement.
Land a fast, paid assessment, then bid the migration fixed-price with the discovery risk measured instead of guessed, then stay on for delivery and managed services. Pathix gets you in the door and keeps you on the account.
Land the assessment
A low-risk, high-margin first sale that maps the environment in hours.
Bid fixed-price
The big unknown measured up front, so you quote the migration without padding.
Keep the account
Pathix stays on through delivery and managed services.
Self-hosted, read-only, metadata-only.
The boundaries are architectural, not promises. Deploy it in your own tenant, read the schema yourself, and check the exact read-only role before you grant it.
In your own Azure
Deploys into the customer's own subscription from a Bicep template and a guided wizard. Nothing about running it requires data to leave the tenant.
Read-only, metadata-only
A read-only application user. Pathix reads schema, registrations, and definitions, and never stores, transmits, or analyzes your business record values.
The AI tier holds the same line
Turn AI on with your own key and the metadata-only boundary still applies. Record values stay out of the AI path too.
See what Pathix finds in a real environment.
A 30-minute walkthrough on a pre-scanned demo environment. No access to your tenant, nothing to install. Bring the questions your current tools can't answer.