Subnet Calc is built by a small software development team that found it painful to manage networks that were growing in complexity.
Engineers dealing with subnetting regularly will no doubt be aware of the online visual splitters which make it easy to split up a subnet but storing the subnet config and preventing overlapping allocations was not so easy.
Our team was using spreadsheets for this task and checking these into Git to maintain some sort of version history.
However, spreadsheets are difficult to review and meaningfully diff, transcription errors are common and there is no way for multiple engineers to safely work together.
We first planned Subnet Calc as an internal tool, but we soon realised that other teams could also benefit from the improved workflow offered by the tool.
The home page has a free visual subnet designer like many that have been around for a while. Our designer stores your last design in the browser’s local storage.
Paid plans add persistent storage, hierarchical child projects, edit locks, change descriptions, version history and diffs.
A leaf subnet can become a separately managed child project with its own locking semantics, and it is even possible for this to be hosted in a different region closer to the team that works on that project.
We have tried to keep the pricing low enough for individual engineers and small teams while still covering the cost of operating and improving the tool further.
I’d be interested to hear how other teams currently manage subnet hierarchies, especially how you stop overlapping allocations and coordinate changes across a team. I’m also interested in ideas for export formats. We currently allow end users to design their own but can create system-wide templates. What would the community find useful? I am thinking CSV, JSON, Terraform maps etc.
The project hierarchy, locking and version-history features all require an account, so I don’t expect feedback on these directly. The user guide gives a rough idea of how these features work. I’m happy to discuss the concepts and trade-offs and receive feedback about these features here.
RossMason•1h ago
Engineers dealing with subnetting regularly will no doubt be aware of the online visual splitters which make it easy to split up a subnet but storing the subnet config and preventing overlapping allocations was not so easy.
Our team was using spreadsheets for this task and checking these into Git to maintain some sort of version history.
However, spreadsheets are difficult to review and meaningfully diff, transcription errors are common and there is no way for multiple engineers to safely work together.
We first planned Subnet Calc as an internal tool, but we soon realised that other teams could also benefit from the improved workflow offered by the tool.
The home page has a free visual subnet designer like many that have been around for a while. Our designer stores your last design in the browser’s local storage.
Paid plans add persistent storage, hierarchical child projects, edit locks, change descriptions, version history and diffs.
A leaf subnet can become a separately managed child project with its own locking semantics, and it is even possible for this to be hosted in a different region closer to the team that works on that project.
We have tried to keep the pricing low enough for individual engineers and small teams while still covering the cost of operating and improving the tool further.
I’d be interested to hear how other teams currently manage subnet hierarchies, especially how you stop overlapping allocations and coordinate changes across a team. I’m also interested in ideas for export formats. We currently allow end users to design their own but can create system-wide templates. What would the community find useful? I am thinking CSV, JSON, Terraform maps etc.
The project hierarchy, locking and version-history features all require an account, so I don’t expect feedback on these directly. The user guide gives a rough idea of how these features work. I’m happy to discuss the concepts and trade-offs and receive feedback about these features here.