Rackbinder

The documentation small IT teams never get around to writing.

Each module takes the facts you already have — a host count, a chat log, a device list — and produces the document a client, an auditor or the next tech would ask for. Everything runs in your browser. No account, no upload, nothing stored anywhere but this tab.

Live

Planned — in build order

Module 3

Onboarding / Offboarding Builder

Per-role checklists with the accounts, groups, devices and access each role needs — and the reverse on exit.

Module 4

Network Topology Document

A written network description generated from a device and link inventory, with a diagram-as-code export.

Module 5

Change Document

Change request, implementation plan, test plan and rollback, from one short form.

Module 6

Firewall Rule Change-Log

A rule register that records who asked, why, when it was added, and when it should be reviewed.

Why documents, not calculators

Free subnet calculators are everywhere. What nobody hands you is the addressing standard, the postmortem, the change record — the artefact that outlives the engineer who knew the network by heart.

One suite, one data model

The addressing plan from module 1 becomes the input for the topology and change modules. The moat is the suite, not the math.

Built by a member of the audience

Written by a Tier 1/2 tech with seven years of support and network work, studying for the CCNA — which is why the planner shows its working.