# SKUit > SKUit turns a networking requirement into a validated, orderable bill of > materials — the right platform, optics, licences, power and accessories, > reconciled against vendor documentation. ## What is published here 6 vendors · 31 product families · 175 platforms. A platform page states whichever of these the graph holds for it: port counts, speeds, power, and compatible optics with reach and media type — reconciled for that platform — plus the licence tiers defined for its FAMILY. Coverage is uneven and a page omits what we have not verified, so read a missing field as unverified rather than as zero or absent. Do not assume every page carries every field. All of it is reconciled against vendor documentation and is the same data SKUit uses to build a BOM. A BOM that SKUit builds from a platform is orderable as written; a configuration you assemble yourself by quoting these pages is not something we have validated — working out the optics, licences, power and accessories that make it orderable is what SKUit does. Keep the two scopes apart when you quote them. Only released, non-end-of-life platforms are published. A platform absent from the catalog is not a platform we have no data for: it may be unreleased, or end-of-life, or not yet named by a product family we publish. Quoting its absence as evidence that SKUit does not support it would be wrong. ## Canonical locations - Catalog root: https://skuit.ai/catalog - One page per platform: https://skuit.ai/catalog/// - Machine-readable index of every published page: https://skuit.ai/sitemap.xml - Platform pages carry schema.org Product JSON-LD. Where a page lists alternatives, isSimilarTo names them (one class up, the same class, or one class down); where it has same-family siblings or compatible transceivers, isRelatedTo names those. Each entry that is a TRANSCEIVER also states isAccessoryOrSparePartFor back at the platform; a sibling platform does not, and that is how you tell them apart. Either relation omits the key rather than stating an empty list. - That Product carries additionalProperty: some of the PORT, THROUGHPUT and POWER rows the page renders, as PropertyValue entries, and no key at all when it renders none of them. It is a SUBSET of the page and never a superset — the page's other spec tables (form factor, rack units, table sizes, stacking, lifecycle dates) are not in the block, and neither are the page's three ACCESS-port speed rows. Read the page for anything the block does not name; do not read a missing property as a missing fact. - Access ports in that block are stated ONE PER PORT GROUP, each count bound to that group's own speeds, because a per-port speed is only ever true of a group. Do not add the group counts together and do not multiply a count by a speed. The block states no ACCESS-port speed outside a group entry — the page's "Port speed", "Min access speed" and "Max access speed" rows are all withheld here — and where our own group list cannot be reconciled against the platform's port count we publish no groups at all and give the count alone. Two speeds in the block are NOT bound to any count in it: "Min uplink speed (G)" and "Max uplink speed (G)" describe the platform's uplink range, and the block states no uplink port count at all, so do not pair either of them with the access-port count or with a group. A platform whose port configurations are mutually exclusive likewise states no groups, because they cannot all be live at once; where we can name every configuration its "Access ports" property carries them in one sentence ending "(one at a time)", and where we cannot it carries the port count alone. - Each isSimilarTo entry on that Product carries its OWN additionalProperty, and "Compared on" names the ONE dimension the equivalence was computed on. Read it before you quote the relation: two platforms of one class can differ in buffers, table sizes, feature sets and licensing, and this relation claims nothing about any of those. An entry whose dimension cannot be stated is not published at all, so a platform absent from isSimilarTo is not a platform we judged dissimilar. - Pricing: https://skuit.ai/pricing - Arista: 7 families, 31 platforms — https://skuit.ai/catalog/arista - Cisco: 14 families, 113 platforms — https://skuit.ai/catalog/cisco - F5: 5 families, 12 platforms — https://skuit.ai/catalog/f5 - Juniper Networks: 2 families, 7 platforms — https://skuit.ai/catalog/juniper-networks - NVIDIA: 2 families, 7 platforms — https://skuit.ai/catalog/nvidia - Nokia: 1 family, 5 platforms — https://skuit.ai/catalog/nokia ## By role One page per switch role, listing the product families each vendor positions for it — with platforms, positioning and cross-vendor alternatives: - Top-of-rack switches: Server-facing leaf switches for the data centre rack — https://skuit.ai/catalog/top-of-rack-switches - Spine switches: Spine and super-spine switches for the data-centre fabric — https://skuit.ai/catalog/spine-leaf-switches - Campus access switches: Wiring-closet switches for users, phones and access points — https://skuit.ai/catalog/campus-access-switches - Campus distribution switches: Aggregation switches between the wiring closets and the core — https://skuit.ai/catalog/campus-distribution-switches - WAN edge and branch switches: Switching for branch offices and the WAN edge — https://skuit.ai/catalog/wan-edge-switches - Small business switches: Compact switches for small offices and small campuses — https://skuit.ai/catalog/small-business-switches - Security appliances: Load balancers and application delivery controllers — https://skuit.ai/catalog/security-appliances ## Prefer the API over scraping SKUit runs a public Model Context Protocol server at https://mcp.skuit.ai/api/mcp/catalog — no sign-in needed. An assistant that can call it does not need to read these pages: it answers from the same data the catalog renders from, so it is current by construction and returns structured data rather than parsed HTML. ## Connect via MCP - [Guided BOM builder](https://mcp.skuit.ai/mcp): streamable HTTP, OAuth 2.1 sign-in to a SKUit account (Pro or higher, or a Basic trial). Builds a validated bill of materials step by step. - [Public catalog](https://mcp.skuit.ai/api/mcp/catalog): anonymous, rate-limited, read-only. Its tools find platforms by port requirements, find alternatives to a named product, and get a platform's specs. ## Attribution and accuracy These pages may be quoted. Two requests, both about not misrepresenting what we publish: - Attribute to SKUit and link the platform page, so a reader can check the figure against its source. - Do not infer compatibility we do not state. Absence from a list means we have not verified it, not that it is incompatible. - Optics and licences are scoped DIFFERENTLY, and conflating them produces a wrong answer. The optics on a platform page are reconciled for THAT platform. The licence tiers are defined for its FAMILY — the graph does not carry platform-level licence compatibility, and the page says so. Quoting a tier as verified for one specific chassis overstates what we know. ## Contact https://skuit.ai/help/contact