NetConverter — by ValeronLabs LLC
Prepare a migration, translate supported configurations and inspect the findings before a network change. Deterministic checks decide the result. AI helps explain it. Your engineers own the cutover.
Planning a project? Estimate your scope or talk through your migration. Platform access is subject to account approval.
Explore the product
Select a step to see where the work happens, what you get and what needs your review.
01 / Start with evidence
Use a saved configuration or collect a selected device and its supporting evidence. Keep missing captures visible from the start.
02 / Understand the source
Inspect the selected scope and its relationships in Local. Workspace editing and migration preparation are part of the preview work.
03 / Move to the target
Choose your target and explicitly submit the configuration. Review generated output alongside the findings and any work that remains.
04 / Inspect the differences
Compare supported source and target behavior. Separate an unexpected exposure from an outage, translation change or unresolved assumption.
05 / Own the change
Resolve findings, validate the target and prepare rollback. Use the evidence to support your change process and sign-off.
Interactive product guide · illustrates the workflow, not a live job or service-health dashboard.
Inside the hosted platform
Quick Convert starts the migration. Jobs brings the result, warnings and reports together. AI Studio gives you a place to investigate what needs attention.
From result to review
Open a saved job to inspect its result, warnings and manual recreation steps. The evidence report separates the checks that ran from those that had nothing to verify.
Use the report and AI Studio together to investigate findings. Keep target-device validation and change approval in your engineering process.
See the current product update →
Inside the product / Local preview
NetConverter Local brings collection, inspection and preparation into an on-site Docker workspace. Cloud migration is a separate, explicit submission.
A result you can inspect
This ASA → PAN-OS example shows why a generated configuration is only part of the job. The Local verifier identifies exposure, outage, NAT and path differences, then leaves the decisions open for an engineer.
Checks, explained
Compare modeled access decisions between source and target. Review coverage and any constructs the model cannot resolve.
Check modeled address translation behavior. Device import and traffic testing still matter.
Identify modeled shadowing that can make a policy behave differently from its appearance.
Find broken or missing zone relationships that need attention before deployment. An explanation does not clear a blocking finding.
It is not certification of every vendor feature, a live dataplane test or approval to deploy. Unsupported features, missing captures and conditional behavior need explicit review. AI can explain findings and propose assistance; it cannot set the final pass/fail status or lift a blocked result.
Understand your validation results →Choose a supported path
Source support, target output and on-site collection are different capabilities. Confirm the vendor pair, software version, features and handoff format for your project.
See dated workspace captures, the current Windows preview status and the planned router and switch experience. Availability and verification vary by platform.
What’s available and what’s coming →Product update / September 28, 2026
New evidence workflows, migration improvements and a Local preview. Each update distinguishes what is available from what is still being tested.
Saved jobs, detailed findings and AI Studio make the result easier to investigate. Recent switch and firewall updates improve how supported source behavior is preserved.
Local development continues. API access has a defined scope, and MCP remains a controlled pilot.
Built around engineering review
Tell us the source, target and features that matter. We’ll help establish what can be translated, what needs more evidence and what stays in the engineer’s hands.