Standardize at fleet scale
Turn one approved golden standard into controlled work across hundreds or thousands of devices.
Network Automation + Always-On RCA
Automate thousands of network devices. Simply. Safely.
Netcode turns your golden standards into exact plans, dry-runs changes before production, rolls them out across multi-vendor fleets, verifies every device and keeps rollback ready.
When automation or monitoring finds a problem, Rez investigates like an engineer on your team. It works read-only, recommends the fix and returns it to Netcode for human approval.
Golden configuration
Dry-run before production
Controlled bulk rollout
Human-approved writes
See every change first
Preview the exact commands, affected devices, validation checks and rollback before production.
Roll out without guesswork
Start with a small device group, verify it live and expand only when the network proves healthy.
Give every exception to Rez
Automatically investigate failed checks and monitoring alerts without allowing RCA to write config.
Dashboards don't fix networks. Engineers do.
Netcode removes the repetitive work. Rez gives engineers a read-only investigation and a safe path from finding to approved action.
Automation Without The Software Project
Network as code should make engineers faster, not turn them into application developers.
Netcode gives network teams a simple path from live discovery to golden standards, exact change plans, dry-run, bulk rollout, verification and rollback. Use guided workflows, existing Ansible content, SSH or APIs without building the control plane yourself.
Automation teams struggle with
- One-off scripts that only their author understands
- No consistent golden configuration across vendors
- No safe way to preview and scale a bulk change
- Exceptions that send everyone back to the CLI
With Netcode + Rez
- Define the standard once and scope it to the right fleet
- Dry-run exact changes before any production write
- Verify each device group and isolate exceptions
- Let Rez diagnose failures and return an approved fix
Simple, Safe Fleet Automation
From golden standard to verified network in one operating workflow.
Netcode handles the expected work at scale. Rez handles the exceptions. Your engineers keep control of every production decision.
Set the standard
Choose the approved configuration, software or policy outcome.
Preview everything
See scope, exact commands, checks and rollback. Dry-run where supported.
Start small, then scale
Prove the first devices and expand through controlled groups.
Let Rez handle failures
Failed verification opens a read-only, scoped investigation automatically.
Approve and continue
Review the fix, apply through Netcode and verify the fleet again.
Automated work. Human-approved change.Discovery, planning, validation and RCA can run automatically. Every production write still stops at your engineer.
What Teams Automate
Standardize the fleet. Modernize the network. Keep engineers out of repetitive toil.
Start with one high-value standard, then reuse the same safety, rollout, verification and RCA model across the rest of the network.
Golden configuration at fleet scale
Bring NTP, DNS, SNMP, logging, AAA, banners, routing policy and security standards into one approved baseline across vendors.
Business value: consistent operations across thousands of devices.Network software lifecycle
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.WAN, routing, QoS and firewall policy
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.Site, cloud and data-center migration
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.Continuous compliance and drift recovery
Compare approved standards to live state, identify meaningful drift and create targeted remediation plans.
Business value: keep the network standardized after the project ends.Alert-to-remediation operations
Let Rez investigate automation failures or monitoring alerts, recommend a scoped fix and return it to Netcode for approval.
Business value: turn ticket queues into engineer-ready actions.See Netcode + Rez In Action
Watch bulk automation meet a real exception and keep moving safely.
See Netcode plan and roll out a fleet change, Rez investigate the failed check read-only, and an engineer approve the scoped remediation before the rollout resumes.
Run this workflow on your networkOne Platform, Two Clear Jobs
Netcode automates the fleet. Rez investigates what does not go as planned.
Both use the same discovered inventory, topology, device identity and local access boundary, so engineers never rebuild context between automation and troubleshooting.
NFleet automation
Netcode Automation
Makes network-as-code accessible to operations teams: define the standard, preview every change, roll out safely and prove the outcome.
- Golden configuration and bulk change
- Dry-run, first-device proof and controlled groups
- Human approval, verification and rollback
RAlways-on RCA
Rez Diagnostics
Receives failed checks, monitoring alerts or engineer questions, investigates live read-only and returns the recommended action.
- SolarWinds, ThousandEyes and Slack entry points
- Live SSH/API evidence and topology context
- Netcode remediation draft, never a direct write
>_Human operations
Netcode Shell
A full network terminal through the local runner, with saved sessions and a path from one-off work into repeatable automation.
- Interactive multi-vendor SSH
- Searchable session history
- Transcript-to-workflow handoff
Under the Hood / How Network Automation Works
The automation logic is simple: compare intended state to live state, then apply only what is proven safe.
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.
Netcode automation is not template push. It is intent - plan - validation - controlled execution - verification - drift control.
Live State
Interfaces, VLANs, BGP neighbors, routes, ACLs, NTP, SNMP, firmware, interface state.
Intended State
Approved NTP servers, VLAN standards, interface roles, routing peers, ACL rules.
Delta Plan
Devices affected, commands to add, commands to remove, rollback commands, risk summary.
Git Branch + Policy Gate
Each change is isolated, reviewed, checked, and blocked before execution if unsafe.
Dry-run / Canary
Candidate config, device syntax check, first-batch canary, and no-commit validation where supported.
Verify Actual State
NTP peers active, VLAN present, BGP session established, route installed, ACL ordered correctly.
Git Rollback + Drift Watch
Rollback to previous approved intent, validate reverse plan, apply through the same gates, and monitor drift.
Product Modules
Everything needed to move from scripts to governed NetDevOps.
Change Workspace
One guided workspace for intent, plan, validation, dry-run, apply, verify, rollback, and drift.
Bulk Change Planner
Select device groups by site, role, vendor, tag, or source-of-truth query. Plan one change across many devices.
Command Preview
Show exact generated commands and rollback commands before anything touches a device.
Git Workflow
Create review branches, commit generated artifacts, review diffs, merge approved intent, and roll back by reverting Git state.
Policy Gates
Block unsafe changes before apply using device groups, command patterns, maintenance windows, approvals, and rollback requirements.
Canary and Batch Apply
Apply to a small canary first, verify, then promote in controlled batches with automatic stop conditions.
Drift Watch
Continuously compare intended state to live state and create remediation plans when drift appears.
Netcode Shell
Open full live SSH sessions through the local runner with transcripts, before/after evidence, optional ticket attachment, and runner-side credentials.
Workflow Packs
Start with guided OS upgrade campaigns, then add golden baseline, VLAN rollout, interface standards, BGP neighbor updates, ACL cleanup, and drift checks.
Netcode Shell
A real network CLI, connected to the automation loop.
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.
Credentials stay local
Device credentials resolve on the customer-side runner, not in the browser and not in the control plane.
Full live CLI
Engineers can troubleshoot and configure from the shell. The human at the keyboard is the approval for this interactive path.
Every session is useful later
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 · Region 3
Runner customer-side
Mode full live SSH
Transcript recording
Evidence before/after diff
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
Every change has a branch. Every rollback has a known previous state.
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.
- A change branch isolates every network change.
- The plan shows exact intended delta.
- Policy checks run before apply.
- Canary result is committed back to the branch.
- Merge means approved intent.
- Drift watch compares live state to approved intent.
main
change/region3-app-segmentation-2048
intent.yaml
plan.md
commands.txt
rollback.txt
validation.md
canary-result.md
verify.md
Git Rollback Panel
Rollback CHG-2048
- Previous approved state
- main@8f31a2
- Current branch
- change/region3-app-segmentation-2048
- Rollback action
- revert app segment, route policy, and firewall object references
- Rollback commands
- 384 generated
- Validation
- Passed
- Status
- ready for rollback canary
Rez · The Always-On Network Engineer
Alerts arrive. Automation fails. Rez starts the investigation.
Rez receives failed Netcode checks, SolarWinds or ThousandEyes alerts, and questions from Slack. It resolves the affected site and dependencies, gathers fresh SSH/API evidence and performs scoped triage like an engineer on your team.
Always availableAutomation verification, monitoring webhook or engineer request can start the same investigation.
Read-only by designRez may inspect live state and validate a hypothesis. It cannot apply configuration.
Closes the work loopA confirmed recommendation becomes a Netcode draft. A human reviews and approves every write.
SWSolarWinds alert
TEThousandEyes alert
NNetcode failed check
SSlack
TTeams · planned
00:00
Verification failedBranch-EDGE-03 WAN routing check failed after the first-device upgrade
triage started00:06
Site and dependency context resolvedBranch-EDGE-03 → WAN → Edge-FW-01 → application
complete00:19
Live read-only validationSoftware and uplink are healthy; the approved WAN BGP neighbor is absent
confirmed00:24
Recommended action preparedRestore the approved BGP neighbor on Branch-EDGE-03 and rerun routing verification
readyRez conclusionAutomation exception isolated to one missing WAN neighbor configuration
Netcode handoffDraft created · exact commands + rollback · awaiting human approval
Multi-Vendor By Design
Automate and troubleshoot the network you already own.
Rezonance normalizes multi-vendor inventory and live state while preserving vendor-specific commands, APIs and evidence. Keep using existing Ansible playbooks, scripts, SSH and APIs inside a safer fleet workflow.
Adapter depth and write support vary by platform and workflow. Pilot scope is agreed and validated before production use.
CiscoAristaFortinetPalo AltoJuniperArubaNokiaHuawei
SSHREST APIsAnsibleGitSolarWindsThousandEyesSlack
Safety And Security
Automate the work without surrendering control of the network.
Outbound-only customer runner
The Windows or Linux runner opens the connection to Rezonance and resolves device credentials inside your environment.
RCA cannot apply configuration
Rez has a separate read action family, approved command filters and no path to Netcode's write actions.
No unattended production write
Exact preview, policy checks, first-device proof and optional two-person approval sit before bulk execution.
Rollback is part of every plan
Commands, verification, approvals, transcripts and reverse actions remain attached to the governed change record.
Every action leaves a record
Device commands, live results, approvals, automation stages and Rez findings are retained for review.
Protect sensitive identifiers
Cryptographic anonymization can protect addresses and identifiers before analysis while preserving network relationships.
Start Where You Are
Start locally, automate one fleet standard, then expand.
Learn the operating model
Free
Local examples, Netcode Shell and sample workflows for engineers evaluating the platform.
Request Community accessAutomate one real workflow
$99/month
Five workflow packs, up to 50 devices, guided planning, verification and limited Rez Diagnostics.
Request Starter accessAutomate one fleet standard
Scoped
Connect a representative device group and one alert source. Prove planning, rollout, verification and Rez exception handling.
Book the pilotFleet Automation + Always-On RCA Pilot
Automate one network standard. Let Rez handle every exception.
Choose a golden configuration, software lifecycle or network policy workflow. We will scope it across a representative fleet, dry-run the exact changes, execute a controlled rollout and connect Rez to failed checks or one monitoring source.
1 fleet standard100-500 representative devices1 monitoring or Slack entry point