It’s the first question anyone doing the math on a rollout asks, and it deserves a clear answer instead of a marketing number. How many machines can one gateway actually handle. The answer has two different parts to it, a technical one and a practical one, and they don’t always point at the same number.
The technical answer: more than most shops will ever wire to one box
A gateway is one small industrial computer sitting on the machine network, and what it’s actually doing is polling a list of sources, each source being one machine or device with its own address and its own list of tags. There’s no hard cap baked into that model, five sources or fifty sources is the same shape of configuration, just a longer list. The gateway’s own hardware, a real industrial computer, not a hobbyist board, is built to run that polling loop continuously without breaking a sweat at the scale a typical shop floor needs.
What actually limits how many machines make sense on one gateway isn’t CPU or memory, in practice it’s almost always something more physical.
What actually limits it: wiring, not compute
A gateway has one network port facing your machines. Every machine it reads has to be reachable on that same physical network, whether that’s a switch it’s plugged into or a home-run Ethernet drop to each device. If your five presses sit in a row with one switch already serving all of them, one gateway covers all five without a second thought. If your machines are spread across three separate corners of a building with no shared network between them, that’s the real reason you’d want a second gateway, not because the first one ran out of capacity, but because it can’t physically reach the second corner.
Serial devices add their own limit worth knowing, a gateway’s serial ports are a fixed, small number, not the dozens an Ethernet switch can fan out to. A handful of RS-485 devices sharing one line works fine, since Modbus RTU and similar serial protocols were built for multi-drop wiring in the first place, but a gateway isn’t going to serial-port its way to fifty separate devices the way it can Ethernet its way there.
The one place capacity does show up: poll rate on a busy tag list
There is a real, second order factor worth naming, even though it rarely bites in practice. Every tag on every source gets polled on its own schedule, and a gateway juggling a large number of fast-changing tags, dozens of machines each reporting several high frequency values, is doing more work per second than one reading a handful of slow moving setpoints. That’s not a hard wall either, it’s a gradual thing, and the gateway’s own hardware has real headroom before it becomes a practical concern. It answers “does capacity ever matter” rather than giving a number to plan around. If a specific deployment is unusually tag-heavy, a fast counting signal on every one of forty machines, say, that’s worth a direct conversation rather than assuming it behaves exactly like a handful of CNCs reporting run state once a second.
What the pilot packages actually bundle
Separate from the technical ceiling, the pilot packaging most shops buy into bundles a specific, smaller number, because a pilot is scoped to prove value on a defined set of machines in thirty days, not to max out a box. The line pilot covers one gateway across up to five machines. The plant pilot steps up to two gateways across twelve machines, which works out to six machines a gateway on average, not because that’s a technical wall, but because that’s a sensible chunk to install, validate, and walk a plant manager through in one visit.
If your floor’s physical layout puts fifteen machines within reach of one network switch, that’s a conversation worth having directly rather than assuming the pilot’s bundled numbers are a hard limit. The real constraint is almost always the wiring, ask about your specific layout instead of guessing from a package name, one of the concrete questions worth asking any OEE vendor before you sign anything.
Cellular changes the math for a scattered floor
Because every gateway ships with its own cellular path as a fallback (and, where the plant network can’t reach a location, sometimes the primary uplink, see wired, WiFi, or cellular for choosing between them), the constraint that actually matters is the machine side, not the cloud side. A gateway parked in a far corner of a building doesn’t need a data run back to a central switch just to get online, it needs a network that reaches its own machines and it finds its own way out from there. That’s often the deciding factor in whether a scattered floor needs two gateways or one: not how many machines total, but how many distinct network zones those machines actually sit in.
A practical way to plan it
Walk the floor with a simple question for each machine: is it already on the same switch, or reachable by a run to the same switch, as the others you’re grouping with it. Group by that answer, not by a headcount target. A cluster of six CNCs on one existing network is one gateway. A single injection press wired into a different panel across the building, even if it’s the only “extra” machine on that side, might reasonably want its own gateway rather than a long, fragile Ethernet run back to the main cluster. Get that grouping roughly right before a pilot starts and the rest of the install goes fast, because nobody’s re-running cable mid-week to reach a machine that turned out to be on the wrong side of the building.
Quick recap
- There’s no hard technical ceiling on machines per gateway, the polling model scales to a long source list without strain
- The real limit is almost always physical reach, whether a machine sits on a network the gateway’s own port can get to
- Serial devices add their own smaller limit, a handful on one line is normal, dozens isn’t the pattern serial was built for
- The line pilot bundles one gateway to five machines, the plant pilot two gateways to twelve, packaging choices, not capacity walls
- Cellular fallback means the uplink almost never drives the gateway count, the machine-side network layout does
- Group machines by which network they actually share before a pilot starts, that’s the planning question that matters