What does the closet need?
Describe the endpoints. Every model that can serve them is sized with the fewest switches and the smallest power supply configuration.
Results
All vendors
None selected shows every vendor. Turn chips on to narrow.
Where the numbers come from
Every spec is taken from the vendor's own datasheet, linked on each model. Values that disagree with other published figures, or that were derived rather than stated, are marked check in Browse and collected on the Needs checking page until someone confirms them.
How PoE budget is modeled
A switch model does not have one PoE budget. It has one per power supply configuration, so each model carries every configuration its datasheet lists, and the sizer picks the smallest configuration that covers the load. Each stored budget is the figure the vendor states, which is the power the supplies make available rather than what the ports can draw. Where that exceeds the port count times the per-port maximum, the sizer uses the port limit instead, and the budget is shown capped with the vendor's figure alongside it: a 24-port switch at 30W per port cannot deliver more than 720W however large the supply.
Numbers that are not directly comparable
Route scale is published differently by each vendor. Cisco states total IPv4 routes as direct plus indirect entries, while HPE Aruba states unicast routes and host table entries separately. They are shown as stated, not converted. Stacking bandwidth is also defined differently: Cisco uses dedicated rear stacking ports, while Aruba VSF stacks over the front uplink ports, which the sizer subtracts from the available uplinks. Fortinet has no hardware stacking at all; a FortiGate manages the switches as one fabric over FortiLink, so there is no member limit or stack bandwidth to compare.
Suggest a change
Spotted a wrong value or a missing model? Open a GitHub issue with the vendor datasheet link. No pull request required; maintainers turn accepted issues into data updates.
Coverage
Sources
Needs checking
These values disagree between two places in the same vendor datasheet, or had to be derived. They are shown as stated until someone confirms them against a newer datasheet, ordering guide, or written vendor confirmation. Accessory SKUs that are not yet traced to a vendor matrix are listed below as well; they still appear in Accessories without a check tag. To propose a fix, open a correction issue or see CONTRIBUTING.md for how to clear one in a pull request.