Closed-Loop Network Operations

Ship network change without turning exceptions into outages.

Rezonance gives multi-vendor network teams one operating loop for complex change: understand live state, plan the rollout, prove the first devices, verify every stage, and isolate failures before they spread.

Netcode executes the change. Rez Diagnostics explains the exceptions. Engineers approve every production write.

Vendor-neutral operations Human-approved writes Read-only RCA Credentials stay local
Regional Edge Modernization Illustrative campaign

CHG-4271 · Region 3

Routing, security and WAN policy convergence

Wave 7 of 12
2,480targets
2,117verified
11held for review
0promoted without proof
Campaign progression85% verified
ScopePlanFirst devicesVerified groupsClose
Route-policy standardizationVerified
Firewall egress and NAT alignmentVerified
SD-WAN and QoS policy migrationIn progress
Telemetry and compliance closeoutQueued
!
Exception isolated before wider rollout Branch-EDGE-03 passed routing checks but outbound NAT evidence is missing for the scoped flow. Rez opened a read-only investigation. The next device group remains paused.
Next actionReview scoped fix
01

Protect change windows

Prove a small first group and stop before a local exception becomes a fleet event.

02

Cut exception time

Move from console hopping to scoped, read-only diagnosis tied to the exact failed check.

03

Increase team capacity

Standardize repeatable work while engineers retain the decision to change production.

04

Keep what already works

Reuse SSH, APIs, Ansible, Git and service-management processes instead of replacing them.

The Operational Problem

The expensive part is not generating commands. It is controlling what happens next.

Large network changes stall because inventory is fragmented, pre-checks are inconsistent, failures arrive without context, and rollback depends on the engineer who built the script. Rezonance turns that fragmented work into one governed operating cycle.

Without a shared loop
  • Scripts, spreadsheets and terminals disagree
  • Failures surface after the blast radius expands
  • Engineers rebuild context under pressure
  • Rollback knowledge lives with one person
With Rezonance
  • Live state and intended outcome share one workspace
  • Each device group must prove health before promotion
  • Rez investigates only the failed dependency and flow
  • The approved change and rollback remain attached

The Rezonance Difference

The change does not end when the commands run.

Other automation tools can push configuration. Rezonance keeps operating through verification, failure isolation, remediation planning and approved recovery.

01

Understand

Discover live devices, topology, policy and dependencies.

02

Plan

Calculate exact scope, risk, commands and rollback.

03

Prove small

Run the first devices and verify the expected outcome.

04

Diagnose

If a check fails, Rez isolates the cause read-only.

05

Continue or recover

Approve the next group, a scoped fix, or rollback.

The machine closes the loop of work.The engineer closes the loop of decision. No production write bypasses human approval.

Enterprise Change Programs

Built for the network work that carries real business risk.

Start with a program that is already consuming change windows, senior engineers and operational trust. Rezonance turns it into a repeatable operating model.

Modernize

Regional edge transformation

Coordinate routing policy, SD-WAN, QoS, security and telemetry changes across sites without treating the network as one undifferentiated batch.

Outcome: faster modernization with contained blast radius.
Converge

Firewall and SD-WAN policy harmonization

Align path intent, egress policy, NAT behavior and application reachability across Fortinet, Palo Alto and routed WAN domains.

Outcome: fewer policy exceptions and cleaner cutovers.
Operate

Multi-vendor software lifecycle

Group mixed hardware by readiness, stage safely, verify routing and services after reboot, then stop or recover only affected cohorts.

Outcome: more fleet progress per maintenance window.
Integrate

M&A and data-center migration

Model overlapping networks, policy differences, route redistribution and phased cutovers before moving traffic between operating domains.

Outcome: migration decisions backed by live dependencies.
Govern

Continuous compliance and drift recovery

Compare approved intent to live state, isolate meaningful deviations and create scoped remediation without normalizing a failed scan as truth.

Outcome: less audit toil and fewer silent configuration gaps.
Recover

Incident-to-remediation operations

