ProductsInfrastructure intelligence

ArcAtlas Next

Visual MSP command surface · Private product

A visual infrastructure workspace that turns device inventory into an operational map with hardware-aware nodes, path tracing, racks, change review, exports, and a client-ready presentation mode.

Private workspace · explore the interface and workflow below.

Actual UI · sample dataArcAtlas Next
ArcAtlas Next topology canvas with gateways, switches, servers, access points, and endpoints
Actual topology workspace · Cedar Ridge is a seeded sample environment
ArcAtlas switch inspector showing ports, VLAN 20, a peer interface, and path tracing
Inspect port state, VLAN, and peer interfaces · sample data
ArcAtlas rack elevation with sample infrastructure
Physical rack view · sample data

Inside the product

How it works

  1. Create a customer workspace and group the environment into sites and racks.

  2. Import inventory from ArcScan and review matches before accepting devices or links.

  3. Arrange hardware on the topology canvas, then inspect ports, VLANs, peers, and paths.

  4. Use rack and presentation views to explain the environment; export a technical or client-facing diagram.

What it solves

A discovery dump is not an infrastructure model. Technicians need a map that preserves uncertainty, site context, physical equipment, racks, paths, and imported evidence without making inferred relationships look confirmed.

Capabilities

  • Hardware-inspired topology with progressive zoom, path tracing, and a dense device inspector
  • Physical and logical views, rack elevations, sites, lifecycle data, and export-ready diagrams
  • ArcScan discovery review before imported inventory becomes trusted infrastructure
  • Technical and client presentation modes with optional reviewed AI environment analysis

Where it gets hard

  • The graph is always incomplete, so inferred and confirmed relationships need different visual weight
  • Layout has to remain readable as sites, racks, devices, and paths grow
  • Discovery imports cannot silently overwrite technician-owned context
  • The same environment has to work as both a technician command surface and a client-facing explanation

In the loop

Optional classification and environment analysis can suggest structure or observations, but imported and generated conclusions stay reviewable.

The technician decides what becomes authoritative, how the environment is presented, and which suggested relationships or findings are accepted.

Actual product interfaces. Captions identify local previews and sample data. Screenshots do not expose private workspaces or production records.

Start a build

Start with a real workflow

Bring the idea.

If this is close to the product you need, tell us what is different. We will build the version that fits the work.

Start a Build