Netcode by Rez helps network teams move from scripts and CLI changes to governed automation: source-of-truth cleanup, workflow automation, validation, drift checks, and Rez RCA when live troubleshooting is needed.
Start with one workflow. Prove it. Then expand to validation, drift, RCA, firewall/NAT, and SD-WAN operations.
We are approving early access manually while the public license flow is finished. If you want to test Rez in your own lab, send us your details and we will follow up.
Windows build · read-only posture · manual early access.
Monitoring says something broke. The bridge call asks why. Engineers jump between CLI sessions, firewall policy, SD-WAN dashboards, routing tables, packet captures, and vendor tools. The real work is not seeing the alert; it is proving what caused it.
The agent gathers read-only facts. The validation layer checks whether those facts actually explain the incident. If the evidence is weak, Rez says so.
Rez reads device and API evidence in read-only mode — pulling the same facts your senior engineer would check first.
Validation engines check protocol, config, forwarding, firewall, NAT, VPN, and SD-WAN facts so downstream symptoms do not get promoted as the root cause.
Rez returns the root cause, the evidence behind it, confidence, and the competing explanations it rejected.
You can try Rez without touching production. For customer pilots, we first confirm the vendor, topology, and incident type fit the coverage we can validate today.
A full Rez UI session against a live Arista incident lab. No production credentials — just watch Rez investigate and prove a root cause end to end.
Try Rez ArenaBring a short incident brief: vendor mix, topology shape, symptom, and what read-only access or lab replay is possible. We will tell you if it fits current validated coverage to validate automating end-to-end incident triage.
Scope My PilotWhen you're ready, grant read-only SSH/API access for actual-path RCA against your real network — allowlisted and fully auditable.
Talk About Live RCAExample from a validated routing-policy scenario: the session is established, but policy suppresses the prefixes users need.
Store users cannot reach DC app prefixes 10.20.0.0/24 and 10.30.0.0/24.
read-onlyestablishedmissingDENY_HQ_OUT outCP_ROUTE_FILTEREDGive every tier the evidence a senior engineer would collect — without putting your best person on every incident.
Rez investigates read-only evidence and only promotes findings that the validation layer can support.
Control matters more than speed. Rez is designed for read-only access, auditability, and clear boundaries.
Designed for enterprise assurance: audit logging, data isolation, encryption, RBAC, and a self-hosted deployment path. Arena uses a live isolated lab; customer evidence review is handled through a guided pilot until self-serve retention controls are deployed.
Read Security & TrustUse Community for labs, start the $99 Starter Pack for one team workflow, or book a focused Network Automation Pilot.
| Plan | Price | Best for | Included |
|---|---|---|---|
| Community Version | Free | Individual engineers, labs, and learning | Local examples, starter workflow templates, community support, and a practical path into Netcode automation. |
| Starter Pack Popular | $99/mo | One small team starting with one workflow | Guided Netcode workflows, basic validation, local runs, starter templates, and limited Rez RCA usage for troubleshooting. |
| Network Automation Pilot | Scoped | Team with a real workflow to automate | Founder-led pilot for source-of-truth cleanup, intent modeling, workflow automation, validation, drift checks, and Rez RCA when checks fail. |
| Team / MSP | Contact for more information | Production NOC / MSP | Client workspaces, SSO, private deployment, Digital Twin, Packet Analysis, Slack/Teams integration, Change Assessment, and full Network Agentic capabilities. |
Production pricing is tied to investigation volume, deployment model, and support needs.
Great tools already answer "what exists" and "what changed." Rez answers the bridge-call question: why is this incident happening now?
| Buyer question | Better fit |
|---|---|
| What devices and paths exist? | IP Fabric / Forward Networks / digital-twin tools |
| Will this change break policy? | Forward / network assurance tools |
| What changed in traffic? | Kentik / flow observability |
| Why is this incident happening now, and what evidence can I send? | Rez |
Use the Community version, start the $99 Starter Pack, or scope a focused Network Automation Pilot against your own environment.