Guide Old systems and supplier trouble
When the product under your system ends
When a supplier ends a product, what keeps working was decided long before, by what you secured while the product was still sold.
- Published
- Updated
- Reading time
- 7 min read
- Editor
- David Lahuta
In short
- In the week of 5 January 2026, Bose published the interface of its SoundTouch speakers before switching off their cloud, and the company behind the open source Tailwind CSS framework let 75% of its engineering team go.234
- Both left owners something that still works, because the speakers can run without the cloud and the framework's code is open.15
- What keeps working is decided years earlier by four things, operation without the supplier's cloud, published interfaces, a full data export, and the source code or a copy held in escrow.
- Since September 2025, EU law gives a customer of a cloud service the right to switch provider and take its data along, within set deadlines.9
What ended in the week of 5 January 2026?
Two endings in one week, from two very different suppliers, and a question from Brussels.
Bose announced in October 2025 that the cloud behind its SoundTouch speakers would end on 18 February 2026.2 On 7 January 2026 it moved the date to 6 May 2026 and published the technical description of the speakers' interface, so that independent developers could build their own compatible tools.23 The speakers came to market in 2013, and Bose said it could no longer sustain the cloud behind this older generation.1
On 6 May the app changed to a version that controls the speakers over the home Wi-Fi network, without the cloud.1 Commands now go straight to the speaker on the local network.3 Streaming over Bluetooth, AirPlay, Spotify Connect and a cable kept working, as did setup, remote control and grouping speakers.1 Presets, music browsing in the app and Alexa voice commands stopped, and the speakers no longer receive security updates.1 Bose said it would delete usage data by 15 May 2026, and owners could ask to download or delete their data through a privacy request form.1
The same week, Adam Wathan of Tailwind Labs wrote on the project's GitHub page that 75% of the people on its engineering team had lost their jobs the day before.4 Tailwind CSS is an open source framework for designing web pages, and he wrote that it was bigger than ever.4 Yet revenue was down close to 80%, and traffic to the documentation, the only way people find the paid products, was down about 40% from early 2023.4 Without customers, he wrote, the company cannot afford to maintain the framework.4 Its code is published under the MIT License, which lets anyone use, copy, change and distribute it free of charge.5
On 6 January 2026, the European Commission opened a call for evidence on European open digital ecosystems, a public request for views before it sets a policy.6 The Commission's news item of 12 January 2026 says European governments and companies depend heavily on digital technology from outside the EU, which limits their choice and creates challenges for cybersecurity.7
| The speakers | The framework | |
|---|---|---|
| What ended | The supplier's cloud1 | Most of the engineering team that maintains it4 |
| What still works | Control on the home network, streaming, setup1 | All of the published code, free to use and change5 |
| What was lost | Presets, voice commands, security updates1 | Certainty about who will maintain it4 |
| What made the difference | A published interface and an app that works without the cloud13 | An open licence5 |
Neither group of owners had a say in the decision. What they kept had been settled when the product was designed and licensed.
What decides what keeps working?
Four things, and each has to be in place before an end is announced. Afterwards the supplier decides alone.
- Operation without the supplier's cloud. The speakers still play because they can be controlled on the local network.1 For each of your systems, ask which functions stop when the supplier's servers go dark, such as sign-in, licence checks, updates or the data itself.
- Published interfaces. An interface is the documented way in which other software talks to a system. Bose published one so that others could build compatible tools.3 With a documented interface, another supplier can connect to your system or replace one part of it.
- A full data export. Your records, documents and history, with the links between them, in a common format that another system can read. Test it at least once a year, because an export nobody has opened is a hope, not a plan.
- The source code, or a copy held in escrow. The code is what lets somebody else keep a system running. Where a system carries the business, you either own the code, it is open, or a neutral third party holds a current copy and releases it to you if the supplier stops. That arrangement is called source code escrow.
Open code is not the same as maintenance. Wathan wrote that if the business could not be fixed, the project would become unmaintained once nobody was left employed to work on it.4 Somebody, a supplier or your own people, must still be able to repair and update what you run.
What does European law already give you?
Two regulations set a floor, one for cloud services and one for products with software in them.
The Data Act, Regulation (EU) 2023/2854, has applied since 12 September 2025.9 For cloud and other data processing services, the customer's rights to switch provider, or to move to its own servers, must be set out in a written contract that the customer receives before signing.9 The contract must include at least the following.9
- A notice period of no more than two months to start the switch.9
- A transition of no more than 30 calendar days, during which the service continues and the provider helps the customer and the new supplier. Only where that is technically unfeasible may the provider justify a longer period of up to seven months.9
- An exhaustive list of the data and digital assets that can be taken along, and at least 30 days to retrieve them afterwards.9
- The provider's duty to support the customer's exit strategy.9
From 12 January 2027 a provider may charge nothing for the switch, and until then no more than its direct costs.9 Where no common standard exists, the provider must export all exportable data on request in a structured, commonly used and machine-readable format.9 Some of these duties, including the end of switching charges, do not apply to a service built mainly for one customer and not offered on a broad commercial scale.9 For such a system, the contract has to carry them.
The Cyber Resilience Act, Regulation (EU) 2024/2847, sets its main duties for software and hardware products placed on the EU market from 11 December 2027.10 The manufacturer sets a support period during which it must handle security flaws, at least five years unless the product is expected to be in use for less.10 The end date of that period, at least the month and year, must be stated clearly at the time of purchase.10 The regulation also says manufacturers should consider releasing the source code when support ends, to other companies that will keep handling security flaws or to the public.10
Both laws set a floor. What a business system needs above it belongs in the contract.
How do you plan an exit in five steps?
An exit plan is written while the supplier is still there and willing to help.
- List the systems the company runs on, and for each the product, the supplier and what depends on the supplier's cloud.
- Rate what an ending would cost you for each one, such as days of stoppage, lost history or a broken link to another system.
- For the critical ones, run a full data export now and check that someone outside the supplier can read it.
- Write down how each critical system would keep running without its supplier, meaning who takes over, with which code, interfaces and access, and in what time.
- At the next renewal, bring the contract up to date with the clauses below. Repeat the review every year, and whenever a supplier is sold or changes its terms.
Which clauses belong in the contract?
Before you decide
- Notice before any product, function or service is ended, long enough for you to move.
- A list of the functions that need the supplier's cloud, and how the system runs without them.
- Documented interfaces, open to you and to any supplier you name.
- A full export of all your data on request, in a common machine-readable format, at no extra charge.
- Time to retrieve your data after the end, and deletion only once you confirm you have it.
- The source code delivered to you, published under an open licence, or held in escrow with clear release conditions such as insolvency or end of support.
- Help with the move to another supplier, with the service running until the move is done.
- The end date of security updates, stated in writing.
What this means for a company in Europe
On 3 June 2026 the Commission adopted its Strategy for EU Open Digital Ecosystems, which it also calls the Open Source Strategy.8 It promotes open standards in public procurement, so that authorities can choose the best solution rather than being locked into proprietary systems.8 The Commission puts open source behind 70 to 90% of all code in the digital economy.7 A company can apply the same test to its own systems on a smaller scale. A system whose interfaces, data and code you can reach is one you can keep when the supplier changes course.
Next step
If you would like to know which of your systems rest on a product that could end, we are glad to go through them with you in a short meeting. What you do with the result is entirely your decision.
Sources
- 1. Bose, SoundTouch support discontinued, end of life page and FAQ (update of 6 May 2026). Read on 17 November 2026
- 2. Bose, SoundTouch end of life page as updated on 7 January 2026 (Internet Archive copy of 7 January 2026). Read on 17 November 2026
- 3. Bose, SoundTouch Web API documentation, version 1.1 (first released 7 January 2026). Read on 17 November 2026
- 4. Tailwind Labs, comments by Adam Wathan on pull request 2388 of the tailwindcss.com repository (6 and 7 January 2026). Read on 17 November 2026
- 5. Tailwind Labs, Tailwind CSS licence (MIT License). Read on 17 November 2026
- 6. European Commission, Have your say, European Open Digital Ecosystems, call for evidence (6 January to 3 February 2026). Read on 17 November 2026
- 7. European Commission, Commission opens call for evidence on Open-Source Digital Ecosystems (12 January 2026). Read on 17 November 2026
- 8. European Commission, Commission boosts open and interoperable digital ecosystems for public administrations (3 June 2026). Read on 17 November 2026
- 9. Regulation (EU) 2023/2854 (Data Act), Articles 23, 25, 29, 30, 31 and 50, Official Journal of the EU. Read on 17 November 2026
- 10. Regulation (EU) 2024/2847 (Cyber Resilience Act), recital 61, Articles 13 and 69 to 71, Official Journal of the EU. Read on 17 November 2026
Change log
- Published.