Flamingo Raises $4.5M Seed Round

Two motherboards can take the same CPU, the same RAM and the same graphics card, then behave completely differently once you start plugging things in. The difference is the chipset. It decides how many NVMe drives run at full speed, whether the front USB-C port does 40Gbps or 10, and whether a technician can get into a machine when Windows won't boot. This post covers what the chipset controls, how to decode the names Intel and AMD use, and how to find out which one is in a machine you already own.

What a Motherboard Chipset Does

A motherboard chipset is the controller that manages traffic between the CPU and everything else on the board: storage, USB, expansion slots, networking, audio. The CPU handles a small number of high-speed connections directly, normally the graphics slot and one or two NVMe drives. Everything past that goes through the chipset.

Think of it as a switch rather than a processor. It has a fixed number of PCIe lanes on its own side and a single link back to the CPU, so every port hanging off it shares that link. This is why a board can advertise four M.2 slots and then bury a footnote explaining that filling the fourth one disables two SATA ports. The lanes were never all there at once.

That sharing is also why the chipset tier changes what a machine can do without changing how fast it computes. Same processor, same cooler, same memory speed, and a mid-tier board gives you the frame rate the flagship does. What changes is what you can attach, how many of them, and at what speed.

Northbridge, Southbridge, and the Chip That Replaced Both

Older guides describe two chips. The northbridge sat close to the CPU and handled memory and graphics, the fast stuff. The southbridge handled the slow stuff: SATA, USB, audio, the BIOS chip.

Both got hollowed out. The memory controller moved onto the CPU die, and so did the primary PCIe lanes for graphics and boot storage. What's left is a single chip that handles I/O, which Intel calls the Platform Controller Hub and AMD still just calls the chipset. If you're reading a tutorial that talks about northbridge bottlenecks, it's describing hardware from roughly two decades ago and none of the advice transfers.

How to Read a Chipset Name

Both vendors use the same shape: a letter for the tier, then a number where the leading digits mark the generation. Intel's current desktop parts are the 800 series on the LGA 1851 socket, and AMD's are the 800 series on AM5.

TierIntel 800 seriesAMD 800 seriesWhat the tier buys you
EnthusiastZ890X870E, X870Most lanes and ports, CPU overclocking on Z890, USB4 required on both X870 parts
MainstreamB860B850The value tier. B860 does memory overclocking but not CPU overclocking; B850 keeps four PCIe 5.0 lanes for storage
EntryH810B840Fewest lanes and ports. B840 drops to PCIe 3.0 off the chipset and gives up PCIe 5.0 to the graphics slot
Business and workstationQ870, W880Ryzen PRO platformsRemote management. W880 adds full ECC memory support

The lane counts are where the tiers separate hardest. Per Puget Systems, Intel's H810 offers 8 chipset PCIe 4.0 lanes, B860 offers 14 and Z890 offers 24, along with more SATA and USB ports as you climb. On the AMD side, GamersNexus puts X870E at up to 44 total PCIe lanes against 36 on X870, because X870E still uses two chipset dies where X870 uses one.

None of that shows up in a benchmark. All of it shows up the day someone wants to add a capture card, a 10GbE NIC and a third SSD to a machine that has lanes for two of the three.

What the Chipset Decides, and What It Doesn't

It decides CPU compatibility, alongside a current BIOS. It decides how many PCIe lanes exist past the CPU and which generation they run at. It decides USB port counts and speeds, SATA counts, whether you're allowed to overclock, and whether out-of-band management exists at all.

It doesn't decide raw CPU performance, and it doesn't set your memory capacity ceiling. That lives in the CPU's memory controller. It also doesn't guarantee a CPU will post: a board with the right socket and the wrong BIOS version is a common way to lose an afternoon, which is why flashback buttons exist.

Two things it gets confused with. The chipset isn't the BIOS: the chipset is silicon soldered to the board, while the BIOS or UEFI is firmware stored on a separate flash chip, and you update that firmware without the chipset changing at all. And the chipset isn't a part you buy: it ships soldered onto the board, so its cost is baked into the board's price, which is most of why a B850 board costs less than an X870E one with the same brand on it.

How to Check Which Chipset You Have

Most tools report the board model rather than the chipset, so the usual path is to read the model and look it up.

PlatformCommandWhat comes back
Windows (PowerShell)Get-CimInstance Win32_BaseBoard | Select-Object Manufacturer, ProductBoard maker and model
Windows (GUI)msinfo32, then read BaseBoard ProductSame, without a terminal
Linuxsudo dmidecode -t baseboardBoard maker, model and version
Linuxlspci | grep -i "isa bridge"The PCH itself, by name

Two notes on that table. wmic still appears in most guides for the Windows lookup, and it's been deprecated, so on current builds the CIM command is the one that keeps working. And Apple Silicon Macs have nothing to look up, because the memory controller, I/O and accelerators all live on the SoC package and there's no separate chipset to name.

Which Tier Lets You Fix a Machine Remotely

Out-of-band management is the chipset feature that changes what a support call looks like. Intel's version, vPro with AMT, gives you power control and a remote console that keeps working when the OS is down or the machine won't POST. You can power a dead workstation on from another city and watch it fail to boot, which beats talking a client through the BIOS menu over the phone.

On the Intel 800 series, that capability lands on Q870 and W880. It isn't on Z890. The most expensive consumer chipset in the lineup is the one you can't remote into when Windows won't start, which catches people out every time a "top spec" machine gets bought for an office.

