Sign in Get started

NetConverter Local / Product preview

Prepare locally.
Choose what goes next.

A Docker workspace on your own network for collecting, understanding and preparing configurations. Local analysis and hosted translation have distinct roles: you choose when to submit a supported migration to the server.

See availability ↓Discuss a Local evaluation →

Status reviewed September 28, 2026. Development preview; no general-release date announced here.

NetConverter Local 2.0.0 running on an on-site Docker appliance, showing firewall entry points and navigation
Captured September 28, 2026 from running Local 2.0.0. No configuration selected, no customer data shown, nothing masked. Visible platform cards are entry points, not proof that every feature or live collection path has passed acceptance.

One suite, two roles

Keep preparation close
to the network.

On your network

Collect vendor-native configurations and supporting captures. Inspect the selected device scope, explore relationships and prepare inputs in the local workspace. Offline analysis does not require a cloud migration job.

On the hosted platform

Explicitly submit supported migration work for translation and validation. Retrieve output and evidence for comparison and review. Local is not a fully offline copy of the hosted translation engine.

Optional model integrations are separate from core local analysis. Server-backed operations require network access and appropriate account permissions.

Availability / September 28, 2026

A clear view of what’s next.

Dated captures · 2.0.0

The Local workspace

The screenshots show a running 2.0.0 appliance and a saved ASA → PAN-OS verification example. This demonstrates those screens and that example; it is not blanket acceptance of every platform.

Windows preview · 2.0.6

Capture coverage and preparation

As of October 1, 2026, the Windows Docker preview is running 2.0.6 with capture-coverage and server-handoff improvements. Supported workflows were checked separately; missing evidence and unsupported migration features remain explicit. The screenshots below are from the earlier 2.0.0 build.

Planned

Router and switch workspaces

The Local home screen marks routers and switches as “Coming next.” Planned entry points are a direction, not a delivery date or a statement of current Local support.

Before wider release

Platform-by-platform acceptance

Collection, saved-config analysis, editing, server handoff and live validation must be checked separately. Mac runtime and downloadable-package acceptance remain separate release work.

Cisco ASA, FMC, standalone Palo Alto, Panorama, Check Point, FortiManager and standalone FortiGate are separate acceptance paths. Ask about your exact device, manager scope and workflow.

Walk through the evidence

A migration difference
is a decision to make.

This saved run compares a hand-built ASA configuration with a PAN-OS configuration containing intentional mistakes. It is a real execution against synthetic test inputs, not a customer migration.

Synthetic ASA to PAN-OS verification with eight open differences and an In review readiness status
Captured September 28, 2026 · Local 2.0.0 · saved run September 23, 2026 at 19:22:26 UTC. Fixture pair: edge01_asa.cfg → edge01_pan.xml. No customer data, nothing masked. This result comes from the Local verifier; hosted migration reports are separate.

What the result found

Two exposure differences, one outage, one NAT difference and four path differences. These are categories in this test result, not accuracy or coverage percentages.

Why it is still “In review”

All eight differences remain without a decision. The screen’s “Proven” label concerns modeled security behavior; it does not make the configuration ready for cutover.

Keep the scope of proof visible

Configuration analysis depends on captured scope and modeled features. It cannot establish live traffic behavior, device acceptance or organizational change approval on its own. Resolve assumptions, test the target and retain a rollback plan.

Start with your environment

See where Local fits
in your migration.

Share your vendor pair and the preparation work you need. We can discuss the current preview and the evidence needed before you rely on it.

Discuss an evaluation →Explore the public collectors →