Does it generate device configuration?

No, deliberately. Syntax varies by platform and version, and a generated config that looks right invites being pasted without reading. The design is the output; turning it into commands needs somebody who knows the equipment.

Does it scan or discover my network?

No. It records what you intend, which is the more durable document. Nothing is polled and nothing leaves your browser.

How are the subnets chosen?

By the same allocator as the VLSM designer: largest first, with a 20% growth allowance, packed into the address space without gaps. Type a subnet in yourself and it is respected and worked around.

What does 'no findings' actually mean?

That the design is internally consistent — every segment fits, gateways are inside their subnets, no VLAN is duplicated, every device has a path to the edge. Whether it is the right design for the building, the budget and the people running it is not something a validator can judge.

Can I keep the project?

Export the JSON. It is plain and readable, sits sensibly in version control beside your other documentation, and imports back on any machine.

Home › Networking › Network Architecture Designer

Network Architecture Designer

One place for the whole design — devices, links, VLANs and addressing — checked by every rule the other tools use, and exported as a document you keep.

Local toolYour network plan stays in your browser. Nothing you enter is uploaded, logged, or sent to any server.

Project

Address space

What this is for, and what it will not do

Every other tool here answers one question well. This one holds the whole design, so the answers have to be consistent with each other — a subnet that fits, on a VLAN that exists, behind a device that is actually connected.

What gets checked

Addressing — overlaps, capacity, gateways inside their subnet, DHCP pools that do not swallow the router.
VLANs — duplicate IDs, reserved ranges, user traffic left on VLAN 1.
Topology — devices with no path to the gateway, and links referring to devices that are not in the design.
Fit — whether the segments actually fit the address space you were given.

What it deliberately is not

It does not generate configuration. Syntax varies by platform and version, and a generated config that looks right is more dangerous than none at all — it invites being pasted without reading. The design is the output; turning it into commands is a job for someone who knows the equipment.

It does not talk to your network. Nothing is discovered, scanned or polled. This records what you intend, which is the more durable document — what is responding today changes, and what you meant does not.

It does not replace judgement. A design with no findings is internally consistent. Whether it is the right design for the building, the budget and the people who have to run it is not something a validator can tell you.

Every tool this draws on

The addressing comes from the VLSM allocator, the checks from the same engine behind the VLAN designer and IPAM Lite, and the path analysis from the graph behind the OSPF designer. Each of those goes deeper on its own subject; this is where the pieces have to agree with each other.