Start from an outage, let Rez identify the in-scope failed condition, then turn the confirmed finding into a reviewed Netcode change.

Outcome: shorter handoffs from diagnosis to safe action.

See The Loop Close

A rollout exception becomes a diagnosis, not a war room.

Watch Digital Twin context, Rez read-only diagnosis, a scoped remediation proposal, verified progression and ready rollback in one 82-second story.

Bring us your change scenario
82 seconds Digital Twin → Rez diagnosis → verified rollout → ready rollback

One Operations Platform

Automation, diagnostics and the engineer's terminal share the same network context.

Discover once. Use the same inventory, topology and device identity across planned changes, live investigations, drift checks and human operations.

NControlled change

Netcode Automation

Plans exact change scope, tests the first devices, verifies live outcomes and pauses before risk spreads.

  • Fleet campaigns and device groups
  • Human approval and two-person control
  • Recorded rollback and change history
RRead-only diagnosis

Rez Diagnostics

Investigates the exact site, dependency and flow that failed, then returns a typed remediation draft without writing configuration.

  • Live SSH and API evidence
  • Topology and operational baseline
  • Scoped handoff into Netcode
>_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
Shared foundationDiscovery + inventory + topology + live state
Customer boundaryLocal runner + local credentials
Existing ecosystemSSH + APIs + Ansible + Git + ITSM

Rez Diagnostics

Healthy adjacencies. Wrong traffic path. Rez finds the signal in the noise.

A remote site advertises a more-specific route that silently pulls half of a data-center subnet toward the wrong edge. BGP remains established, interfaces stay up and generic health dashboards look green.

QuestionWhy can Store 204 reach 10.20.0.200 but not 10.20.0.10?
Scoped finding10.20.0.0/25 from Store-01 overrides the intended DC /24 for the failed destination.
Next safe actionDraft a route-policy change for review. Do not touch healthy adjacencies.
Digital Twin · Incident INC-2048Read-only
SStore-204source
WWAN coreBGP healthy
DDC fabric10.20.0.0/24
!Store-01leaked /25
10.20.0.200   intended /24
10.20.0.10   shadowed by /25
Root cause isolatedMore-specific route shadow, not a BGP outageLive route evidence + expected origin + destination-specific path

Vendor-Neutral By Design

Build one operating model across the network you actually own.

Rezonance normalizes multi-vendor inventory and live state while preserving vendor-specific commands, APIs and operational evidence. Existing Ansible playbooks and scripts can remain part of the workflow.

Adapter depth and write support vary by platform and workflow. Pilot scope is agreed and validated before production use.

CiscoAristaFortinetPalo AltoJuniperArubaNokiaHuawei
SSHREST APIsAnsibleGitServiceNow

Enterprise Trust Boundary

Autonomy where it is safe. Human control where it matters.

Outbound only

Credentials remain inside your network

The Windows or Linux runner initiates outbound connectivity to the service. Device credentials are resolved locally.

Read-only

Diagnostics cannot apply configuration

Rez uses a separate read action family and returns findings or draft remediation, never a direct write.

Human approved

Every production change stops at a person

Policy, first-device proof and requester-not-approver controls sit in front of fleet execution.

Recoverable

Change and rollback travel together

Commands, verification, approvals and reverse actions remain attached to the same governed record.

Start Where You Are

Explore locally, automate one workflow, or prove a high-value program.

Community

Learn the operating model

Free

Local examples, Netcode Shell and sample workflows for engineers evaluating the platform.

Request Community access
Starter

Automate one real workflow

$99/month

One workspace, up to 25 devices, guided planning, verification and limited Rez Diagnostics.

Request Starter access

Design Partner Program

Bring us the change window your team dreads.

Give us one complex, multi-device program and a safe environment. We will model the blast radius, prove the first devices, show how failures are isolated, and leave every production decision with your engineers.

1 difficult change program1 customer-side runner1 measurable operating result
Bring us the change window your team dreads. Design the pilot Watch demo