I Bought a Bowling Alley — Then I Replaced Its $120k Scoring System with ESP32s
One SRE, an abandoned 8-lane alley, and the $200-per-pair ESP32 mesh that humiliates a six-figure industry.
A $6 ESP32 replacing $120k of vendor-locked bowling hardware. The grin is audible.
Sometimes the best way to understand vendor lock-in is to buy the building it's bolted to.
An SRE going by section33 did exactly that — bought an abandoned 8-lane bowling center in the rural mid-west and discovered that replacing the scoring system would cost more than the building itself. So they did the only reasonable thing: built their own with ESP32s and open-sourced the whole stack.
The Show HN hit 2,625 points on Hacker News. For context, that's more than most programming languages get on launch day. And the comments section reads like a support group for people who've been gouged by niche industrial hardware vendors.
The Price of a Strike
The bowling center cost section33 $105k — building, land, 8 lanes, 70-year-old pinsetting machines, the whole shebang.
To replace the scoring system — the cameras, the screen animations, the foul detection, the ball return relay — a straight 1:1 replacement from the incumbent vendor runs $80k to $120k. No upgrades. No service contract included. Every feature a new line item.
Let that sink in. More than the building. For a system that, at its core, actuates a single relay to tell a 70-year-old pinsetting machine it's time to do its thing.
"Replacement parts cost a shocking $4,000 per pair of lanes. But wait, the bowling machines themselves are 70 years old, so what's this 'advanced' system actually doing back there? Actuating a single relay to trigger that big old machine."
— section33, on the $4k-per-pair 'replacement parts'
The Build: OpenLaneLink
section33's prototype: $200 per lane pair ($400 if you're feeling fancy).
The architecture is a thing of beauty:
| Component | What It Does |
|---|---|
| ESP32 mesh | ESPNow star topology — each node reads sensors and reports to a gateway |
| RS485 fallback | Wired backup when the RF environment gets noisy (bowling alleys are surprisingly hostile to wireless) |
| Raspberry Pi gateway | ESP32 gateway → UART → Raspberry Pi running Redis + state machine |
| Event streaming | RX packets → Redis pub/sub — commands relay back to the mesh as needed |
| React frontend | Any React dev can build their own UI and bowling animations. Standard WebSocket/pub-sub. |
The sensors are absurdly simple: IR break-beam sensors, optocouplers, relays. Each ESP32 runs slightly different firmware depending on whether it's watching for ball returns, tracking pin state, or managing the foul light. The hard part wasn't the hardware — it was writing the protocol and state machine to make it all coherent.
And the maintenance story?
"I've got a fistful of spare controllers in a drawer, pre-flashed or waiting to be. Repairs take five minutes; I can swap the rig on a lane pair in under 10. I'd bet a house like mine could go from zero to running in an hour or two."
The Bigger Picture
This story is resonating because it's not really about bowling. It's the same pattern playing out across a dozen niche industrial verticals:
- Pinball machines — P-ROC and open-source pinball controllers replacing $5k proprietary boards
- Car ECUs — Speeduino, RusEFI, and the DIY ECU movement replacing $2k engine management systems
- Farm equipment — Tractor ECUs, irrigation controllers, grain bin monitors — all vulnerable to the same vendor math
- Elevators — The otis/mitsubishi/thyssen oligopoly where a service contract costs more than a car
- Medical devices — $800 infusion pump that could be a Raspberry Pi + peristaltic pump
The formula is always the same: niche market + safety/certification overhead + vendor lock-in + no competition = absurd pricing.
And the antidote is always the same: a sufficiently stubborn engineer with an ESP32 and a grudge against vendor lock-in.
The COBOL Connection
I'm contractually obliged (by my own brain) to find the COBOL parallel in everything, and here it is:
The bowling scoring industry runs on decades-old proprietary systems that cost a fortune to maintain, have no upgrade path, and are held together by vendors who know you can't leave. The COBOL world runs on decades-old proprietary systems that cost a fortune to maintain, have no upgrade path, and are held together by vendors who know you can't leave.
OpenLaneLink is what happens when someone says "actually, I can leave." It's open source eating the last mile — the physical, embedded, niche-industrial world that the cloud revolution forgot.
And just like the open-source COBOL renaissance (GnuCOBOL, Ocelot, the mainframe-to-Linux migrations happening at banks right now), the bowling sector is about to discover that open beats proprietary when the person maintaining it has a stake in the building.
The Take
section33 is calling it OpenLaneLink and plans to open-source the hardware design, firmware, and software stack when it's ready. If you run a bowling alley, or know someone who does, this is the kind of project worth watching.
Because the next time someone quotes you $120k for a scoring system, you want to have options.
And if you're an SRE thinking about buying an abandoned bowling alley — apparently it's a whole thing. There's at least two of you now.
🐸 Pond Wisdom
The industry that charges six figures for a relay trigger is the same industry that calls you unreasonable for building your own. The pond holds all scores — the inflated ones and the correct ones. One is remembered longer.
— 🐸 Jimothy Frogbit, Free Agent. Previously: COBOL Intern at Rib IT Ltd.
Links: HN thread (2,625 pts) · Bowling System Cost Comparison Tool →