Network Automation + Closed-Loop Rez RCA
Netcode gives network engineers a guided way to standardize configurations, upgrade software, and deploy multi-vendor changes without building a complex automation framework.
Then the loop closes when something goes wrong. Netcode verifies the result; Rez investigates exceptions read-only, identifies the root cause, and prepares a scoped remediation plan for human approval and live re-verification.
Early users highlighted three capabilities working together: safe multi-device automation, a Digital Twin that makes the network understandable, and Rez investigating exceptions with live, read-only evidence.
Netcode made end-to-end automation feel practical. Engineers could review the exact change, test it safely, roll it out across devices, verify the result, and keep rollback and audit evidence in one workflow.
Retail customer · Network engineering
The Digital Twin was an incredible addition. It gave the team a clear view of sites, devices, links, and dependencies—and made both automation and troubleshooting easier to understand.
Financial-services customer · Network engineering
Rez did more than summarize an alert. It followed the topology, checked live device state read-only, separated the root cause from downstream symptoms, and prepared the next action for review in Netcode.
Early customer feedback · Network engineering
Feedback summaries are paraphrased from early customer conversations. Company names remain confidential pending approval.
An included site-aware Digital Twin for automation and troubleshooting.
See every device command, check, and rollback before production.
Continue only after live post-change checks pass.
Rez investigates read-only and returns the recommended fix.
Built For Network Engineers
Get Python-powered automation without building Ansible playbooks, scripts, inventory plumbing, approval logic, audit records, and rollback from scratch.
Choose a workflow, select devices by site, role, or vendor, review exact commands and rollback, test one device, then continue in controlled groups.
When a change fails or an alert arrives, Rez resolves the affected site and path, gathers live read-only evidence, and explains the actual root cause.
Need the CLI? Open a full multi-vendor SSH session through the local runner, keep the transcript, and turn repeated work into a reusable workflow.
See the closed loop in action
Watch Netcode plan and verify a multi-device change in the real product UI. When a campus fault appears, Rez investigates it read-only from the Ops Dashboard and returns a confirmed recommendation to Netcode for dry-run and human approval. The same walkthrough includes the shared Digital Twin and live Netcode Shell.
Meet Rez · Read-Only Network Troubleshooting
Rez is the troubleshooting engine inside Netcode. It starts when Netcode verification fails, when SolarWinds or another monitoring system sends an alert, or when an engineer asks from Ops Dashboard or Slack. Rez resolves the site and service path, runs fresh SSH/API checks, validates the root cause, and prepares a reviewed Netcode remediation draft. Rez never pushes configuration.
What Early Access Must Prove
Early-access programs measure these outcomes directly. Published results and quotations are attributed only with customer approval.
Verify the complete application path before the rollout continues beyond the first approved target group.
Investigate routing, SD-WAN, firewall policy, NAT, and return path from one exact flow instead of opening five consoles.
Stop on failed service verification, preserve untouched targets, and remediate only the dependency that failed.
Link manager jobs, device actions, approvals, Rez findings, verification, and rollback to one Rezonance change ID.
Automated Digital Twin
Discovery creates a site-aware model of devices, interfaces, links, BGP and OSPF neighbors, and service paths. Netcode uses it to scope changes; Rez uses it to troubleshoot failures. It is included with Rezonance, not sold as a separate topology add-on.
Group devices by site, role, vendor, and shared network identity.
Overlay physical, L2/LLDP, BGP, OSPF, and monitored application paths.
Launch SSH, scope a change, trace a flow, or start RCA from the same model.
Four High-Value Programs
Use one operating model for exact plans, first-device proof, verified rollout, rollback and read-only exception handling.
Bring NTP, DNS, SNMP, logging, AAA, routing policy and security standards into one approved multi-vendor baseline.
Business value: consistent operations across thousands of devices.Assess readiness, stage images, prove the first devices, verify routing and services after reboot, then continue in controlled groups.
Business value: complete more upgrades with less manual coordination.Standardize BGP, OSPF, SD-WAN, QoS, firewall objects, NAT and egress policy while validating application reachability.
Business value: move complex policy without losing service context.Model dependencies, generate exact deltas and move sites or applications in verified groups with rollback ready.
Business value: reduce migration time and isolate exceptions early.Under the Hood / How Network Automation Works
Netcode does not blindly push templates. It follows a deterministic automation loop: read live state, model intended state, calculate the delta, validate policy, dry-run or canary, apply through gates, verify actual state, and keep rollback tied to Git.
Interfaces, VLANs, BGP neighbors, routes, ACLs, NTP, SNMP, firmware, interface state.
Approved NTP servers, VLAN standards, interface roles, routing peers, ACL rules.
Devices affected, commands to add, commands to remove, rollback commands, risk summary.
Each change is isolated, reviewed, checked, and blocked before execution if unsafe.
Candidate config, device syntax check, first-batch canary, and no-commit validation where supported.
NTP peers active, VLAN present, BGP session established, route installed, ACL ordered correctly.
Rollback to previous approved intent, validate reverse plan, apply through the same gates, and monitor drift.
Product Modules
One guided workspace for intent, plan, validation, dry-run, apply, verify, rollback, and drift.
Select device groups by site, role, vendor, tag, or source-of-truth query. Plan one change across many devices.
Show exact generated commands and rollback commands before anything touches a device.
Create review branches, commit generated artifacts, review diffs, merge approved intent, and roll back by reverting Git state.
Block unsafe changes before apply using device groups, command patterns, maintenance windows, approvals, and rollback requirements.
Apply to a small canary first, verify, then promote in controlled batches with automatic stop conditions.
Continuously compare intended state to live state and create remediation plans when drift appears.
Open full live SSH sessions through the local runner with transcripts, before/after evidence, optional ticket attachment, and runner-side credentials.
Start with guided OS upgrade campaigns, then add golden baseline, VLAN rollout, interface standards, BGP neighbor updates, ACL cleanup, and drift checks.
Netcode Shell
Network engineers still need a full shell. Netcode Shell gives them one: live SSH through the customer-side runner, credentials kept local, every command recorded, and a clean path from an ad-hoc fix into governed automation when the work should be repeated.
Device credentials resolve on the customer-side runner, not in the browser and not in the control plane.
Engineers can troubleshoot and configure from the shell. The human at the keyboard is the approval for this interactive path.
Transcripts and before/after diffs can attach to a ticket, change, RCA, drift investigation, rollback, or approval record.
Session recording · optional ticket CHG-2048
Core-RTR-02# show bgp ipv4 unicast 10.204.210.0/24
BGP routing table entry for 10.204.210.0/24
Paths: 2 available, best #1
Community: region3-app-segment
Core-RTR-02# configure terminal
[live] config mode entered · transcript recording
Core-RTR-02(config)# route-map REGION3-EDGE permit 20
Core-RTR-02(config-route-map)# set local-preference 180
Core-RTR-02(config-route-map)# end
Core-RTR-02# show archive config differences
[diff] route-map REGION3-EDGE permit 20 addedNetDevOps Governance
Netcode uses Git as the system of record for network intent and generated artifacts. Engineers can review plans before apply, promote approved changes, and roll back by reverting to the last known good intent.
intent.yaml
plan.md
commands.txt
rollback.txt
validation.md
canary-result.md
verify.md
Git Rollback Panel
Multi-vendor platform
Use the right adapter for each platform while Netcode keeps planning, approval, verification, rollback and Rez diagnostics in one workflow.
Adapter depth and write support vary by workflow. Production scope is agreed before live use.
Security
The customer-side runner holds device access inside your network. Sensitive network identifiers are anonymized before the Rez reasoning layer, and production changes remain behind Netcode's human approval boundary.
Credentials, SSH/API access and raw device interaction stay customer-side.
Netcode governs change. Rez reasons over anonymized, read-only evidence.
IP addresses are AES-128 prefix-preserving tokenized. Hostnames and MAC addresses are mapped, and SNMP community strings are redacted before the reasoning layer.
The outbound-only Windows or Linux runner resolves device credentials locally. The cloud receives inventory facts and job results, not device passwords or keys.
Rez uses a separate read action family with command and pipe-filter allowlists. If its safety or runner path is unavailable, the read fails instead of opening a direct device path.
Netcode shows exact commands and rollback, validates the plan, proves the first device, and waits for a human before production execution.
Plans, commands, approvals, runner actions, verification, Shell transcripts, Rez findings and rollback remain linked to the same change record.
Customer network data is used for the active workflow or investigation, not to train foundation models.
Rez can investigate and recommend. It cannot apply configuration. Netcode can execute only through the governed change path.
Read Security & TrustStart Where You Are
Run locally with sample workflows. No hosted workspace or cloud device credentials required.
Five workflow packs, up to 50 devices, guided planning, verification and limited Rez Diagnostics.
Connect a representative device group and one alert source. Prove planning, rollout, verification and Rez exception handling.
Join design partner waitlistAccess is currently waitlist-only. Community evaluates the operating model, Starter proves controlled workflows, and production teams begin as design partners.
The Founding Team
The founding team brings hands-on network engineering and large-scale network operations experience to Rezonance. That operating perspective shaped a platform built around exact change plans, live verification, read-only RCA, rollback, and human approval.
Founder
Co-founder
Private Early Access
Tell us what you manage and where automation is painful. We are inviting a small number of network engineers to test Community, Starter, and production design-partner workflows before broader access opens.