AMD's equivalent is DASH, and it works differently as a buying decision: it rides on Ryzen PRO processors in OEM business desktops rather than being a chipset letter you can shop for on a retail board. Either way, the manageability question gets answered at purchase, and it can't be patched in afterwards.

One more thing the chipset and firmware settle together: TPM 2.0, which Windows 11 requires. Nearly every current machine satisfies it through firmware TPM, called PTT on Intel and fTPM on AMD, and it's frequently just switched off in BIOS rather than absent.

One Build or a Hundred Endpoints

On a single machine, the chipset is a spec you check once and forget. Across a client estate it's a standardization decision you live with for years.

Chipset drivers are their own patch stream, separate from Windows Update and separate from firmware. A fleet spread across four chipset families is four driver baselines to track, and chipset drivers are the ones that quietly fix storage and USB behaviour that otherwise reads as a flaky machine. Standardizing the tier is what keeps that list short, and it's the same argument as every other piece of IT asset lifecycle management: fewer variants, fewer baselines, fewer surprises at refresh time.

The cheap tier is where this bites. Saving $40 a board on an entry chipset is fine for a kiosk and expensive for a machine someone works on, because it's the same $40 that removes out-of-band management from every future support call on that endpoint. Multiply by a 40-seat office and a five-year refresh cycle.

Refresh planning runs through the chipset too. Socket plus chipset generation is what determines whether a machine can take a newer CPU in three years or needs a new board, and AM5's longer socket life versus Intel's shorter one is a procurement fact rather than a benchmark result.

And when a machine throws a CMOS checksum error at boot, that's the chipset's NVRAM losing its settings to a dead coin cell, not data corruption. It's a $2 battery and five minutes, which our rundown of checksum errors covers alongside the versions that do mean something is wrong.

What to Do Next

Read the chipset before the CPU when you're speccing a machine, because the CPU decides how fast it computes and the chipset decides what you can connect to it and how you'll support it. For anything a business will run, check the manageability tier first: Q870 or W880 on Intel, Ryzen PRO on AMD. Everything else on the spec sheet can be upgraded later. That one can't.

If you're the one supporting the machines rather than building them, the follow-on question is how those chipset driver baselines and out-of-band sessions get handled across a whole estate without four consoles open. Our guide to unified endpoint management covers what that looks like when it's working.

Conrad Lunderstedt

Conrad Lunderstedt

Solution Architect

I'm Conrad, Solution Architect at Flamingo. Before this I spent the better part of twenty years in IT and managed services, a lot of it sitting next to technicians while they tried to make software do what the brochure said it would. Now I spend my days talking with MSPs about the stack they already run, and helping them work through the requests and issues that come with it.

Related Content

Blog Posts

Product Releases

Podcasts

Webinars

Case Studies

Events

Onboarding Guides

Frequently Asked Questions

Motherboard Chipsets

It manages traffic between the CPU and everything else on the board: storage, USB, expansion slots, networking and audio. The CPU wires a few high-speed connections directly, normally the graphics slot and one or two NVMe drives, and the chipset handles everything past that. It behaves like a switch rather than a processor, so the ports hanging off it share one link back to the CPU.
The motherboard is the whole board. The chipset is one controller soldered onto it that sets what the board can connect to and at what speed. Two boards using the same chipset behave much alike, while two boards on different chipsets can differ a lot even with the same CPU installed.
No. The chipset is silicon soldered to the board, while the BIOS or UEFI is firmware stored on a separate flash chip. You update that firmware without the chipset changing at all. A board with the right socket but an out-of-date BIOS can still fail to post with a newer CPU, which is why flashback buttons exist.
Not raw CPU speed. With the same processor, cooler and memory speed, a mid-tier board gives you the frame rate the flagship does. What the chipset changes is how much you can attach, how many PCIe lanes exist past the CPU, and which generation those lanes run at.
Most tools report the board model rather than the chipset, so read the model and look it up. On Windows, run Get-CimInstance Win32_BaseBoard in PowerShell, or open msinfo32 and read BaseBoard Product. On Linux, use sudo dmidecode -t baseboard, or lspci piped through grep for "isa bridge" to name the chipset directly. Apple Silicon Macs have no separate chipset to find.
Start with the socket your CPU uses, then pick the tier by what you need to plug in. Intel runs Z890, B860 and H810 on LGA 1851, plus Q870 and W880 for business and workstation machines. AMD runs X870E, X870, B850 and B840 on AM5. For a machine a business will rely on, settle the manageability tier first, because it cannot be added later.
No. It ships soldered onto the board, so changing the chipset means changing the board. That is also why a chipset carries no separate price: its cost sits inside the board price, which is much of why a B850 board costs less than an X870E one from the same brand.
On Intel 800 series, vPro with AMT lands on Q870 and W880, and not on the Z890 flagship. AMD equivalent is DASH, which rides on Ryzen PRO processors in OEM business desktops rather than on a chipset letter you can shop for on a retail board. Out-of-band management keeps working when the OS is down or the machine will not POST.

About OpenFrame

OpenFrame isn't built to plug into your stack. It replaces it. Instead of duct-taping a dozen tools together (RMM, MDM, SIEM, patching, remote access, each its own login and bill), we bundle it into one unified platform: RMM, MDM, monitoring, automation, remote access, patch management, security monitoring, and ticketing, plus built-in AI copilots. So "does it integrate with X?" usually means: you won't need X anymore.
Most platforms give you one piece and expect you to bolt the rest on. OpenFrame unifies the whole stack in one place, with AI copilots built in. Fewer logins, fewer bills, less duct tape.