Our robotics program is built on a kit that just got discontinued — now what?
Your kits don't die on discontinuation day. Audit app support, spares and competition dates, then buy churn-proof: standard Python, offline-first, commodity sensors, and a simulator.
TL;DR
- Your kits do not stop working the day they are discontinued. First audit what actually breaks: app support, spare parts, competition eligibility. Fix the urgent gaps, keep teaching, and replace hardware on your timetable, not the vendor's.
- LEGO Education announced in January 2026 that the entire SPIKE portfolio is being retired, with sales ending 30 June 2026. That is four years after Mindstorms was discontinued and schools were pointed at SPIKE. FIRST LEGO League teams may use SPIKE only through the 2027-28 season.
- The durable fix is a procurement rule, not a brand choice: buy platforms that run standard languages (Python/MicroPython), work fully offline with no account, use commodity connectors with individually purchasable sensors, and have a simulator so the curriculum survives hardware gaps.
- Skills written in a standard language outlive any single board. Skills locked inside a proprietary app belong to the vendor, not to your students.
"We bought class sets twice in four years. Now a third?"
If your robotics program is built on LEGO SPIKE Prime, 2026 has been rough. LEGO discontinued Mindstorms in 2022 and encouraged schools to migrate to SPIKE. Many did, at class-set prices. In January 2026 LEGO announced the retirement of the full SPIKE portfolio, with sales ending 30 June 2026 and a successor "Computer Science & AI" kit starting at $339.95. Schools that followed the official migration path are now facing their third buy-in in four years.
This is not a new feeling. When Mindstorms was killed, a German school IT assistant put the whole problem in one sentence:
"What we need is planning security."
— Jürgen Adloff, Maria Montessori comprehensive school, via heise.de, Jul 2024
The cost is not just hardware. It is every lesson plan, teacher training hour and build guide tied to the platform:
"Coaches and mentors who have built curricula around SPIKE Prime will need to retrain on new platforms[,] rewrite lessons and robot design strategies"
Competition teams got their own version of the same shock. In December 2025, FIRST announced that from the 2027-28 season the new SystemCore control system will allow exactly one legal actuator, the REV-built A301. The Chief Delphi announcement thread ran to 189 posts, 8,474 views and 1,537 likes, and a change.org petition followed. One student petition post on r/FTC summarised the objections:
"the ongoing rev monopoly, a lack of potential reliability, limited accessibility especially for low-budget and foreign teams, and the future obsolecence of current actuators that many of us have paid good money for"
And beyond education, consumer IoT spent 2025 teaching everyone the same lesson. AeroGarden announced it was shutting down on 1 January 2025, promising app support only "until March 2026". Belkin announced Wemo's cloud and app would terminate on 31 January 2026. A Hacker News commenter drew the obvious conclusion:
"This is why any piece of automation that comes into my home is required to function without internet or an app."
Why this keeps happening
Education hardware is a side business for consumer brands
Toy and consumer-electronics companies run on retail product cycles. Portfolios get pruned for reasons that have nothing to do with your five-year technology plan. Schools budget in multi-year cycles and expect a class set to serve several cohorts. Those two clocks were never synchronised, and when they clash, the school loses. Mindstorms in 2022 and SPIKE in 2026 are the same story twice.
Closed ecosystems turn discontinuation into total loss
If the connectors are proprietary, the sensors are proprietary, and the programming language is a vendor-specific block dialect inside a vendor app, then everything is coupled to one company's roadmap. When the platform dies, the curriculum, the teacher training and the spare-parts pipeline die with it. Compare that with a program taught in standard Python: the board is replaceable, the learning is not.
Cloud and app dependency adds a second kill switch
Even when the hardware survives, an app end-of-support date can strand it. LEGO's EV3 app reaches end of support on 31 July 2026, stranding working robots that predate SPIKE. AeroGarden and Wemo show the harder version: devices that need a cloud to function simply stop. Any device that requires an account, an app store listing or a server to do its basic job has a lifespan set by someone else's finance department.
Competition rules can lock you in overnight
Teams do not control the rulebook. FIRST's single-actuator decision shows that even careful buyers can have their inventory obsoleted by policy rather than by physics. Commenters on the Chief Delphi announcement thread pointed out the irony of a rule promoting design freedom by removing every alternative option.
What actually works: a churn-proof procurement checklist
You cannot make a vendor immortal. You can make your program survive any single vendor's death. Before the next purchase order, test every candidate platform against these six rules:
- Standard language or nothing. The platform must be programmable in MicroPython, Python or another mainstream language, not only in a proprietary block dialect. Blocks are fine for beginners, but there must be a documented path to real code, because real code transfers to the next board, and to matric, and to a career.
- Run the router-off test. Unplug your internet and try a full lesson: flash code, read sensors, drive motors. If the platform needs an account, a login server or a cloud sync to do its basic job, it fails. Load shedding makes this test doubly relevant in South African schools, but the AeroGarden and Wemo shutdowns make it relevant everywhere.
- Commodity connectors and individually sold spares. Can you buy one replacement sensor, or must you buy another full kit? Proprietary plugs are a tax on every future repair. Prefer plug-and-play ports that accept widely available sensors.
- Simulator continuity. If the hardware is lost, broken, stolen or discontinued, can students keep learning in a browser? A simulator that runs the same language as the board means your curriculum is never hostage to a shipping delay or a product retirement.
- Apply the vendor-vanishes test. Ask the supplier directly: if your company disappeared tomorrow, what still works? The honest answers are the ones that name open standards. Community rescue projects exist, Pybricks literally brands itself "Saving LEGO MINDSTORMS", but a rescue you do not need is better than a rescue that arrives.
- Stage the spend. Pilot with a small set for one term before committing to a class set. Budget for spares at purchase time, not repair time, while parts are still on sale.
How we approached this with sheenbot∞
We designed sheenbot∞ around exactly these failure modes, because we watched schools live through them. The board runs standard MicroPython, so code and skills outlive any one product. It works fully offline with no account, no subscription and no cloud dependency; nothing about the board stops working if our servers are unreachable. Ports are plug-and-play and sensors are commodity parts sold individually in our store, so a broken sensor is a small purchase, not a new kit. Firmware updates ship over BLE. And curriculum continuity is covered by sheen verse, a free in-browser 3D simulator that runs real MicroPython with no hardware at all. To be fair to the checklist: we are a smaller company than LEGO, which is precisely why we anchored the platform to open standards rather than asking for trust. If you are re-planning a whole lab rather than one kit, our lab sourcing and setup service exists to run this procurement exercise with you, vendor lists included.
Your realistic options, compared
| Option | Examples | What survives discontinuation | Teacher workload | Honest downsides |
|---|---|---|---|---|
| Closed proprietary ecosystem | LEGO SPIKE, VEX IQ | Hardware keeps running, but apps, spares and competition eligibility expire on the vendor's schedule (SPIKE sales end 30 June 2026; FLL use ends after 2027-28) | Lowest on day one: polished lessons and classroom management built in | Repeat repurchase risk (Mindstorms, then SPIKE, now a $339.95 successor); block-dialect skills do not transfer; proprietary connectors |
| Open-standard board | sheenbot∞, micro:bit | MicroPython/Python code runs on the next board; commodity sensors are reusable; offline operation is unaffected by any cloud shutdown | Moderate: real-language teaching needs some teacher upskilling, eased by block-to-code editors and simulators | Smaller build-system ecosystems than LEGO's bricks; smaller vendors carry their own longevity risk, mitigated but not erased by open standards |
| Pure DIY | Raw ESP32, Arduino | Everything: every part is commodity and multi-sourced | Highest: the teacher becomes the systems integrator, curriculum author and repair desk | Fragile wiring in young hands, no unified support, slow lesson setup; hard for younger learners |
FAQ
Is LEGO SPIKE Prime discontinued?
Yes. LEGO Education announced in January 2026 that the entire SPIKE portfolio is being retired, with sales ending 30 June 2026. The announced successor is a "Computer Science & AI" kit starting at $339.95, and FIRST LEGO League teams may continue using SPIKE only through the 2027-28 season.
Do our existing SPIKE and EV3 kits stop working now?
No. The hardware keeps working; what expires is official software support, spare-part supply and competition eligibility. Note the dates: EV3 app end of support is 31 July 2026, and community firmware projects like Pybricks, which brands itself "Saving LEGO MINDSTORMS", can extend the useful life of retired bricks. Use the remaining runway to teach while you plan the transition calmly.
What is the best coding robot that works without a subscription or account?
Judge candidates by criteria, not marketing: it should program in standard MicroPython or Python, pass a router-off test for a full lesson, and use individually purchasable commodity sensors. sheenbot∞ is built to that spec: fully offline, no account or subscription, standard MicroPython, with a free browser block editor and simulator you can test before buying anything.
What happens to smart devices when the cloud service shuts down?
If the device needs the cloud for its core function, it stops working or loses most features. AeroGarden announced its shutdown for 1 January 2025 with app support promised only "until March 2026", and Belkin set Wemo's cloud and app termination for 31 January 2026. The protection is buying devices that function locally, without internet or a mandatory app.
How do we make our next robotics purchase churn-proof?
Apply the six-rule checklist above: standard language, offline-first operation, commodity connectors and spares, simulator continuity, an explicit vendor-vanishes answer, and staged buying. No vendor can promise to exist forever, so buy platforms whose value survives the vendor. If you want help running that process for a whole lab, see our lab sourcing service or try the free sheen verse simulator with your class first.
