Consumer Rights Wiki - User contributions [en]

Article suggestions

2026-06-07T17:21:24Z

Wownyc: article exists, search for bricks and minifigs

This page is dedicated towards providing a communal list for users to submit potential articles to feature on the wiki, and to give editors inspiration on what pages they might want to add to the wiki. If you create an article based on an entry from this list, or see that someone else has done so, please make sure to delete the row from this page in order to prevent confusion.

Sources should be inserted within the 'refs' section of the table. If using the [[Consumer_Rights_Wiki:Jargon_buster#Visual_editor_('Edit')|visual editor]], take advantage of '<nowiki/>'''insert reference'''<nowiki/>' via {{Key press|Ctrl|Shift|K}} so that the sources are quick to add to future articles. If you are using the source editor, feel free to copy and paste the formatting from other correctly formatted references on the page. The more sources you include with an article idea, the more likely it is that others will pick the article idea up and run with it, so please attempt to include a good variety of descriptive sources!

Please take note of the wiki's [[Consumer Rights Wiki:Inclusion guidelines|Inclusion criteria]] when submitting article suggestions. If you see article suggestions here which do not fit the Wiki, feel free to remove them, leaving your reasoning in an edit note.

If you are an editor looking for further inspiration to write an article, you can also check out the [[Louis Rossmann - Video Directory|Louis Rossmann video directory]] and [[Other Channels - Video Directory|other channels video directory]] for a good collections of potential articles.

==Example==
Below is an example of what an entry should appear as:
{| class="wikitable"
|+
!Company
!Summary of Incident
!Refs
|-
|[[Nintendo]]
|In 2025, the company Nintendo stripped Switch 2 consoles that used the MIG switch cartridge of all online functionality
|<ref name=":3">{{Cite web |last=Scattered Brain |date=Jun 16, 2025 |title=Soo... Nintendo banned my Switch 2 (Don't try the MIG Switch!) |url=https://www.youtube.com/watch?v=ExgYTA18_vo&t=656s |url-status=live |archive-url=https://preservetube.com/watch?v=ExgYTA18_vo |archive-date=22 Feb 2026|access-date=Jun 18, 2025 |website=[[YouTube]]}}</ref><ref name=":0">{{Cite news |last=Orland |first=Kyle |date=Jun 17, 2025 |title=Switch 2 users report online console bans after running personal game “backups” |url=https://arstechnica.com/gaming/2025/06/playing-personal-game-backups-could-get-your-switch-2-banned-by-nintendo/ |url-status=live |archive-url=http://web.archive.org/web/20251222013641/https://arstechnica.com/gaming/2025/06/playing-personal-game-backups-could-get-your-switch-2-banned-by-nintendo/ |archive-date=22 Dec 2025|access-date=Jun 19, 2025 |work=Ars Technica}}</ref>
|}

==List of incidents not yet covered==
[[Category:Sources]]

{| class="wikitable sortable"
!Company
!Summary of Incident
!Refs
|-
|194 Online Marketing Services (incl. [[Google]], [[Microsoft]], [[Meta]])
|Survey shows that more than half of websites set marketing cookies despite users opting out via Do Not Track header, Browser add-ons or by declining cookie banners. Google calles it a "misunderstanding of how their products work", Meta comments that according to the law an opt-out only prohibits selling of the data, not collecting it.
|<ref>{{Cite web |title= |url=https://www.404media.co/google-microsoft-meta-all-tracking-you-even-when-you-opt-out-according-to-an-independent-audit/}}</ref><ref>{{Cite web |title= |url=https://globalprivacyaudit.org/2026/california}}</ref>
|-
|[[8Player]]
|In early March, 2026, the Apple TV application called 8Player began displaying a notice informing users who had already paid for the app, that the app would not continue to function unless they agreed to an ongoing subscription.
The text of the notice says the following:
----Thank you for being a valued 8player user.

To keep improving the app and delivering new features, 8player is moving to a subscription model.

You can continue using the full version at no cost until April 15, 2026.

After that, activate the subscription in the app to keep full access. Your existing features will remain available, and no action is needed today.

Thank you for supporting 8player over the years.

[[:File:8player-subscription-model-notice.png]]
|
|-
|[[ABC Financial Services]]
|Manages memberships and recurring service subscriptions for other companies. Prevents customers from being able to cancel a service by locking them into a never-ending cycle of auto renewals, and not allowing the customer to opt out of auto renewal.
|
|-
|[[Acer]]
|Removed Predator/Nitro Sense Applications for laptops from their support sites somewhere in early March 2026 (Looking at wayback machine snapshots). The application is required by the laptops to be able to toggle "Turbo" mode, which applies overclocks and boosts cooling. Additionally, recent Windows update(s) (KB5083769/KB5082417) have broken the application, making users unable to use it even if you were able to install it.
|
|-
|AcuRite
|AcuRite began emailing customers last month that they’d soon have to control their devices with the "AcuRite Now" iOS and Android app, eliminating the free "My AcuRite" app, the replacement of which, "AcuRite Now" requires a subscription for features previously active in the free app.
|https://arstechnica.com/gadgets/2026/05/weather-monitoring-firm-hangs-dark-cloud-over-customers-heads-by-forcing-new-app/
|-
|Affinity / [[Canva]] page created needs editors to help
|Canva purchases [[Serif]]; the owner of perpetual license design software Affinity Publisher, Designer, and Photo on March 26th 2024. Provides a pledge to assure users that Canva will not "ruin" the suite. In October 2025, Affinity users are locked out of the community forum for a new "Creative Freedom" announcement on October 30th 2025. Complete radio silence for a whole month while they tease long term users on Twitter and Discord. Finally on October 30th 2025, the new Affinity software is announced as "free". Instead, all creative professionals that used the original software are forced to create a new Canva account to access the new Affinity and thus agree to Canva's ToS<ref name=":1">{{Cite web |date=2025-10-30 |title=Canva Terms of Use |url=https://www.canva.com/policies/terms-of-use/ |url-status=live |archive-url=http://web.archive.org/web/20260128105545/https://www.canva.com/policies/terms-of-use/ |archive-date=28 Jan 2026|website=Canva Legal Trust Center}}</ref>. Affinity redirects the pledge page to an announcement for the new software, effectively burying the original pledge<ref name=":4">{{Cite web |date=2024-03-27 |title=The Affinity and Canva Pledge |url=https://affinity.serif.com/en-us/press/newsroom/affinity-and-canva-pledge |url-status=dead |archive-url=https://web.archive.org/web/20251002083749/https://affinity.serif.com/en-us/press/newsroom/affinity-and-canva-pledge/ |archive-date=2025-10-02 |website=web.archive.org}}</ref>. Questions about Canva now being able to monetize the work of professionals to train their own AI models sold to Canva users are left unanswered. Free, but at what cost?
EDIT: Initial article has been written but needs more work, citation, and verification. [[Canva Affinity Studio adds arbitration clause|See this article here]].
|<ref name=":1" /><ref name=":4" />
|-
|[[Alibaba]]
|{{Wplink|Alibaba Group|Wikipedia entry}}
|
|-
|[[AMD]]
|Linux users now have to pay for Vivado even though it used to be free
|<ref>{{Cite web |last=Rudra |first=Sourav |date=2026-05-25 |title=AMD Pulls a Bait-and-Switch on Linux Users with Vivado Licensing Changes |url=https://itsfoss.com/news/amd-vivado-bait-and-switch-on-linux-users/ |url-status=live |access-date=2026-06-01 |website=It's FOSS}}</ref>
|-
|[[Apotheka]]
|Personal ID codes, purchase information and contact details of almost half of Estonian citizens and residents have been compromised in a mass data breach of the IT system operated by Allium UPI, a firm dealing with pharmacy and hospital products.
|<ref>{{Cite web |date=2024-04-04 |title=Cybercriminals steal data of around 700,000 Apotheka pharmacy customers |url=https://news.err.ee/1609302096/cybercriminals-steal-data-of-around-700-000-apotheka-pharmacy-customers |url-status=live |website=[[ERR]]}}</ref>
|-
|[[Apple]]
|$17 000 Apple Watch 18 karat gold edition out of support only 8 years after its introduction (not end of sale!). This means no software support, and, crucially, no repair or replacement parts. If the battery dies, the watch is but a paperweight.
|<ref>{{Cite web |title=Apple will no longer fix the $17,000 gold Apple Watch |url=https://www.theverge.com/2023/10/2/23900158/apple-watch-edition-gold-2015-obsolete-unsupported-beyonce |url-status=live |archive-url=https://web.archive.org/web/20260222211749/https://www.theverge.com/2023/10/2/23900158/apple-watch-edition-gold-2015-obsolete-unsupported-beyonce |archive-date=22 Feb 2026|website=The Verge}}</ref>
|-
|[[Apple]], [[Beats]]
|No support for Powerbeats (4th generation) despite the headphones being under 5 years from when Apple last distributed the product for sale. The product is not listed as discontinued or vintage, and by Apple's own guidelines, should be eligible for replacement parts and repair. OEM replacement eartips cannot be purchased for any Beats earphones.
|<ref>{{Cite web |title=Obtaining service for your Apple product after an expired warranty |url=https://support.apple.com/en-us/102772 |url-status=live |archive-url=http://web.archive.org/web/20260207094149/https://support.apple.com/en-us/102772 |archive-date=7 Feb 2026|access-date=2025-10-18}}</ref><ref>{{Cite web |title=Beats Repair and Service |url=https://support.apple.com/beats/repair |url-status=live |archive-url=http://web.archive.org/web/20260104000857/https://support.apple.com/beats/repair |archive-date=4 Jan 2026|access-date=2025-10-18}}</ref><ref>{{Cite web |title=Apple store search for eartips |url=https://www.apple.com/us/search/eartips?src=alp |url-status=live |archive-url=http://web.archive.org/web/20251028001314/https://www.apple.com/us/search/eartips?src=alp |archive-date=28 Oct 2025|access-date=2025-10-18}}</ref>
|-
|[[Apple]] iWork/Creator Studio
|The update that makes the iWork apps part of the new Apple Creator Studio subscription now adds tracking that is enabled by default and implemented as opt-out. The information about it is displayed in a first launch screen without any immediate way opt out, which qualifies as a dark pattern. Instead, the user has to go through a slightly convoluted path via the iPhone/iPad system settings app, and under the submenu "Apps" find each of the iWork apps and disable analytics there individually for each app. On Desktop, it is under a dedicated menu item under the "Pages"/"Numbers"/"Keynote" menu.
|<ref>{{Cite web |title=New versions of Keynote, Numbers, and Pages collect telemetry by default on iOS, iPadOS, and macOS |url=https://www.reddit.com/r/ios/comments/1qq7q9m/new_versions_of_keynote_numbers_and_pages_collect/ |archive-url=https://web.archive.org/web/20260223032029/https://old.reddit.com/r/ios/comments/1qq7q9m/new_versions_of_keynote_numbers_and_pages_collect/ |archive-date=23 Feb 2026}}</ref>
|-
|[[archive.today]] / archive.ph (Web Archival Service)
|The website used [[JavaScript]] embedded into the website code to conduct a DDOS attack from users' devices against a blogger who has voiced criticism of the service in the past. This may make also cause legal issues for users.
NOTE: A similar technique has previously been used by Chinese search giant [[Baidu]], so we might want to create a category or tag for this type of thing

ADDENDUM: This page was reported to have been changing the information displayed in some archived screenshots, such as the author who published particular articles.
|<ref>{{Cite web |last=Kirchner |first=Malte |last2=Kunz |first2=Dr. Christopher |date=10 Feb 2026 |title=Archive.today: Operator uses users for DDoS attack |url=https://www.heise.de/en/news/Archive-today-Operator-uses-users-for-DDoS-attack-11171455.html |url-status=live |archive-url=http://web.archive.org/web/20260212060655/https://www.heise.de/en/news/Archive-today-Operator-uses-users-for-DDoS-attack-11171455.html |archive-date=12 Feb 2026 |website=heise}}</ref><ref>{{Cite web |last=LMG Clips |title=Wikipedia Banned 690,000 Archive Links - LMG Clips |url=https://youtu.be/rrnFUvFGf5A?si=32JRogu2ID9xykHd |access-date=2026-03-03 |website=LMG Clips on YouTube - Wikipedia Banned 690,000 Archive Links}}</ref>
|-
|[[ASUS]] (ROG)
|Releases bios updates via windows executable, meaning that you can't update your bios to the latest version to amend a security vulnerability or fix an issue unless you're running microsoft windows. The windows executable simply extracts a binary file, that you can drop on a thumb drive. This could be easily done via direct download to support other operating systems.
|
|-
|[[AutoAuth]]
|'''AutoAuth''' represents a significant shift toward "repair-by-subscription," where owning a vehicle no longer guarantees the right to maintain it. By placing a digital firewall between the owner and the car’s computer, AutoAuth forces independent shops and DIY enthusiasts to pay recurring access fees and register their personal data with a third-party gatekeeper just to perform basic maintenance, such as electronic parking brake retractions or oil life resets.
|
|-
|[[Backblaze]]
|Backblaze makes canceling a subscription needlessly complex and convoluted. This is referring to their personal backup solution, I do not know how other subscriptions are handled.
To cancel a Backblaze subscription after 30 days you are required to delete your account. A full refund can apparently be requested within that window
[https://www.backblaze.com/company/policy/payments-and-refunds "Payments and refunds"].
If after 30 days you decide to cancel or switch to a different service after your subscription ends you have the following options:
1. Wait until the end of your subscription to cancel.
2. Delete your account, removing your access to the service prematurely.
There is no "do not renew" option, even removing your payment information is not possible. In my opinion it should be possible to enjoy the access you paid for without having to remember to cancel a year or two later.
[https://help.backblaze.com/hc/en-us/articles/217665728-Canceling-and-Deleting-a-Backblaze-Account "Canceling and deleting a Backblaze account"]
|
|-
|[[Bayer]]
|[[wikipedia:Bayer|Wikipedia]]. See [[Monsanto]]
|
|-
|[[Benjamin]]
|Offerwall phone app that pays users money for various tasks- such as watching ads, or downloading and using software. After years of user satisfaction, in late 2025, the company first put a 2 month moratorium on users' ability to withdraw their earned money, then rolled out a massive wave of enshittification features, the most egregious of which, is a "withdrawl queue", where withdrawing your earnings is placed into a queue with no visible progress. No days, no queue tracker, many members have been waiting over 3 months for their withdrawls to be processed, on a feature listed as "instant withdrawl". Various policies also implemented that would completely void a user's earned money, mainly inactivity but also many baseless random user bans (many of which were reversed). There are hundreds of frustrated user testimonials on reddit (https://www.reddit.com/r/benjaminone/).
|
|-
|Berlin
|City of Berlin installs security cameras that alerts authorities about people who are "loitering without reason".
|<ref>{{Cite web |last=Krempl |first=Stefan |date=10 Mar 2026 |title=Surveillance in Berlin: When AI reports "loitering without reason" |url=https://www.heise.de/en/news/Surveillance-in-Berlin-When-AI-reports-loitering-without-reason-11206420.html |website=heise}}</ref>
|-
|[[Better Business Bureau]] (BBB)
|Users who have been wronged and even scammed by companies have recently started reporting that the BBB has ignored, rejected, misclassified, closed prematurely or taken down their valid, BBB compliant, complaints for no apparent reason<ref>{{Cite web |date=2026-03-29 |title=Better Business Bureau Reviews |url=https://www.trustpilot.com/review/bbb.org |url-status=live |access-date=2026-03-29 |website=Trustpilot}}</ref>. Attempts to remedy the situation often result in unanswered/ignored emails and ghosting. Companies with large percentages of unresolved complaints often get an A+ rating (which basically contradicts the BBB's own guidelines). This is especially true when it comes to paying BBB member companies, but is often also the case with non member companies. A Redditors explained that a company can easily buy an A+ BBB rating by paying the BBB<ref>{{Cite web |title=Waste Managment sent an ad disguised as a bill |url=https://www.reddit.com/r/ColoradoSprings/comments/1l6hr18/comment/mwpys3o/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button |url-status=live |access-date=2026-03-30 |website=Reddit}}</ref> or by paying a lawyer to threaten to sue the BBB for defamation.
|
|-
|[[Best Buy]]
|In late 2025, BestBuy added [https://www.bestbuy.com/site/help-topics/pricing-message/pcmcat748302046647.c?id=pcmcat748302046647#:~:text=Our%20%E2%80%9CComparable%20Value%E2%80%9D%20(Comp,retailers%20or%20e%2Dcommerce%20companies. "Comparable Value"] as means of comparing values of products that is of equivalent value to other products sold by manufacturers, 1st party, or 3rd party vendors. Changes to their pricing model has made it to where it is more difficult to determine overall value of a product compared to MSRP.
|<ref>{{Cite web |last=Support |first=Best Buy |date=2025-01-24 |title=Pricing: Promotions |url=https://www.bestbuy.com/site/help-topics/pricing-message/pcmcat748302046647.c?id=pcmcat748302046647#:~:text=Our%20%E2%80%9CComparable%20Value%E2%80%9D%20(Comp,retailers%20or%20e%2Dcommerce%20companies. |url-status=live |access-date=2026-02-24 |website=Best Buy}}</ref>
|-
|[[Blackview]]
|[https://www.blackview.hk Blackview], a technology brand that originally specialized in rugged outdoor phones more info at [https://www.blackview.hk/about-blackview "About us]"
Certain Phones have been hit with advertisements from the App called "System message" which is baked in the OS, "Allow Notification dots" can be disabled however "All System message notifications" and neither "Push" notifications cannot be disabled by the user. The App cannot be disabled nor uninstalled, it can be forced stopped and set the battery restriction option to "restricted". I [[User:SolidSnakePliskin|SolidSnakePliskin]] creating this entry have seen this happen firsthand on 1st April 2026 on my Blackview Model Number: N6000 (EEA) Purchased on [https://web.archive.org/web/20260401174012/https://www.amazon.it/dp/B0CCXBNTWR Amazon Italy]. OS Details: Android Version 13 (Security Update November 5, 2025) & DokeOS 3.1. Further More other Reddit users complaining [https://old.reddit.com/r/blackview/comments/1mo441x/get_rid_of_system_notification_that_contains_ads/ here].
|
|-
|[[Bluesky]]
|Introduced ID check for Direct Messaging to comply with laws in certain states and abroad, despite both the company and community being against it.
Its legal docs ([https://bsky.social/about/support/tos ToS], [https://bsky.social/about/support/privacy-policy PP], [https://bsky.social/about/support/community-guidelines CG]) need [[JavaScript|JS]] to be viewed by humans, however this seems more of an oversight than deliberate
|
|-
|[[Carvana]]
|Saying cars that have been in accidents have not; Lies about inspection and does not replace brake pads even when worn down. Non-refundable $1,500 shipping fee. See [https://www.youtube.com/watch?v=r9yhOeTUEo4 Louis Rossmann's video]
|
|-
|[[Chuwi]]
|Misleading consumers by falsifying the specsheet of one of their latest laptops, and repeatedly threatened one of the online publications that wrote an article of their alleged misdeeds.
|<ref>{{Cite web |last=Leitner |first=Simon |date=2026-03-12 |title=CPU fraud, next round: Chuwi CoreBook Plus with supposed AMD Ryzen 5 7430U also affected |url=https://www.notebookcheck.net/CPU-fraud-next-round-Chuwi-CoreBook-Plus-with-supposed-AMD-Ryzen-5-7430U-also-affected.1248660.0.html |url-status=live |archive-url=https://web.archive.org/web/20260313120720/https://www.notebookcheck.net/CPU-fraud-next-round-Chuwi-CoreBook-Plus-with-supposed-AMD-Ryzen-5-7430U-also-affected.1248660.0.html |archive-date=2026-03-13 |access-date=2026-03-12 |website=Notebookcheck}}</ref>
|-
|[[Cloudary Holdings Limited / Webnovel]]
|Terms of service with binding Arbitration.
|<ref>{{Cite web |title=Webnovel ToS |url=https://www.webnovel.com/terms_of_service |url-status=live |archive-url=http://web.archive.org/web/20260101204816/https://www.webnovel.com/terms_of_service |archive-date=1 Jan 2026}}</ref>
|-
|[[Devolo]]
|Devolo switches off servers and removes their app from stores for their "Home Control" system, thus severely reducing the functionality of their devices (apparently Z-Wave-based).
|<ref>{{Cite web |title=IT-News für Profis |url=https://www.golem.de/news/weiterbetrieb-verursacht-weitere-kosten-devolo-macht-smart-home-system-zum-grossteil-unbrauchbar-2508-199409.html |url-status=live |archive-url=http://web.archive.org/web/20251210052941/https://www.golem.de/news/weiterbetrieb-verursacht-weitere-kosten-devolo-macht-smart-home-system-zum-grossteil-unbrauchbar-2508-199409.html |archive-date=10 Dec 2025|website=Golem |language=de}}</ref>
|-
|[[DeviantArt]]
|DeviantArt launched in 2000 and quickly became a household name among digital artists. [https://www.wix.com/press-room/home/post/wix-acquires-deviantart-pairing-wix-capabilities-with-global-creative-community But in 2017 WiX] bought the website and in 2022 had made all art on it's site liable to be training data by default. They then back peddled and then set all art to noai by default. Now they are moving basic functions to be behind their paywall. [https://www.deviantart.com/razorstargazer/journal/Deviantart-is-the-worst-website-ever-created-1309667089 Ones that were free.]
|<ref>{{Cite web |title=The AI Controversy on DeviantArt: How a Creative Paradise Became a Battleground |url=https://expertbeacon.com/the-ai-controversy-on-deviantart-how-a-creative-paradise-became-a-battleground/ |url-status=live}}</ref><ref>{{Cite web |title=Wix Acquires DeviantArt, Pairing Wix Capabilities with Global Creative Community |url=https://www.wix.com/press-room/home/post/wix-acquires-deviantart-pairing-wix-capabilities-with-global-creative-community |url-status=live}}</ref>
|-
|DotPe cyber-sec negligence
|In 2024, an Indian company that provides digital services to food-chains got trivially hacked/cracked, allowing anyone to get customer data and company revenue-stats across many countries
|<ref>https://web.archive.org/web/20240923081639/https://peabee.substack.com/p/whats-inside-the-qr-code-menu-at</ref>
|-
|[[Digital Europe]] (lobby organization consisting of [[Microsoft]], [[Google]], [[Amazon]], and [[Meta]])
|Group lobbied to keep datacenter emissions secret from consumers via confidentiality clause that was adopted almost verbatim by the Eurpean Comission, intentionally keeping consumers in the dark about the environmental impact of the products they use.
|<ref>{{Cite web |title= |url=https://www.theguardian.com/technology/2026/apr/17/microsoft-us-tech-firms-lobbied-eu-secrecy-rules-datacentre-emissions}}</ref>
|-
|[[E621]]
|Terms of service that require agreement to forced arbitration to use the website.
|<ref>{{Cite web |date=2025-10-02 |title=E621 |url=https://e621.net/ |url-status=live |archive-url=http://web.archive.org/web/20260128164339/https://e621.net/ |archive-date=28 Jan 2026|website=E621}}</ref>
|-
|[[EcoVac]]
|Vacuum cleaner robots produced by company 'EcoVac' were found vulnerable to hacking over bluetooth allowing for remote control and access to camera feed. Security researcher Dennis Giese notified the company in December of 2023. In August of 2024, the issue was described by the company as "extremely rare in typical user environments and require specialized hacking tools and physical access to the device."
|<ref>{{Cite web |last=Fell |first=Julian |date=2024-10-04 |title=We hacked a robot vacuum — and could watch live through its camera - ABC News |url=https://www.abc.net.au/news/2024-10-04/robot-vacuum-hacked-photos-camera-audio/104414020 |url-status=live |archive-url=http://web.archive.org/web/20251128025250/https://www.abc.net.au/news/2024-10-04/robot-vacuum-hacked-photos-camera-audio/104414020 |archive-date=28 Nov 2025|access-date=2025-09-10 |website=ABC News}}</ref><ref>{{Cite web |last=Franceschi-Bicchierai |first=Lorenzo |date=2024-08-09 |title=Ecovacs home robots can be hacked to spy on their owners, researchers say {{!}} TechCrunch |url=https://techcrunch.com/2024/08/09/ecovacs-home-robots-can-be-hacked-to-spy-on-their-owners-researchers-say/ |url-status=live |archive-url=https://web.archive.org/web/20260222212044/https://techcrunch.com/2024/08/09/ecovacs-home-robots-can-be-hacked-to-spy-on-their-owners-researchers-say/ |archive-date=2026-02-22 |access-date=10 Aug 2024}}</ref><ref>{{Cite web |last=Franceschi-Bicchierai |first=Lorenzo |date=2024-08-15 |title=Lorenzo Franceschi-Bicchierai on X: "Finally, Ecovacs responds to the researchers' findings, saying it won't fix the bugs. |url=https://x.com/lorenzofb/status/1823774980460388675 |url-status=live |archive-url=http://web.archive.org/web/20241108194816/https://x.com/lorenzofb/status/1823774980460388675 |archive-date=8 Nov 2024}}</ref>
|-
|[[Elegoo Centauri Carbon|Elegoo]]
|The Elegoo Centauri Carbon 3d printer has been proven to use open source Klipper software which requires them to publish their changes to the code.
|<ref>{{Cite web |date=2025-08-28 |title=PSA: Elegoo Centauri Carbon & GPL Compliance |url=https://freethecode.lol/ |url-status=live |archive-url=http://web.archive.org/web/20251206142736/https://freethecode.lol/ |archive-date=6 Dec 2025|access-date=2025-08-28 |website=PSA: Elegoo Centauri Carbon & GPL Compliance}}</ref>
|-
|[[Ericcson]]
|Data Breach March 2026
|
|-
|[[FBI]]
|FBI buys location data of US citizens
|<ref>{{Cite web |title=FBI is buying location data to track US citizens, director confirms |url=https://techcrunch.com/2026/03/18/fbi-is-buying-location-data-to-track-us-citizens-kash-patel-wyden/ |url-status=live |website=[[TechCrunch]]}}</ref>
|-
|[[Foxconn]]
|Foxconn is an electronics manufacturer with various human rights violations on it's record. They've also convinced the government to use eminent domain to take people's property to build factories, that never end up using the factories.
|
|-
|[[Foxit Reader]]
|Updater uses dark pattern to trick unsuspecting users into installing a trial version of their paid product. The checkbox is enabled again by default with each update in the hope that the user misses it by accident at some point.
|
|-
|[[Gaggia]]
|Between 2015 to 2019, the redesigned Gaggia Classic removed the traditional three-way solenoid valve. The valve was restored in the 2019 Gaggia Classic Pro after criticism and backlash from the espresso enthusiast community.
|<ref>{{Cite web |last=Waddell |first=Kelsey |date=2023-03-23 |title=Gaggia Classic vs Pro: A Closer Look at the Differences |url=https://www.roastycoffee.com/gaggia-classic-vs-pro/ |website=Roasty Coffee}}</ref>
|-
|[[General Motors|GM]]
|GM originally released the EV1 in 1996 on a lease program, and then instead of selling the much loved used/leased vehicles to consumers, they decided to crush the grand majority of them. Very few surviving examples can be found today, with most in private collections or at universities.
Because it was seen as a failure to major auto manufacturers, It would take over a decade before another EV was produced in the United States.
|
|-
|Google TLS Changes
|Google's new requirements to certificate authorities require separate authority/signing chains to be used to issue Server Authentication and Client Authentication certificates. Therefore, starting 11 February 2026, Let's Encrypt will no longer include the Client Authentication EKU on default certificates
|
|-
|[[Google]] ([[Android]])
|Google apparently plans to reduce the interval of publishing source code of security patches they consider non-critical. This is another blow to the custom ROM community.
Right now we don't have these incidents organised chronologically, maybe we should have a table with a timeline of measures Google takes to enshittify and close down Android (more APIs moved to Play Services, Developer verification, withholding AOSP device trees for Pixel devices to mess with [[GrapheneOS]], now delayed source code disclosure). What's worst, they always cite safety as a reason.
|<ref>{{Cite web |title=Exclusive: Google wants to make Android phones safer by switching to ‘risk-based’ security updates |url=https://www.androidauthority.com/android-risk-based-security-updates-3597466/ |archive-url=http://web.archive.org/web/20260107025310/https://www.androidauthority.com/android-risk-based-security-updates-3597466/ |archive-date=7 Jan 2026 |website=Android Authority}}</ref>
|-
|[[Google]], [[Mozilla]], [[Apple]], [[Microsoft]], but largely Google-led
|Google Chrome, Mozilla Firefox, and Safari are removing XSLT 1.0 support, which could break critical parts of government's websites worldwide<ref>{{Cite web |last=Dimant |first=Dimitrii "Mamut" |date=2025-08-10 |title=XSLT removal will break multiple government and regulatory sites across the world #11582 |url=https://github.com/whatwg/html/issues/11582 |url-status=live |archive-url=http://web.archive.org/web/20260211221059/https://github.com/whatwg/html/issues/11582 |archive-date=11 Feb 2026|access-date=2025-10-25 |website=Github (specifically the Web Hypertext Application Technology Working Group's HTML standards repo, controlled by Mozilla, Google, Microsoft and Apple)}}</ref>. There are valid security reasons for them to want to stop supporting this 1999-era standard, however they have had 26+ years to update to a newer standard (such as the 2017-era 3.1 standard, which is backwards compatible and would allow these sites to continue to work<ref>{{Cite web |date=2017-03-21 |title="XML Path Language (XPath) 3.1: W3C Recommendation 21 March 2017" |url=https://www.w3.org/TR/xpath-31/ |url-status=live |archive-url=http://web.archive.org/web/20260116015839/https://www.w3.org/TR/xpath-31/ |archive-date=16 Jan 2026|website=W3C}}</ref>). The single unpaid developer maintaining these libraries has more or less retired after getting flooded with impossible to satisfy security requests from these companies<ref>{{Cite web |last=Wellnhoffer |first=Nick |date=2025-05-08 |title=Triaging security issues reported by third parties |url=https://gitlab.gnome.org/GNOME/libxml2/-/issues/913 |url-status=live |archive-url=http://web.archive.org/web/20260131231248/https://gitlab.gnome.org/GNOME/libxml2/-/issues/913 |archive-date=31 Jan 2026|access-date=2025-10-25 |website=gitlab.gnome.org}}</ref>. There is an existing project called XRUST to implement the 3.1 standard<ref>{{Cite web |date=2025-05-09 |title=XRust: XPath, XQuery, and XSLT for Rust |url=https://gitlab.gnome.org/World/Rust/markup-rs/xrust |url-status=live |archive-url=http://web.archive.org/web/20260204085435/https://gitlab.gnome.org/World/Rust/markup-rs/xrust |archive-date=4 Feb 2026|access-date=2025-10-14 |website=gitlab.gnome.org}}</ref>, which is 2/3rds of the way through supporting all the features of 1.0 - the XSLT part fully supports all the 1.0 features at this point. XSLT is part of the W3C Consortium's open web standards for formatting and presenting XML, and is also how RSS works, so RSS feeds would stop working as well, disrupting the livelihoods of podcasters<ref>{{Cite web |last=Rijo |first=Luis |date=2025-08-20 |title=Google targets RSS feeds in new XSLT removal proposal |url=https://ppc.land/google-targets-rss-feeds-in-new-xslt-removal-proposal/ |url-status=live |archive-url=https://web.archive.org/web/20260222212228/https://ppc.land/google-targets-rss-feeds-in-new-xslt-removal-proposal/ |archive-date=22 Feb 2026|access-date=2025-10-14 |website=PPC-Land}}</ref>. This has led to questions of who owns the web - the public (including the government) who paid for and laid down the highways / web infrastructure - or a handful of large corporations? <ref>{{Cite web |last=Branscombe |first=Mary |date=2025-09-01 |title=XSLT Debate Leads to Bigger Questions of Web Governance |url=https://thenewstack.io/xslt-debate-leads-to-bigger-questions-of-web-governance/ |url-status=live |archive-url=http://web.archive.org/web/20260131231310/https://thenewstack.io/xslt-debate-leads-to-bigger-questions-of-web-governance/ |archive-date=31 Jan 2026|access-date=2025-10-14 |website=The New Stack}}</ref>
|
|-
|[[Google Photos]]
|Google Makes it more difficult to manage photos within your google drive account through third party applications, including open source software running on linux.
This makes it incredibly frustrating to clear space in google drive if you've exceeded the space limits.
|<ref>https://github.com/gilesknap/gphotos-sync-discussion/discussions/1</ref>
|-
|[[GoPro]] Hero 12
|GoPro Hero 12 requires the GoPro app to be installed before you can use the camera. Many currently used devices are not compatible with the app, therefore making use of the camera difficult to impossible for new owners or upon camera factory reset. There's also the question of what data the app collects and whether it requires login and or camera activation.
|
|-
|[[Honda]]
|moved the garage door opener from a button on the mirror to a [[Pay-walling|paywall]] [[subscription service]]
|<ref>https://reddit.com/r/mildlyinfuriating/comments/1sd54jo/replaced_my_honda_with_a_new_one_after_an/</ref>
|-
|[[Hyundai]] (BlueLink)
|Hyundai ads in-car advertisements for subscription services, while you're driving, after telling you not to look at the screen while driving.
The advertisement is a full page of text, that you can't either enable or disable while you're driving. Your only options are to (A) select later, to delay the ad for another driving session, or (2) Pull over and park your car so you can (C) enable the feature at $10/mo or (iii) dig through settings menus to figure out how to disable the message permanently (which will probably only be actually permanent until the battery in the car dies).
BlueLink appears to be marketing lingo for their cell-phone-linked remote start/stop, lock/unlock, and climate control features. The only feature that should actually need a cellular subscription appears to be stolen vehicle recovery.
|<ref>{{Cite web |last=Green |first=Hank |date=2026-16-04 |title=Should I Sue Hyundai? |url=https://www.youtube.com/watch?v=SQ1RUyOF2Rk |url-status=live |website=Youtube}}</ref> <ref>https://connected-mobility.hyundai.com/what-we-do/connected-car-services/bluelink</ref>
|-
|[[Internet radios]]
|I'd like a page where I can share information about internet radios "openness." Few allow you to enter a radio station's URL (which I would consider the least intrusive option). Most depend on third-party websites or apps; [https://www.sangean.com/uk/blog/149 some of which have already bricked devices].
|
|-
|[[itch.io]], [[Night School Studios]], [[Netflix]]
|In September 2024, users who purchased the game Oxenfree on itch.io were warned that the game was going to be pulled from the platform on October 1st. Consumers would not be able to download the installers after this date, so they would lose access unless they had them backed up. Users speculated that Netflix, the parent company of the development studio, had ordered the move; however, no response from Netflix or the developers was ever published. This is particularly notable because it is against itch.io's terms of service: "Users shall retain a license to this content even after the content is removed from the Service."
|<ref>{{Cite web |last=itch corp |date=15 Apr 2023 |title=itch.io Terms of Service |url=https://itch.io/docs/legal/terms |url-status=live |archive-url=https://web.archive.org/web/20240907004719/https://itch.io/docs/legal/terms |archive-date=7 Sep 2024 |access-date=27 Jun 2025 |website=itch.io}}</ref> <ref>{{Cite web |last=ShawnS |date=31 Jan 2025 |title=OXENFREE |url=https://delistedgames.com/oxenfree/ |url-status=live |archive-url=https://web.archive.org/web/20250321070400/https://delistedgames.com/oxenfree/ |archive-date=21 Mar 2025 |access-date=27 Jun 2025 |website=Delisted Games}}</ref> <ref>{{Cite web |last=Colp |first=Tyler |date=9 Sep 2024 |title=Another reminder that your digital library isn't forever: Oxenfree will be completely removed from Itch.io next month |url=https://www.pcgamer.com/games/adventure/another-reminder-that-your-digital-library-isn-t-forever-oxenfree-will-be-completely-removed-from-itch-io-next-month/ |url-status=live |archive-url=https://web.archive.org/web/20250523111125/https://www.pcgamer.com/games/adventure/another-reminder-that-your-digital-library-isn-t-forever-oxenfree-will-be-completely-removed-from-itch-io-next-month/ |archive-date=23 May 2025 |access-date=27 Jun 2025 |website=PC Gamer}}</ref>
|-
|[[The Japan Times|Japan Times, The]]
|The Japan Times uses the DMCA to take down an open source study resource for the Genki and Quartet workbooks.
|<ref>{{Cite web |last=Clydesdale |first=Seth |date=2025-09-11 |title=Important Information Regarding Genki and Quartet Study Resources |url=https://ko-fi.com/post/Important-Information-Regarding-Genki-and-Quartet-D1D21L4B1S |url-status=live |archive-url=http://web.archive.org/web/20251116072121/https://ko-fi.com/post/Important-Information-Regarding-Genki-and-Quartet-D1D21L4B1S |archive-date=16 Nov 2025}}</ref><ref>{{Cite web |title=Update Regarding Genki and Quartet Study Resources DMCA Situation |url=https://ko-fi.com/post/Update-Regarding-Genki-and-Quartet-Study-Resources-Y8Y21M1F5E |url-status=live |archive-url=http://web.archive.org/web/20251115073152/https://ko-fi.com/post/Update-Regarding-Genki-and-Quartet-Study-Resources-Y8Y21M1F5E |archive-date=15 Nov 2025}}</ref><ref>{{Cite web |date=2025-10-03 |title=All Exercises for Genki/Quartet Study Resources Have Been Removed |url=https://ko-fi.com/post/All-Exercises-for-GenkiQuartet-Study-Resources-Wi-R6R81M8LLN |archive-url=http://web.archive.org/web/20251113045244/https://ko-fi.com/post/All-Exercises-for-GenkiQuartet-Study-Resources-Wi-R6R81M8LLN |archive-date=13 Nov 2025}}</ref>
|-
|[[Kangaroo]]
|A home security camera company that locks local hardware features behind software subscriptions and paywalls that ultimately could work without external service. Access to local storage playback via the app is locked behind a paywall; see reviews. "cooldown" periods provide a risk to security as motion detection does not activate until after a fixed period of time on no-subscription plans with clips that only capture 12 seconds of recording, this was not always the case.
|<ref>{{Cite web |last=Delaney |first=John |date=2021-11-09 |title=Kangaroo Indoor + Outdoor Cam Review |url=https://www.pcmag.com/reviews/kangaroo-indoor-plus-outdoor-cam |url-status=live |archive-date=2024-08-11 |access-date=2026-04-01 |website=PCMag}}</ref><ref>https://www.bestbuy.com/product/kangaroo-indoor-outdoor-wired-1080p-security-camera-white/J3QLYYW64G/sku/6506997/reviews?pageSize=20</ref>
|-
|[[Klarna]]
|A German consumer rights association reports that payment provider Klarna requests access to users' bank accounts for payment purposes, but instead of just initiating transactions as the user expects, it also scans the complete list of transactions on the user's bank account for advertising purposes and also forwards that data to third parties. Klarna also faces criticism for encouraging debt by offering "buy now, pay later" schemes.
|<ref>{{Cite web |title= |url=https://www.spiegel.de/netzwelt/apps/klarna-verbraucherschuetzer-kritisieren-konto-schnueffelei-bei-zahlungsdienstleister-a-de915cd3-997e-4b39-ad67-bb5d22969635}}</ref><ref>{{Cite web |title= |url=https://www.chip.de/news/Warnung-vor-KlarnaVebraucherschuetzer-sind-besorgt_185654845.html}}</ref><ref>{{Cite web |title= |url=https://www.computerbild.de/artikel/cb-News-Sicherheit-Verbraucherzentrale-warnt-Klarna-analysiert-Kontodaten-39229147.html}}</ref>
|-
|[[Kohls]]
|There is no option to delete your account on their website
|
|-
|[[KOSA]]
|KOSA claims to make kids safer, but it’s really a dangerous censorship bill that would give the U.S. government unprecedented control over the internet. This would put youth in danger by preventing them from accessing potentially life-saving resources.
|<ref>{{Cite web |last=Fight for the Future |first= |date=2026-01-24 |title=Reject online censorship. Tell lawmakers to oppose KOSA! |url=https://www.stopkosa.com/ |url-status=live |archive-url= |archive-date= |access-date=2026-01-24 |website=Stop KOSA}}</ref><ref>https://web.archive.org/web/20250228145348/https://www.houstonchronicle.com/news/houston-texas/education/article/Katy-ISD-blocks-LGBTQ-resources-suicide-16647274.php</ref>
|-
|[[LBRY]] Foundation, [[Odysee]]
|Community first decentralization & Odysee's plan to enable censorship by switching away from the opensource LBRY network.
|<ref>{{Cite web |title=The LBRY Foundation |url=https://lbry.org/ |url-status=live |archive-url=http://web.archive.org/web/20260211161516/https://lbry.org/ |archive-date=11 Feb 2026|access-date=2025-08-08 |quote=The LBRY community invites everyone to join us in building a more free and open way to share content and information online.}}</ref><ref name=":2">{{Cite news |last=Watson |first=RT |date=6 Jun 2024 |title=Decentralized YouTube alternative Odysee acquired by Forward Research despite content concerns |url=https://www.theblock.co/post/298888/decentralized-youtube-alternative-odysee-acquired-by-forward-research-despite-content-concerns |url-status=live |archive-url=http://web.archive.org/web/20251127094918/https://www.theblock.co/post/298888/decentralized-youtube-alternative-odysee-acquired-by-forward-research-despite-content-concerns |archive-date=27 Nov 2025|access-date=16 Aug 2025 |work=The Block}}</ref><ref>{{Cite journal |last=Li |first=Jun |last2=Grintsvayg |first2=Alex |last3=Kauffman |first3=Jeremy |last4=Fleming |first4=Charles |date=2020 |title=LBRY: A Blockchain-Based Decentralized Digital Content Marketplace |url=https://ieeexplore.ieee.org/document/9126007 |url-status=live |journal=2020 IEEE International Conference on Decentralized Applications and Infrastructures (DAPPS) |location=Oxford, UK |publisher=IEEE |doi=10.1109/DAPPS49028.2020.00005 |isbn=978-1-7281-6978-1 |url-access=registration |archive-url=http://web.archive.org/web/20250825221749/https://ieeexplore.ieee.org/document/9126007/ |archive-date=25 Aug 2025 |via=IEEE Xplore}}</ref>
|-
|[[LexisNexis]]
|Data breach March 2026
|
|-
|[[LG]]
|LG discontinued its LG Bluetooth Remote app (including plugins such as "btc4") making it non-public on the Play Store and making Bluetooth controllable devices (like for example the CM2630B) half as useful, without even publishing neither the protocol used to control such devices nor the source code of the app.
|
|-
|Linkedin
|LinkedIn has been caught running a massive, silent operation that scans the local computers of its visitors. Every time a user visits <code>linkedin.com</code> using a Chromium-based browser (Chrome, Edge, Brave), a hidden JavaScript program executes to check for the presence of over '''6,000 specific browser extensions.'''
|https://www.youtube.com/watch?v=mHj6IvBmlpU
https://browsergate.eu/
|-
|[[Lowe's]]
|Lowe's uses flock cameras and other AI powered cameras to collect data and build a profile on "prospective, current, or former Lowe's customers". Their cameras point away from their stores.
|<ref>{{Cite web |last=Koebler |first=Jason |date=6 Aug 2025 |title=Home Depot and Lowe's Share Data From Hundreds of AI Cameras With Cops |url=https://www.404media.co/home-depot-and-lowes-share-data-from-hundreds-of-ai-cameras-with-cops/ |url-status=live |archive-url=http://web.archive.org/web/20260216173226/https://www.404media.co/home-depot-and-lowes-share-data-from-hundreds-of-ai-cameras-with-cops/ |archive-date=16 Feb 2026|access-date=15 Sep 2025 |website=404 Media}}</ref><ref>{{Cite web |date=26 Aug 2025 |title=Lowe’s U.S. Privacy Statement |url=https://www.lowes.com/l/about/privacy-and-security-statement |url-status=live |archive-url=http://web.archive.org/web/20251228013530/https://www.lowes.com/l/about/privacy-and-security-statement |archive-date=28 Dec 2025|access-date=15 Sep 2025 |website=Lowe's}}</ref>
|-
|[[Marquis]]
|Data Breach March 2026
|
|-
|[[Meta]] and [[YouTube]]
|In a recent trial Meta and Google were found liable for making there social media platforms addictive and harmful
|<ref>{{Cite web |title=Jury finds Meta and Google negligent in social media harms trial |url=https://www.npr.org/2026/03/25/nx-s1-5746125/meta-youtube-social-media-trial-verdict |url-status=live}}</ref><ref>{{Cite web |title=Campaigners welcome Meta and YouTube's defeat in landmark social media addiction trial |url=https://www.bbc.com/news/articles/c747x7gz249o |url-status=live}}</ref><ref>{{Cite web |title=Meta and YouTube Found Negligent in Landmark Social Media Addiction Case |url=https://www.nytimes.com/2026/03/25/technology/social-media-trial-verdict.html |url-status=live}}</ref>
|-
|[[Microsoft]]
|Microsoft's Android keyboard app SwiftKey set to make it impossible to backup user data without a Microsoft Account, backups must be stored in Microsoft cloud
|<ref>{{Cite web |last=Roth |first=Emma |date=18 Mar 2026 |title=SwiftKey will soon require a Microsoft account to save your typing info. |url=https://www.theverge.com/tech/896859/swiftkey-will-soon-require-a-microsoft-account-to-save-your-typing-info}}</ref>
|-
|[[Microsoft]]
|Locked the developers of Windscribe, Veracrypt, and, Wireguard out of their accounts
|
|-
|[[Microsoft]] Rewards
|Used to be a good program, but over the last few years they've implemented a number of anti-user policies including extensive cool-downs for earning points on Bing, and making it more difficult to redeem points. There are multiple reports on r/microsoftrewards of people getting banned or restricted when they have over $100 worth of points that they are trying to redeem. They've also removed points opportunities that used to be interesting and engaging.
|
|-
|[[Minut]]
|Minute sells sensors and alarms. They released an alarm (Point) on kickstarter that long after release got a firmware update adding forced subscription if more than one person wanted to use the alarm.
|<ref>https://www.kickstarter.com/projects/minut/pointthe-friendly-home-alarm</ref>
<ref>https://www.minut.com/</ref>
|-
|[https://www.mobvoi.com/us Mobvoi/Ticwatch]
|Written with partially help of AI
Mobvoi has gained a reputation for a "launch and forget" pattern, where devices are marketed with the promise of future software updates that often arrive years late or are cancelled entirely. This pattern—most notable in the two-year delay of the Wear OS 3 update—frequently leaves consumers with hardware that lacks core advertised features, such as Google Assistant. Additionally, the company faces criticism for restrictive warranty policies and a difficult return process that often places the financial burden of shipping and replacement on the user. Once the app was abandoned subscription was still available for purchases but was unusable
|https://9to5google.com/2025/12/05/mobvoi-ticwatch-wear-os-dead/
https://www.androidcentral.com/wearables/mobvoi-explains-wear-os-3-holdup
https://www.pcmag.com/news/another-wear-os-smartwatch-maker-appears-to-have-given-up
https://www.xda-developers.com/mobvoi-lying-ticwatch-hardware/
|-
|Multiple
|Several legal cases involving forced arbitration in some manner; many of these relate to other anticonsumer practices, such as when Wells Fargo illegally opened up ~3.5M fake checking and credit accounts in customers' names. Highly advised to deeply scrub for supplementary sources.
|<ref>{{Cite web |date=Apr 16, 2019 |title=Fact Sheet: Cases Tossed Out of Court Because of Forced Arbitration Causes and Class Action Bans |url=https://www.centerjd.org/content/fact-sheet-cases-tossed-out-court-because-forced-arbitration-causes-and-class-action-bans#_ftn1 |access-date=Feb 12, 2026 |website=Center for Justice & Democracy at New York Law School |url-status=live |archive-url=http://web.archive.org/web/20251013145327/https://centerjd.org/content/fact-sheet-cases-tossed-out-court-because-forced-arbitration-causes-and-class-action-bans |archive-date=13 Oct 2025}}</ref>
|-
|[[MuseGroup]] (MuseSounds)
|Releasing more and more subscription sound packs while previously released one-time purchase sound packs are full of bugs/issues and have gone without updates for sometimes over a year. They have also increased the price of one-time purchase packs by about 500% while still providing no additional or improved functionality.
They also added unsolicited popups advertising their paid sound packs at startup of the open source MuseScore application, as well as buttons and commands for their cloud service to the home screen, which cannot be disabled. They previously ran into controversy when changing the privacy policy of Audacity and tried to add tracking. The closed-source MuseHub application (which is required to download the free sound packs) connects to tracking services with neither a real opt-in nor an opt-out option. Newer versions of MuseHub now seem to [[Forced account|require an account]] to download free sound packs and sound effects, which previously was not the case. Muse Hub starts at every system launch by default and stays active in the background despite this not being required for its functionality. They also added proprietary parts to MuseScore (like the MuseSample), which is kept closed source. They also bought StaffPad and seem to have quietly ceased its development without publishing any statements.
|
|-
|[[NationStates]]
|Data Breach March 2026
|
|-
|[[Navdy]], [[Harman International]]
|Device discontinued and no updates, device can be used offline for 1 year until it stops working.
https://www.reddit.com/r/navdy/
|
|-
|[[Navia]]
|Data Breach March 2026
|
|-
|[[Netgear]] (internet networking equipment)
|Almost every Netgear internet router requires the creation of a new account to function as a router (see [[Forced account]]), where the TOS includes an agreement to binding arbitration. Most if not all devices are locked into proprietary firmware with no option to change. Some automatic updates have reportedly cause loss of performance with option to revert to a previous version, "bricking" the device in some cases.
Engages in anti-consumer practices, requiring a subscription for basic WiFi-router features such as parental controls. According to a blogpost by a senior employee, grew from "45% in 2016 to over 60% in 2019" of the US consumer router market. In 2025, Netgear is "being sued by TP-Link for a 'Smear Campaign' to Advance US Router Ban [of it's competitor TP-Link].
|<ref>{{Cite web |title=NETGEAR Terms and Conditions |url=https://www.netgear.com/about/terms-and-conditions/ |url-status=live}}</ref><ref>{{Cite web |title=What subscription plans are available for NETGEAR Smart Parental Controls? |url=https://kb.netgear.com/000062104/What-subscription-plans-are-available-for-NETGEAR-Smart-Parental-Controls |url-status=live}}</ref><ref>{{Cite web |title=Abhay Bhorkar |url=https://www.netgear.com/hub/author/abhorkar/ |url-status=live}}</ref><ref>{{Cite web |title=TP-Link Accuses Netgear of 'Smear Campaign' to Advance US Router Ban |url=https://www.pcmag.com/news/tp-link-accuses-netgear-of-smear-campaign-to-advance-us-router-ban?test_uuid=04IpBmWGZleS0I0J3epvMrC&test_variant=B |url-status=live}}</ref>
|-
|[https://www.nexigroup.com/ Nexi S.p.A.]
|Nexi is a payment services provider based in Italy, which has been used by the [https://fsfe.org/ Free Software Foundation Europe] (FSFE) for ~ 15 years. They have allegedly been asking FSFE for personal information of FSFE executives and supporters and have recently cancelled their contract with FSFE.
|<ref>{{Cite web |date=2026-03-16 |title=450 FSFE supporters affected: Payment provider Nexi cancelled us |url=https://fsfe.org/news/2026/news-20260316-01.en.html |url-status=live |archive-url=https://web.archive.org/web/20260317162959/https://fsfe.org/news/2026/news-20260316-01.en.html |archive-date=2026-03-17 |access-date=2026-03-17 |website=FSFE - Free Software Foundation Europe}}</ref>
|-
|[[Odido]] Netherlands B.V.
|Odido is an internet service provider in the Netherlands with a 10-15% market share [[https://www.acm.nl/nl/publicaties/acm-telecommonitor-derde-kwartaal-2025 79]]. On the 3rd of March 2026 a user reported that his Odido Zyxel EX5601-T1 router was (illegally) sending analytics data to a Turkish AI-company [[https://www.linkedin.com/pulse/odido-router-verzamelt-analytics-van-je-huishouden-sipke-mellema-0uoie/ 80]]. The user reported on the 8th of March 2026 that the router silently stopped sending this data with no formal mention/patch from Odido. The user reported on the poor security of the router and that the analytics data contained the unencrypted names of local networks, the names of devices connected to these networks, and MAC-addresses. The poor security of Odido's routers follows a massive data leak of 6.2 million customers' full legal names, phone numbers, emails, bank account numbers, passport numbers and more [[https://tweakers.net/nieuws/244656/odido-waarschuwt-voor-datalek-miljoenen-klantgegevens-gestolen-bij-cyberaanval.html 81]].
|<ref>{{Cite web |title=ACM Telecommonitor derde kwartaal 2025 |url=https://www.acm.nl/nl/publicaties/acm-telecommonitor-derde-kwartaal-2025 |url-status=live}}</ref><ref>{{Cite web |title=Odido-router verzamelt analytics van je huishouden |url=https://www.linkedin.com/pulse/odido-router-verzamelt-analytics-van-je-huishouden-sipke-mellema-0uoie/ |url-status=live}}</ref><ref>{{Cite web |title=Odido waarschuwt voor datalek: miljoenen klantgegevens gestolen bij cyberaanval |url=https://tweakers.net/nieuws/244656/odido-waarschuwt-voor-datalek-miljoenen-klantgegevens-gestolen-bij-cyberaanval.html |url-status=live}}</ref>
|-
|[[OICA]] (European automotive lobby organisation)
|The OICA recently pushed for the right to emit sounds from quiet electric cars to make them as loud as conventional cars with combustion engine and against stricter noise regulation in cities. The fake engine noises in question are specifically not for safety purposes, but for emotional effect for the driver. However, instead of playing the noises only inside for just the driver to hear, the noise is to be played on speakers on the exterior, thus affecting the general public. Noise pollution has long been known to have adverse health effects. ''[NOTE: Similar to environmental aspects, greenwashing etc., we will have to find a good angle for how this fits the wiki. I would say it does match the general theme of manufacturers deliberately making their products worse for minor financial gain and lobbies pushing against things that are in public interest.]''
|<ref>{{Cite web |last=Krempl |first=Stefan |date=2026-01-07 |title=Sound Dictatorship vs. Quiet: The Battle for E-Car Roar |url=https://www.heise.de/en/news/Sound-Dictatorship-vs-Quiet-The-Battle-for-E-Car-Roar-11133630.html |url-status=live |archive-url=http://web.archive.org/web/20260108165124/https://www.heise.de/en/news/Sound-Dictatorship-vs-Quiet-The-Battle-for-E-Car-Roar-11133630.html |archive-date=8 Jan 2026|access-date=2026-01-08 |website=Heise Online}}</ref>
|-
|Pearl Abyss
|Crimson Desert engaged in hardware gatekeeping by purposely locking out support for Intel GPUs. Their response when people asked what was going on was, “Get a refund.” They failed to mention in their hardware requirements that Intel GPUs were not supported. Intel also reached out to Pearl Abyss over the course of Crimson Desert’s development to offer support but was ignored. Pearl Abyss has now backpedaled after public backlash and says they will offer Intel GPU support.
|<ref>{{Cite web |title=Intel suggests it was snubbed by Crimson Desert dev after reaching out "many times" about Arc GPUs – company says it provided "early hardware, drivers, and engineering resources" to studio |url=https://www.tomshardware.com/pc-components/gpus/intel-suggests-it-was-snubbed-by-crimson-desert-dev-after-reaching-out-many-times-about-arc-gpus-company-says-it-provided-early-hardware-drivers-and-engineering-resources-to-studio |url-status=live}}</ref><ref>{{Cite web |title=Crimson Desert blocks Intel ARC GPUs from playing, studio asks owners to refund |url=https://www.neowin.net/news/crimson-desert-blocks-intel-arc-gpus-from-playing-studio-asks-owners-to-refund/#:~:text=Users%20on%20Reddit%20who%20discovered,resolution%20for%20Intel%20ARC%20owners. |url-status=live}}</ref><ref>{{Cite web |title=Crimson Desert doesn't support Intel Arc GPUs on PC, it may never, and the devs say get a refund if you have one — they didn't warn players until launch |url=https://www.windowscentral.com/gaming/pc-gaming/crimson-desert-doesnt-support-intel-arc-gpus-it-may-never-and-the-devs-say-get-a-refund-if-you-have-one |url-status=live}}</ref><ref>{{Cite web |title=Crimson Desert Doesn't Work on Intel GPUs, But Pearl Abyss Is Working On It |url=https://www.ign.com/articles/crimson-desert-doesnt-work-on-intel-gpus-but-pearl-abyss-is-working-on-it |url-status=live}}</ref>
|-
|[[Regus]]
|A flexible office / workplace provider for freelancers, contractors, small businesses, etc.
This is specifically for their Virtual Office service. I am sure they apply these same predatory and deceptive tactics with the rest of their services as well.
Locks you into a contract for virtual services that they may terminate at any time. You can too only if you follow very specific and exaggerated terms. They will bill you for the entire agreement even with it terminated. You lose access to the services immediately upon termination but are forced to pay for the rest of the agreement. They are predatory with agreements and will not allow you to break them and will charge you for the entire thing regardless of what happens.
Forced arbitration. Force you to waive any right to class action lawsuits.
Contract comes with terms hidden in their "house rules" document, automatically opting the user into services they did not knowingly agree to, by default. These services are NOT included in the original contract in any way except through the referencing to other documents like the "Terms of Service" and "House Rules", not disclosed ahead of time. They clearly show a lower price and do not clearly show any of the additional services you unknowingly opt into.
They lead you into a low price to get the agreement signed. Once signed, you cannot escape or get out with their terms. You find out later that they've made you agree to additional services by default. They require YOU to jump through hoops to opt out of those services, and they bury the information to do it.
They have predatory auto-renewals for the contracts that are typically months to years long, with many being sold into higher 1 year+ contracts for "savings" and "discounts". These auto-renewals cannot be canceled without 3 MONTHS notice! If it renews, you are locked into another term which you will be forced to pay in full even if you terminate.
This is all for VIRTUAL office services that cost nothing to provide or remove.
A lot of deceptive patterns including, but not limited to: Comparison prevention, hidden costs, hidden subscription, obstruction.
|[https://serviceagreement.regus.com/TermsPDF/VirtualOffice/Global20250301.pdf Terms of Service]
[https://serviceagreement.regus.com/PreviewHouseRule.aspx?guidId=840179ed-c894-4e91-8ccc-3b882bcf4b38 House Rules]
[https://www.myregus.com/help#:~:text=you%20can%20give%20notice%20to%20terminate%20your%20agreement%20at%20anytime%20in%20your%20online%20account%20%2D%20but%20you%20will%20be%20charged%20until%20the%20end%20of%20your%20agreement%20term. Help Page - terminate anytime but pay everything]
|-
|[https://www.skystone.games/ Skystone Games]
|Boundary, a multiplayer online-only first-person shooter, got shut down just a year after its release by Skystone Games, and its publishing rights relinquished, citing "ongoing delays and a lack of updates from the developer". Studio Surgical Scalpels (the developer) stated that the publisher decisions were "extremely sudden and unreasonable", and attempted to "regain the rights to boundary". The game has been offline for more than a year at the time of writing, and no refunds or communications to the user base has been made by Skystone Games.
|<ref>{{Cite web |date=2024-06-19 |title=Boundary - End of service notice |url=https://store.steampowered.com/news/app/1364020/view/4209257868262605607?l=english |url-status=live |access-date=2025-07-07 |website=Steam |archive-url=http://web.archive.org/web/20251021143111/https://store.steampowered.com/news/app/1364020/view/4209257868262605607?l=english |archive-date=21 Oct 2025}}</ref><ref>{{Cite web |date=2024-06-30 |title=Boundary Shut Down: Who's to Blame? |url=https://www.youtube.com/watch?v=Kr8IhV1fovE |url-status=live |archive-url=https://preservetube.com/watch?v=Kr8IhV1fovE |archive-date=16 Feb 2026}}</ref>
|-
|Samsung Galaxy S25
|Samsung s25 ultra one ui 8.5 android 16 needs location for blue light shield even for custom schedule.
|[https://drive.google.com/file/d/1Djw8iz7HWTt_uywYQywnMVDwmnBGPt_t/view?pli=1 Screenshot]
|-
|[[Sony]], Sony Online Entertainment/[[Daybreak Game Company]]
|Selling off SOE to the investment firm Columbus Nova, all games published by SOE were delisted without prior notice to consumers or developers, and licenses were revoked as well.
|<ref>{{Cite web |last=S |first=Shawn |date=Jun 10, 2016 |title=Akimi Village |url=https://delistedgames.com/akimi-village/ |url-status=live |archive-url=http://web.archive.org/web/20251127030103/https://delistedgames.com/akimi-village/ |archive-date=27 Nov 2025|website=Delisted Games}}</ref><ref>{{Cite news |last=Weber |first=Rachel |date=Feb 2, 2015 |title=SOE acquired, becomes Daybreak Game Company |url=https://www.gamesindustry.biz/soe-acquired-becomes-daybreak-game-company |work=GamesIndustry.biz |url-status=live |archive-url=http://web.archive.org/web/20260204235742/https://www.gamesindustry.biz/soe-acquired-becomes-daybreak-game-company |archive-date=4 Feb 2026}}</ref>
|-
|[[Sony]]
|Sony implements surge pricing/discounts on a per-user basis on their playstation store by profiling users, similar to airlines, car rentals, and concert tickets... only the goods are digital only and downloadable rather than physical media. Critics are calling this Surveillance Pricing.
|<ref>https://youtu.be/t8yVc6Uarho?si=fJeCzxqmxgyB_tLq</ref>
|-
|[[Spectora]]
|Spectora is a home inspection software used by many home inspectors, a very important portion of the home buying process. Spectora has announced they intend to insert ads April 7th. The ads look like the home inspector (a independent entity) is recommending outside services. Spectora has also purchased other home inspection platform HomeGauge on April 4th. With Fixle being in the purchese which is the ad network they now own. There are also allegations (have not been proven) of sale of the inspection data (something that remains confidential with client controlling confidentiality) to insurance companies, and Home Lenders. Causing increased rates on historical inspection data even when those things could be a condition to close on the home.
|<ref>{{Cite web |title=Forced Partnership |url=https://forum.nachi.org/t/forced-partnership/266387 |url-status=live}}</ref><ref>{{Cite web |title=Fixle by Spectora: Post-Inspection Tools for Home Buyers |url=https://www.spectora.com/fixle/?utm_campaign=41151531-2026%20Fixle%20Launch%20Campaign&utm_medium=email&_hsmi=411347418&utm_content=411347418&utm_source=hs_automation |url-status=live}}</ref><ref>{{Cite web |title=Spectora acquires HomeGauge |url=https://coverager.com/spectora-acquires-homegauge/ |url-status=live}}</ref>
|-
|[[Starbucks]]
|Data Breach affecting employees March 2026
|
|-
|[[Superbox]]
|Android TV box manufacturer Superbox remotely locks consumers' devices if they were sold below the manufacturer's minimum specified prices and asks consumers to contact the retailer when they complain.
They are not the first to do something like this. [[Deye]] locked down inverters in the US that they suspected might be gray imports.
|<ref>{{Cite web |title=You'll Own Nothing and Be Happy |url=https://www.youtube.com/watch?v=5I5-rAyFQrk |website=YouTube |type=Video |url-status=live |archive-url=https://preservetube.com/watch?v=5I5-rAyFQrk |archive-date=16 Feb 2026}}</ref>
|-
|[[Symantec]]
|Product: Norton Internet Security.
This one might be tough to document, because it's been slowly going on for the past 15 years. Norton used to offer a great internet security package with a ton of good and useful services for a decent price. Unfortunately, slowly over the years, they've gone further and further down the rabbit hole of charging more money for fewer and fewer features, and then locking some of those features behind even more paywalls and micro-transactions.
|
|-
|[[Steam]] by Valve software
|As of 2026 games bought to work and made for Windows 7, are no longer accessible on Windows 7 OS - A system they were made to work on and sold for. Titles that might not even work on modern Windows instalments.
This is done by forcing updates before launching of any title.
If there was a patch it will always fail before finishing update process.
Thus if user is unwilling to move to next installment of supported the operating system for whatever reason, which is not valve's decision to make. User is locked out of his purchase.
|[https://disk.yandex.com/i/ZPOVZYq11i8nJQ][https://disk.yandex.com/i/pBkHSsIhU5KqmA][https://disk.yandex.com/i/-mGVJAJHSTX-5Q][https://disk.yandex.com/i/I-NVZmXmfBrBEQ]
|-
|[[Telus]]
|Data Breach March 2026
|
|-
|[[TriZetto]]
|Data Breach March 2026
|
|-
|[[Universal Audio]]
|Product: UAD (Volt) Audio Interfaces
Universal Audio (UAD) [[Forced account|requires users to create an account and sign in]] to their software to use their audio interfaces–this is a necessary step and without it the interfaces are unusable.
|<ref>{{Cite web |title=Official UAD setup guide for "Volt" audio interfaces |url=https://help.uaudio.com/hc/en-us/articles/4409233546644-How-to-set-up-your-Volt-Interface}}</ref><ref>{{Cite web |title=Review of Volt 876 audio interface by Julian Krause |url=https://youtu.be/CCnttwq9jMw?si=DcwA97e3pSfp5rlr&t=803}}</ref>
|-
|[[UP3]] By [[Jawbone]]
|Approximately 2011, Pioneering startup company from San Francisco, had revolutionary fitness trackers. In 2017 with no notice to customers they stole personal data and shut down app which in turn, bricked devices. Highly likely went bankrupt and sold to sister company to manipulate customer services and rights. Now owned by Aliph brands.
|
|-
|[[Vive]]
|In 2022, Vive discontinued the original Vive Facial Tracker module a year after the original release, then released an updated model with proprietary firmware that blocked use on other 3rd party VR headset, while only allowing the new model to work with their new locked-down headset. The 2021 version of the face tracker's long term support was seemingly cut overnight without any software updates since 2021.
|<ref>{{Cite web |last=Vive Team |date=2022-08-07 |title=VIVE Focus 3 gets Facial Tracker, and Eye Tracker |url=https://blog.vive.com/us/vive-focus-3-gets-facial-tracker-and-eye-tracker/ |url-status=live |archive-url=https://web.archive.org/web/20250619155201/https://blog.vive.com/us/vive-focus-3-gets-facial-tracker-and-eye-tracker/ |archive-date=2025-06-19 |access-date=2025-09-21 |website=Vive Blog}}</ref><ref>{{Cite web |last=StateKi |date=2023-10-10 |title=Post by StatekTi on X |url=https://nitter.catsarch.com/StatekTi/status/1733954156379963393 |url-status=live |archive-url=https://web.archive.org/web/20260520140619/https://nitter.catsarch.com/StatekTi/status/1733954156379963393 |archive-date=20 May 2026 |access-date=2025-11-21 |website=X (Formerly Twitter)}}</ref>
|-
|Wheatstone Corporation
|Wheatstone Corporation are a manufacturer of professional broadcast equipment, mainly audio consoles and interfaces that utilise their proprietary Wheatnet audio over IP protocol.
Wheatstone restricts access to firmware updates, software configuration tools and software. You must open a support ticked in order for them to send you a download link to these software tools, they make it very difficult to access software required to make their hardware audio interfaces work, even stating they want proof of purchase (not just a licence key) before they will even give you the download link. Managing licences is also non-existent and you will need to contact support, and as such a fee is imposed.
|
|-
|White House
|The White House made a news app, but this app tracks your location every 4.5 minutes through third-party OneSignal
|<ref>{{Cite web |last=Deep Humor |date=2026-03-30 |title=Don't Download This App |url=https://youtu.be/d5OTwcRxaTw?si=REEdhGeYPelHGLEQ |url-status=live |access-date=2026-03-30 |website=[[YouTube]]}}</ref><ref>{{Cite web |last=Tixon |first=Bernadette B. |date=2026-03-29 |title=White House App Found Tracking Users' Exact Location Every 4.5 Minutes via Third-Party Server |url=https://www.ibtimes.co.uk/white-house-app-gps-tracking-controversy-1788974 |url-status=live |access-date=2026-03-31 |website=[[International Business Times]]}}</ref><ref>{{Cite web |last=Milden |first=Dashia |date=2026-03-30 |title=I Downloaded (and Deleted) the White House App So You Don't Have To. It's a Hot Mess |url=https://www.cnet.com/tech/services-and-software/i-downloaded-and-deleted-the-white-house-app-so-you-dont-have-to-its-a-hot-mess/ |url-status=live |access-date=2026-03-31 |website=CNET}}</ref><ref>{{Cite web |date=2026-03-30 |title=White House app sparks concern over location tracking and privacy issues |url=https://www.tradingview.com/news/cointelegraph:565f766ef094b:0-white-house-app-sparks-concern-over-location-tracking-and-privacy-issues/ |url-status=live |access-date=2026-03-31 |website=[[TradingView]]}}</ref>
|-
|[[WHMCS]]
|Discontinuation of support and updates for WHMCS legacy “Owned” licenses, forcing users who want ongoing updates or technical support to switch to subscription licensing and pay recurring fees rather than continue with the original owned model. This change affects all holders of legacy owned licenses and alters the long-term terms under which those licenses were originally sold
|<ref>{{Cite web |title=WHMCS Knowledgebase |url=https://www.whmcs.com/members/index.php/knowledgebase/70/Support-and-Updates-Expiration.html |url-status=live |archive-url=http://web.archive.org/web/20251211021038/https://www.whmcs.com/members/index.php/knowledgebase/70/Support-and-Updates-Expiration.html |archive-date=11 Dec 2025}}</ref><ref>{{Cite web |title=Important pricing changes to your WHMCS owned license Mailer |url=https://www.whmcs.com/members/mailings/?k=price21-emailo |url-status=live |archive-url=https://web.archive.org/web/20260215233549/https://www.whmcs.com/members/mailings/?k=price21-emailo |archive-date=15 Feb 2026}}</ref>
|-
|[[Wireless Power Consortium]]
|After monopolizing wireless charging market Qi turned from an open standard into a proprietary.
Version 1.3 introduced "secure authentication between the transmitter and the receiver", i.e. in order to operate every charger must include an expensive proprietary chip licensed only to certified members. This results in increased development and manufacturing costs directly passed onto consumer. Version 2.2, unlike previous versions, "is available for WPC Members only".
|<ref>{{Cite web |title=Qi Certification Is Changing and We've Got You Covered |url=https://www.nxp.com/company/about-nxp/smarter-world-blog/BL-QI-CERTIFICATION-IS-CHANGING |url-status=live |archive-url=http://web.archive.org/web/20251104012700/https://www.nxp.com/company/about-nxp/smarter-world-blog/BL-QI-CERTIFICATION-IS-CHANGING |archive-date=4 Nov 2025|website=NXP Semiconductors}}</ref>
<ref>{{Cite web |title=Download the Qi Specifications |url=https://www.wirelesspowerconsortium.com/knowledge-base/specifications/download-the-qi-specifications/ |url-status=live |archive-url=http://web.archive.org/web/20251104094044/https://www.wirelesspowerconsortium.com/knowledge-base/specifications/download-the-qi-specifications/ |archive-date=4 Nov 2025|website=Wireless Power Consortium}}</ref>
|-
|[[Wizards of the Coast]]
|Wizards of the Coast (WotC) seems to be positioning itself to move away from publishing physical books that last forever in favor of pushing digital-only sales and micro-transactions of content and subscriptions. They attempted to amend the OGL (Open Game License) to include language that would require third party authors of D&D content to give up rights to their own content, so WotC can sell it to consumers without crediting the original authors.
Notably, as a direct response to these anti-consumer activities and policies, a select few of the third party publishers have instead decided to come out with their own systems that are not beholden to WotC's whims. A couple of examples include ''Draw Steel'' and ''Daggerheart''. An earlier conflict prompted Paizo to release their own version of the classic D20-based tabletop RPG, ''Pathfinder'', when WotC started releasing the fourth edition of it's rule-set.
|
|-
|[[Wolfgang Puck]]
|Some of the bread makers have anti repair screws in them to prevent people from repairing them themselves. Needs more citations.
|
|-
|[[World Orb]]
|World Network (Sam Altman/Open AI) scheme to collect biometric data on all people. Tied to cryptocurrency, AI schemes. Supposedly way for people to show they are human (run by the people who are trying to make a profit from AI).
|
|-
|Yoti
|Age verification company that operates in the UK, used by Sony for Playstation accounts. A user claims that Yoti reported him to authorities for using their app on GrapheneOS.
|https://discuss.grapheneos.org/d/36134-grapheneos-user-reported-to-authorities-for-using-grapheneos
https://imgur.com/a/yoti-hates-graphene-threatens-you-MCHs6NA
https://www.reddit.com/r/privacy/comments/1txn8di/did_i_just_got_threatened_by_yoti_age/
|-
|[[Zhiyun]]
|Like competing products from [[DJI]], Zhiyun video gimbals require a Chinese smartphone app, internet access and an [[Forced account|account]] to activate on first use.
|<ref>{{Cite web |last=ZHIYUN Tutorials |date=25 Jul 2023 |title=ZHIYUN CRANE 2S Activation Tutorial |url=https://www.youtube.com/watch?v=_CjNp6pWNoQ |archive-url=https://preservetube.com/watch?v=_CjNp6pWNoQ |archive-date=23 Feb 2026 |website=YouTube}}</ref>
|}

==List of themes not yet covered==
Consumer Rights Wiki is not an encyclopedia.

*Before proposing or making a theme article, see if you can find an article that covers the topic on wikipedia, or some other reference. If you can, just use a reference to that.
*Check the list of theme articles [[:Category:common terms]], to be sure there isn't already an article on the topic, or one closely related. Sometimes a theme may be covered by generalizing an existing article.

{| class="wikitable"
|+
!Theme
!Summary of Theme
!Refs
|-
|Car manufacturers replacing physical controls by touch-screens
|This is increasingly common, and puts drivers at risk. Some corps pretend touchscreens are a "premium" or "modern" feature, but are typically cheaper for them
|
|-
|[[Content delivery network]] ([[CDN]])
|[[wikipedia:Content_delivery_network|WP]], see also [[Cloud (service)]]. While helpful, they can infer the browsing history of millions of users across sites. The bigger their monopoly, the more cross-site tracking power they have. Even GDPR has been against using CDNs in some situations. Examples of CDN: [[wikipedia:Amazon_CloudFront|CloudFront]] (see [[Amazon]] [[wikipedia:Amazon_Web_Services|AWS]]), [[Cloudflare]], [[Microsoft]] [[wikipedia:Microsoft_Azure|Azure]], [[wikipedia:Fastly|Fastly]], etc...
|
|-
|[[Copyright]]
*Consumer License Agreement (CLA)
|Copyright is an important theme, please mention what it covers, what are the exceptions (e.g. [[wikipedia:first-sale doctrine|first-sale doctrine]]), what laws cover it ([[Digital Millennium Copyright Act|DMCA]]), what exceptions the laws provide (e.g. panorama, see Refs column)
*Cover CLA as an incident type (example company/project [[Canonical]]/[[LXD]]), it's a form of forced contract assigning the company (source code maintainer) the copyright to open source contributions, allowing them to use them in closed source releases.
|[https://www.copyrightexceptions.eu/ CopyrightExceptions.eu]
*[https://drewdevault.com/blog/Dont-sign-a-CLA-2/ Seriously, don't sign a CLA]
*[https://stgraber.org/2023/12/12/lxd-now-re-licensed-and-under-a-cla/ LXD now re-licensed and under a CLA]
|}

==List of companies doing the right thing==
It would be helpful to include examples of companies doing the right thing, even if they aren't, strictly speaking, consumer products.
{| class="wikitable"
|+
!Company
!Good deed
!Refs
|-
|APSystems
|After requests from users, the company released a firmware update that adds a local API to their EZ-1M solar micro inverter, allowing it to remain fully usable if the company ends support for the device
|<ref>{{Cite web |title=APsystems EZHI Local API User Manual |url=https://global.apsystems.com/document/apsystems-ezhi-local-api-user-manual/ |url-status=live |archive-url=http://web.archive.org/web/20251107061040/https://global.apsystems.com/document/apsystems-ezhi-local-api-user-manual/ |archive-date=7 Nov 2025|website=global.apsystems.com}}</ref>
|-
|Concept2
|Readily provides parts and diagrams. Exists under a [https://www.concept2.com/about/perpetual-purpose-trust Perpetual Purpose Trust].
|
|-
|Core Devices (from creator of Pebble Smartwatches)
|Not strictly Core Devices, but when Pebble was sold to Fitbit, the servers remained online for some time, and the Pebble app was updated to allow the Rebble community project to take over some of the Pebble server-side functionality. All backers of the upcoming Pebble 2 series of watches were refunded in full, despite it being a crowd-funding campaign.
Following Google's acquisition of Fitbit and after many years, Google released much of the Pebble Smart Watch source code on github (excluding proprietary libraries). Core Devices and Rebble replaced the usage of the proprietary libraries with open source alternatives, and released new Android and iOS apps, not only supporting the new core devices, but bringing updated support to legacy Pebble devices.
|
|-
|Fairphone
|The new Fairphones (5th and 6th generation) are availible with stock android as well as e/os, which is a fork of lineage os and a european alternative cloud provider (murena) instead of google. This has many privacy features (app tracker blocker, tor network usage, and gps spoofing) availible in a few clicks. Also degoogle apps (microg, safetynet, ...) are preinstalled therefore it is w´possible to install everything also from playstore with an anonymous account. As e/os is a fork of lineage os and there is an official guide to flash the fairphone with e/os and is officially supported, flashing lineage os is very easy.
|<ref>{{Cite web |date=2026-02-24 |title=How to manually install Android on your Fairphone |url=https://support.fairphone.com/hc/en-us/articles/18896094650513-How-to-manually-install-Android-on-your-Fairphone |url-status=live}}</ref><ref>{{Cite web |title=The Fairphone (Gen. 6) with privacy first /e/OS |url=https://shop.fairphone.com/the-fairphone-gen-6-e-operating-system |url-status=live}}</ref>
|-
|Framework
|They have 10/10 repair score by iFixit site for most of their products. They also support right to repair themselves.
|<ref>{{Cite web |title=Sustainability |url=https://frame.work/sustainability |url-status=live |website=[[Framework]]}}</ref><ref>{{Cite web |last=Frauenheim |first=Carsten |title=Framework Laptop 13 Repair |url=https://www.ifixit.com/Device/Framework_Laptop |url-status=live |website=[[iFixit]]}}</ref>
|-
|Home Assistant
|Open-source smart home platform that provides local control, automation, and interoperability for a wide range of smart home devices. Provides support for many cloud devices after they're subject to [[discontinuation bricking]].
|<ref>{{Cite web |title=Home Assistant |url=https://www.home-assistant.io/ |url-status=live |archive-url=https://web.archive.org/web/20260129222300/https://www.home-assistant.io/ |archive-date=2026-01-29 |access-date=2026-02-05}}</ref>
|-
|Noctua
|Extremely long support for old products and availability of upgrade kits
|<ref>{{Cite web |last=LMG Clips |date=19 Feb 2026 |title=The Last CPU Cooler You Will Ever Buy |url=https://www.youtube.com/watch?v=D3g4-fb6u90 |archive-url=https://preservetube.com/watch?v=D3g4-fb6u90 |archive-date=23 Feb 2026}}</ref>
|-
|Numatic International
|A UK based manufacture of commercial and consumer wet/dry floor cleaning products (vacuums, scrubbers, floor buffers) that provides a robust library of technical documents, parts breakdowns, data sheets and training for free on both new and existing products without the need to login, pay additional fees or be an approved repair facility.
|
|-
|Oral-B
|When installing the Android App, there is no login, and the user is asked for analytics tracking consent.
|
|-
|Orange Pi (Shenzhen Xunlong Software Co., Ltd.)
|Commitment to Open Source Hardware and Transparency. (written with help of AI)
Public Schematics, Open Documentation (extensive datasheets for the SoCs), Right to Repair Friendly by using standardized components and providing the "map" (schematics) to the board. Community-Centric: hey actively support the "maker" ecosystem by allowing third-party OS developers (like Armbian) easy access to the hardware information needed to keep older boards running for a decade or more.
|http://www.orangepi.org/index.html
http://www.orangepi.org/html/serviceAndSupport/index.html
|-
|Philips
|Added files for replacement parts to Printables so you can 3D print parts for your Philips products
|<ref>{{Cite web |title=Philips |url=https://www.printables.com/@Philips |url-status=live |website=Printables}}</ref>
|-
|ratgdo
|A garage door opener controller developed by Paul Wieland, allowing you to locally control it (namely Chamberlain openers that would otherwise require the MyQ app for smart home features).
|<ref>{{Cite web |last=Wieland |first=Paul |title=About - ratgdo |url=https://ratcloud.llc/pages/about |url-status=live |archive-url=https://web.archive.org/web/20251213022055/https://ratcloud.llc/pages/about |archive-date=2025-12-13 |access-date=2026-02-05}}</ref>
|-
|Reticulum
|Reticulum is an open-source, decentralized networking stack designed to communicate between practically any wireless device, even without internet. Its purpose is to provide fully anonymous end-to-end encrypted communication by default, especially in the age of government surveillance. The Reticulum network, protocol, and hardware are not tied any company in particular but were initially created by Github user 'markqvist'. Honorable mention to NomadNet, which is a network of nodes that serve webpages, similar to the internet, that communicate via Reticulum.
|<ref>{{Cite web |last=markqvist |title=Reticulum Network |url=https://reticulum.network/ |access-date=2026-02-15 |website=Reticulum |archive-url=http://web.archive.org/web/20260222180553/https://reticulum.network/ |archive-date=22 Feb 2026}}</ref>
|-
|RME Audio
|Audio equipment manufacturer that provides reliable, high-quality audio interfaces and equipment with driver and firmware support that spans 15+ years. Extensive documentation and support for both Mac, Windows, and USB Class-Compliant machines on all of their products across several OS generations ensures compatibility, transparency, and a dedication for keeping old hardware alive.
|<ref>{{Cite web |date=28 Apr 2026 |title=RME |url=https://www.rme-usa.com/ |url-status=live |access-date=28 Apr 2026 |website=RME-usa.com}}</ref><ref>{{Cite web |date=28 Apr 2026 |title=RME Downloads |url=https://www.rme-usa.com/downloads.html |url-status=live |access-date=28 Apr 2026 |website=RME-usa.com}}</ref>
|-
|stevesgames.co.uk
|Will never put ads or in-app purchases in their computer games and will make gamees available for free after securing the companys future.
|
|-
|Sweetwater Sound
|The largest US-focused audio and music retailer that offers one of the best customer support systems to customers. Provides near 24x7 support with each customer being designated to a dedicated "sales engineer" who becomes the primary point of contact, with support networks that have direct contact to product vendors. Also contributes to more than 600 non-profits across the US. Also keeps outdated or obsolete product pages online as references, acting as a sort of music product database for most audio vendors.
|<ref>{{Cite web |date=30 Apr 2026 |title=Why Choose Sweetwater? |url=https://www.sweetwater.com/about/why-choose-sweetwater/ |url-status=live |access-date=30 Apr 2026 |website=Sweetwater.com}}</ref>
|-
|Tektronix
|Provided extensive product data on unsupported products to a museum, vintageTEK, and thus to tekwiki and the rest of the community.
|<ref>{{Cite web |last=Lenihan |first=Thomas F. |date=2012-02-28 |title=Copyright Notice |url=https://vintagetek.org/copyright-notice/ |url-status=live |archive-url=https://web.archive.org/web/20250828004431/https://vintagetek.org/copyright-notice/ |archive-date=2025-08-28 |access-date=2025-10-18 |website=vintageTEK museum}}</ref>
|-
|Ulanzi
|The company offers a tutorial on how users can mix their own fog juice to use with Ulanzi mini fog machines from readily available low-cost ingredients, whereas competitors sell proprietary fog juice at extortionate prices, refuse to release the formula and refuse to honour the warranty if users use anything but the OEM brand with their machines.
|<ref>{{Cite web |title=Tutorial {{!}} How to DIY Ulanzi FM01 Fog Machine Juice? |url=https://www.youtube.com/watch?v=qiq1B6-dcEM |type=Video}} ([https://preservetube.com/watch?v=qiq1B6-dcEM Archived])</ref>
|-
|ZSA
|This company produces programmable ergonomic keyboards. They have 10/10 repair score by iFixit site for one of their keyboards <ref>{{Cite web |title=ErgoDox EZ Keyboard Repairability Assessment |url=https://www.ifixit.com/Guide/ErgoDox+EZ+Keyboard+Repairability+Assessment/125077}}</ref>. They also support right to repair themselves <ref>{{Cite web |title=Supporting the Right to Repair |url=https://blog.zsa.io/2105-right-to-repair/}}</ref>. They have their own web software to modify keyboard layout <ref>{{Cite web |title=Voyager default layout |url=https://configure.zsa.io/voyager/layouts/default/latest/2}}</ref>, but it's possible to download source code of your layout and compile and flash it yourself using their fork of the QMK <ref>{{Cite web |title=QMK, forked for ZSA's Oryx Configurator (to safeguard stability) |url=https://github.com/zsa/qmk_firmware/}}</ref>. The flashing can be done with standard tools, without any signing and bootloader unlocking.
|
|}

==See also==
*[[Louis Rossmann - Video Directory]]
*[[Other Channels - Video Directory|Other Channels - Video Directory]]

==Reference List==
<references />

Flashforge

2026-06-07T17:06:25Z

Wownyc: replace with existing category

{{Cleanup|Issue 1 = Non-formatted citations.}}
{{CompanyCargo
|Description=Forces Adventurer 5M/AD5X owners onto proprietary Flash Studio slicer with banner ads; class action filed over heating & extruder defects
|Founded=2011
|Industry=3D printing,Consumer electronics
|Logo=FlashForge.png
|ParentCompany=
|CompanyAlias=Zhejiang Flashforge 3D Technology Co. Ltd.,Flashforge
|Type=Private
|Website=https://www.flashforge.com/
}}

'''Flashforge''' (legal name: '''Zhejiang Flashforge 3D Technology Co., Ltd.''') is a Chinese desktop & industrial 3D printer manufacturer founded in 2011.<ref name="ff-about">{{Cite web |url=https://www.flashforge.com/pages/about-us |title=About Us - Flashforge |website=Flashforge |access-date=May 22, 2026}}</ref> Between February 2025 and May 2026, Flashforge progressively closed the network architecture of its Adventurer 5M & AD5X consumer 3D printers, pushing owners towards a proprietary slicer carrying a banner advertisement for a $1 Meshy.ai membership offer, and which broke third-party slicer compatibility documented in OrcaSlicer GitHub issues #5154, #10112, #10260, & #11658.<ref name="ff-service-notice">{{Cite web |url=https://www.flashforge.com/blogs/news/service-upgrade-notification |title=Service Upgrade Notification |website=Flashforge |access-date=May 22, 2026}}</ref><ref name="ff-meshy">{{Cite web |url=https://www.flashforge.com/blogs/news/flashforge-meshy-ai |title=Flashforge × Meshy AI: From AI Ideas to Real Prints |date=2026-05-20 |website=Flashforge |access-date=May 22, 2026}}</ref> The same printers are the subject of a February 2026 class-action investigation by the Washington, D.C. consumer-protection firm Migliaccio & Rathod LLP over recurring heating, extruder, and auto-leveling failures.<ref name="classlaw-ff">{{Cite web |url=https://classlawdc.com/2026/02/25/flashforge-3d-printer-investigation/ |title=Flashforge 3D Printer Investigation |date=2026-02-25 |website=Migliaccio & Rathod LLP |access-date=May 22, 2026}}</ref>

==Consumer-impact summary==

*'''Vendor lock-in via firmware update.''' The March 25, 2025 ''"Service Upgrade Notification"'' set hard version floors that retired the open networking pathways previously used by mainline OrcaSlicer and third-party tooling.<ref name="ff-service-notice" />
*'''In-app advertising.''' Flash Studio Desktop (the rebranded Orca-Flashforge) carries a banner promoting a $1 Meshy.ai membership offer inside its printer-management view.<ref name="ff-meshy" />
*'''Open-source license dispute.''' OrcaSlicer issue #5154 alleges Flashforge bundled the GPLv3-licensed OrcaSlicer fork with a restrictive commercial EULA prohibiting redistribution, modification, and reverse engineering.<ref name="orca-5154">{{Cite web |url=https://github.com/SoftFever/OrcaSlicer/issues/5154 |title=Flashforge is violating OrcaSlicer's GPLv3 license (Issue #5154) |date=2024-04-26 |website=GitHub: SoftFever/OrcaSlicer |access-date=May 22, 2026}}</ref>
*'''Class-action investigation.''' Migliaccio & Rathod LLP solicits Adventurer 5M & AD5X owners reporting nozzle heating failures, premature extruder breakage, and auto-leveling crashes that gouge the build plate.<ref name="classlaw-ff" />
*'''Telemetry without disclosed source.''' Orca-Flashforge issue #26 documents the desktop slicer making outbound connections to roughly twenty hostnames (including a competitor API and the NetEase IM library) that do not appear in the company's published source repository.<ref name="orca-ff-26">{{Cite web |url=https://github.com/FlashForge/Orca-Flashforge/issues/26 |title=Provide actual codebase which exposes all connections (Issue #26) |date=2025-11-15 |website=GitHub: FlashForge/Orca-Flashforge |access-date=May 22, 2026}}</ref>

==Background==

Flashforge was incorporated in 2011 as Zhejiang Flashforge 3D Technology Co., Ltd.<ref name="ff-about" /> The company manufactures desktop FDM 3D printers (the Adventurer, Creator, Guider, and Inventor lines), resin and DLP printers (the Foto and Hunter lines), and industrial wax 3D printers (the WaxJet series).<ref name="ff-about" /> Its budget sub-brand '''Voxelab''' targets entry-level consumers, and a U.S. distribution arm operates under the name Flashforge USA.<ref name="ff-usa">{{Cite web |url=https://www.flashforge-usa.com/ |title=Flashforge USA |website=Flashforge USA |access-date=May 22, 2026}}</ref>

Flashforge originally shipped open network protocols on its FDM printers. An August 15, 2024, a Flashforge blog post described Orca-Flashforge (a fork of SoftFever's open-source OrcaSlicer) as the recommended slicer for the Adventurer 5M series & Guider 3 Ultra,<ref name="ff-orca-guide" /> & Adventurer 5M firmware 2.6.5 (April 11, 2024) added ''"Support Orca-Flashforge connection"'' & a LAN mode.<ref name="ff-orca-guide">{{Cite web |url=https://www.flashforge.com/blogs/news/orca-and-orca-flashforge-a-comprehensive-guide |title=Orca and Orca-Flashforge: A Comprehensive Guide |date=2024-08-15 |website=Flashforge |access-date=May 22, 2026}}</ref><ref name="ff-5m-changelog">{{Cite web |url=https://www.flashforge.com/a/docs/adventurer-5m-series/adventurer-5m-series-firmware-update-log |title=Adventurer 5M Series Firmware Update Log |website=Flashforge |access-date=May 22, 2026}}</ref> The 2025 service migration replaced that posture with a closed, cloud-mediated architecture.

==Incidents==

===Flash Studio mandatory slicer advertising and third-party slicer lockout===

{{Main|Flashforge Flash Studio mandatory slicer advertising and third-party slicer lockout}}

In early 2025 Flashforge published a ''"Service Upgrade Notification"'' announcing the retirement of its legacy server services on March 26, 2025 & requiring Adventurer 5M, Adventurer 5M Pro, & Guider 3 Ultra owners to update firmware to v3.1.0 or later & the Orca-Flashforge desktop slicer to v1.3.0 or later.<ref name="ff-service-notice" /> Orca-Flashforge was subsequently rebranded to Flash Studio Desktop, & on May 20, 2026 the company announced a Meshy.ai partnership that embedded a banner promoting a $1 Meshy membership offer inside the slicer's printer-management view.<ref name="ff-meshy" /> Owners running mainline OrcaSlicer 2.3.0 against post-migration firmware report ''"ERR_CONNECTION_REFUSED"'' errors on the device tab (OrcaSlicer issue #10260, July 28, 2025).<ref name="orca-10260">{{Cite web |url=https://github.com/OrcaSlicer/OrcaSlicer/issues/10260 |title=Device Section of Orca Slicer not working with Flashforge AD5M (Issue #10260) |date=2025-07-28 |website=GitHub: OrcaSlicer/OrcaSlicer |access-date=May 22, 2026}}</ref> Two community Klipper-based firmware mods (''xblax/flashforge_ad5m_klipper_mod'' & ''DrA1ex/ff5m'') restore open networking at the cost of voiding the manufacturer warranty.<ref name="klipper-xblax">{{Cite web |url=https://github.com/xblax/flashforge_ad5m_klipper_mod |title=Unofficial mod for Flashforge Adventurer 5M (Pro) 3D printers to run Moonraker, custom Klipper, Mainsail and Fluidd |website=GitHub: xblax/flashforge_ad5m_klipper_mod |access-date=May 22, 2026}}</ref>

===Flashforge threatens to report customers for printing firearms or weapon components===

In late 2025, Flashforge posted an infographic titled '''NO to weaponized 3D printing''' on Facebook, threatening to report customers printing firearms or weapon components to "authorities"<ref>{{Cite web |date=2025-11-14 |title=Flashforge telling and threatening their users |url=https://www.reddit.com/r/3Dprinting/comments/1owqkqs/flashforge_telling_and_threatening_their_users/ |url-status=live |archive-url=https://ghostarchive.org/archive/9gc3A |archive-date=2026-07-06 |access-date=2026-06-07 |website=[[Reddit]]}}</ref><ref>{{Cite web |date=2025-11-15 |title=3D Printer manufacturer Flashforge openly threatens to report their customers to authorities for printing weapon components |url=https://www.reddit.com/r/Firearms/comments/1oxtrni/3d_printer_manufacturer_flashforge_openly/ |url-status=live |archive-url=https://ghostarchive.org/archive/5DsuW |archive-date=2026-06-07 |access-date=2026-06-07 |website=[[Reddit]]}}</ref>, implying that it has the capability to view users prints, or to mitigate liability.

The Facebook post has been reproduced below:
<div style="width: 30vw; color: gray;">
We build tools for creation--never for harm. 
Flashforge stands for safe, responsible 3D printing.
</div>
<div style="width: 30vw; color: gray; text-align: center">
NO to weaponized 3D printing

Flashforge does not support or condone the 3D printing of firearms or weapon components. (Subject to the Flashforge user agreement.)

Flashforge prohibits using our products and services to create firearms or weapon components. Violations may lead to account termination and refer- ral to authorities.
</div>

Privately made firearms are legal in the United States, at least federally.<ref>https://www.atf.gov/firearms/privately-made-firearms</ref>

The Facebook post was later retracted.{{Citation needed}}

===Adventurer 5M & AD5X hardware-defect class-action investigation===

On February 25, 2026 the Washington, D.C. consumer-protection law firm Migliaccio & Rathod LLP opened a class-action investigation soliciting Adventurer 5M & AD5X owners whose printers exhibit recurring failures.<ref name="classlaw-ff" /> The firm's intake page lists specific defect patterns: nozzles that fail to heat or hold temperature, printers that stop working within days or months of purchase, premature extruder & filament-feeder breakage, repeated jams & feeding errors, & auto-leveling failures resulting in nozzle scraping & poor first-layer adhesion.<ref name="classlaw-ff" /> The firm solicits affected owners through an online intake form.<ref name="classlaw-ff" /> Tom's Hardware reviewer Denise Bertacchi, in a published October 12, 2025 AD5X review, separately reported that the bundled Orca-Flashforge slicer ''"is perhaps the least stable version"'' of OrcaSlicer she had used, crashing about every third print.<ref name="tomshardware-ad5x">{{Cite web |url=https://www.tomshardware.com/3d-printing/flashforge-ad5x-review |title=Flashforge AD5X review: An affordable option for fast color 3D printing |last=Bertacchi |first=Denise |date=2025-10-12 |website=Tom's Hardware |access-date=May 22, 2026}}</ref> The investigation is open as of May 2026; no class certification or settlement has been announced.<ref name="classlaw-ff" />

==Products==

Flashforge sells three families of additive-manufacturing hardware plus the proprietary Flash Studio software suite.

*'''Adventurer 5M series.''' CoreXY FDM printers including the Adventurer 5M (open frame) & Adventurer 5M Pro (enclosed with HEPA filtration). Affected by the March 2025 service migration & the Migliaccio & Rathod class-action investigation.<ref name="ff-service-notice" /><ref name="classlaw-ff" />
*'''Adventurer 5X (AD5X).''' Multi-color CoreXY FDM printer with an Intelligent Filament System. Affected by the same firmware lockout & class-action investigation, & the subject of the October 2025 Tom's Hardware stability review.<ref name="tomshardware-ad5x" /><ref name="classlaw-ff" />
*'''Creator 5 / Creator 5 Pro.''' Four-toolhead changing systems heavily promoted in the Meshy.ai partnership materials.<ref name="ff-meshy" /><ref name="prnewswire-meshy">{{Cite web |url=https://www.prnewswire.com/news-releases/flashforge-and-meshy-partner-to-bring-ai-image-to-3d-directly-into-consumer-multi-color-printing-302778460.html |title=FlashForge and Meshy Partner to Bring AI Image-to-3D Directly Into Consumer Multi-Color Printing |date=2026-05-21 |website=PR Newswire |access-date=May 22, 2026}}</ref>
*'''Guider 3 Ultra.''' Enterprise-tier FDM printer also covered by the March 2025 service migration's mandatory firmware floor.<ref name="ff-service-notice" />
*'''Software.''' Flash Studio Desktop (formerly Orca-Flashforge; a GPLv3 fork of SoftFever's OrcaSlicer), Flash Studio Mobile (formerly Flash Maker), & the legacy FlashPrint slicer.<ref name="ff-meshy" /><ref name="orca-5154" />
*'''Legacy & adjacent lines.''' Creator (2011-), Creator Pro, Creator 3, Dreamer, Finder, Adventurer 3 & 4, Inventor, Guider II, Foto 8.9 LCD resin, Hunter S DLP, & the industrial WaxJet 400/510/530 wax-pattern printers.<ref name="ff-about" />

The budget sub-brand Voxelab markets entry-level FDM & resin printers separately from the main Flashforge catalogue.<ref name="ff-about" />

==See also==
*[[Flashforge Flash Studio mandatory slicer advertising and third-party slicer lockout]]
*[[Bambu Lab Authorization Control System]]

==References==
{{Reflist}}

[[Category:Companies]]
[[Category:Flashforge]]
[[Category:3D_printers]]
[[Category:Chinese companies]]

Category:Flashforge

2026-06-07T17:04:35Z

Wownyc: add 3dp category

This category is for articles relating to [[Flashforge]].

[[Category:Companies]]
[[Category:3D_printers]]

FlashForge

2026-06-07T17:01:08Z

Wownyc: create redirect

#REDIRECT [[Flashforge]]

Cisco Meraki

2026-06-07T16:56:11Z

Wownyc: /* MX Series */ merge cells

{{StubNotice}}
{{Incomplete}}
{{Cleanup|Issue 1 = References and links do not have proper formatting.}}
{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by [[Cisco Systems, Inc.|Cisco]] in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==
Since around 2017, hardware has been locked down with SecureBoot.<ref>{{Cite web|url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895|title=Cisco Meraki MX68W - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881|title=MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub|access-date=2026-06-07}}</ref> Hardware released before 2017, without SecureBoot enabled, or with SecureBoot exploits may be reflashable to OpenWrt.<ref name="watchmysys" />

The company was previously friendly to open-source.<ref name="watchmysys">{{Cite web|url=https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/|title=Breaking secure boot on the Meraki Z3 and Meraki Go GX20 {{!}} «WatchMySys» Blog|access-date=2026-06-07}}</ref><ref name="only_took_four_months">{{Cite web|url=https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4|title=Adding OpenWrt support for Meraki MR53 - #4 by e97 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://forum.archive.openwrt.org/viewtopic.php?id=63838|title=Cisco Meraki MS220-8P|access-date=2026-06-07}}</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref name="mr44">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5|title=OpenWrt support for Meraki MR44 - #5 by sumo - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64|title=OpenWrt support for Meraki MR46 - #64 by hmartin - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref> and/or releases source code that doesn't build.<ref>{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60|title=OpenWrt support for Meraki MR46 - #60 by hmartin - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46" />

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>{{Cite web|url=https://github.com/riptidewave93/LEDE-MR33/issues/13|title=Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub|access-date=2026-06-07}}</ref>

===User freedom===
{{Incomplete section}}

===User privacy===
{{Incomplete section}}

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===
{{Incomplete section}}

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx60 [OpenWrt Wiki] Meraki MX60]
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |[https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32 Support for Cisco Meraki MX80 - #30 by meshpoint - For Developers - OpenWrt Forum]
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| rowspan="2" align="left" |MX64
| align="left" |MX64
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| rowspan="2" align="left" |[https://openwrt.org/toh/meraki/mx64 [OpenWrt Wiki] Meraki MX64 and MX64W]
|-
| align="left" |MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| rowspan="2" align="left" |MX65
| align="left" |MX65
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| rowspan="2" align="left" |[https://openwrt.org/toh/meraki/mx65w [OpenWrt Wiki] Meraki MX65 and MX65W]
|-
| align="left" |MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| rowspan="3" align="left" |MX67
| align="left" |MX67
| rowspan="6" align="right" |2018-08-28<ref>{{Cite web |date=2018-08-28 |title=A New MX Lineup for the Modern Branch {{!}} The Meraki Blog |url=https://meraki.cisco.com/blog/2018/08/a-new-mx-lineup-for-the-modern-branch/ |url-status=live |archive-url=https://web.archive.org/web/20250823150602/https://meraki.cisco.com/blog/2018/08/a-new-mx-lineup-for-the-modern-branch/ |archive-date=2025-08-23 |access-date=2026-06-07 |website=Cisco Meraki Blog}}</ref>
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX67W
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX67C
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| rowspan="3" align="left" |MX68
| align="left" |MX68
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68W
| align="left" |
| align="left" |Yes<ref>{{Cite web |date=2022-08-19 |title=Cisco Meraki MX68W - #3 by hurricos - For Developers - OpenWrt Forum |url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/3 |url-status=live |access-date=2026-06-07}}</ref>
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895 Cisco Meraki MX68W - For Developers - OpenWrt Forum]
|-
| align="left" |MX68CW
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3 Meraki Mx105 lets see if we can figure this out - #3 by broncosis - For Developers - OpenWrt Forum]
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/support-for-meraki-mx85/207538 Support for Meraki MX85? - For Developers - OpenWrt Forum]
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |[https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26 Adding OpenWrt support for Meraki MR53 - #26 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr52 [OpenWrt Wiki] Meraki MR52]
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |[https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11 Flash Meraki MR32 NEW Method - #11 by darkm4n - Installing and Using OpenWrt - OpenWrt Forum]
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr18 [OpenWrt Wiki] Meraki MR18]
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |[https://openwrt.org/toh/meraki/mr34 [OpenWrt Wiki] Meraki MR34]
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr42 [OpenWrt Wiki] Meraki MR42]
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409 OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum]
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21 OpenWrt support for Meraki MR46 - #21 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |[https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097 MR36 bootloader uboot source code - For Developers - OpenWrt Forum]
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 Cisco Meraki MX68W - #13 by hmartin - For Developers - OpenWrt Forum] [https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 Support for Meraki MS120-8LP - For Developers - OpenWrt Forum] [https://github.com/halmartin/meraki-builder/issues/11 MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |[https://github.com/halmartin/meraki-builder/issues/23 Support Meraki MS225 (brumby)? · Issue #23 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:GPL violations]]

Cisco Meraki

2026-06-07T16:54:40Z

Wownyc: /* MX Series */

{{StubNotice}}
{{Incomplete}}
{{Cleanup|Issue 1 = References and links do not have proper formatting.}}
{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by [[Cisco Systems, Inc.|Cisco]] in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==
Since around 2017, hardware has been locked down with SecureBoot.<ref>{{Cite web|url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895|title=Cisco Meraki MX68W - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881|title=MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub|access-date=2026-06-07}}</ref> Hardware released before 2017, without SecureBoot enabled, or with SecureBoot exploits may be reflashable to OpenWrt.<ref name="watchmysys" />

The company was previously friendly to open-source.<ref name="watchmysys">{{Cite web|url=https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/|title=Breaking secure boot on the Meraki Z3 and Meraki Go GX20 {{!}} «WatchMySys» Blog|access-date=2026-06-07}}</ref><ref name="only_took_four_months">{{Cite web|url=https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4|title=Adding OpenWrt support for Meraki MR53 - #4 by e97 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://forum.archive.openwrt.org/viewtopic.php?id=63838|title=Cisco Meraki MS220-8P|access-date=2026-06-07}}</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref name="mr44">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5|title=OpenWrt support for Meraki MR44 - #5 by sumo - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64|title=OpenWrt support for Meraki MR46 - #64 by hmartin - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref> and/or releases source code that doesn't build.<ref>{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60|title=OpenWrt support for Meraki MR46 - #60 by hmartin - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46" />

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>{{Cite web|url=https://github.com/riptidewave93/LEDE-MR33/issues/13|title=Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub|access-date=2026-06-07}}</ref>

===User freedom===
{{Incomplete section}}

===User privacy===
{{Incomplete section}}

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===
{{Incomplete section}}

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx60 [OpenWrt Wiki] Meraki MX60]
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |[https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32 Support for Cisco Meraki MX80 - #30 by meshpoint - For Developers - OpenWrt Forum]
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| rowspan="2" align="left" |MX64
| align="left" |MX64
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx64 [OpenWrt Wiki] Meraki MX64 and MX64W]
|-
| align="left" |MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx64 [OpenWrt Wiki] Meraki MX64 and MX64W]
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| rowspan="2" align="left" |MX65
| align="left" |MX65
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx65w [OpenWrt Wiki] Meraki MX65 and MX65W]
|-
| align="left" |MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx65w [OpenWrt Wiki] Meraki MX65 and MX65W]
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| rowspan="3" align="left" |MX67
| align="left" |MX67
| rowspan="6" align="right" |2018-08-28<ref>{{Cite web |date=2018-08-28 |title=A New MX Lineup for the Modern Branch {{!}} The Meraki Blog |url=https://meraki.cisco.com/blog/2018/08/a-new-mx-lineup-for-the-modern-branch/ |url-status=live |archive-url=https://web.archive.org/web/20250823150602/https://meraki.cisco.com/blog/2018/08/a-new-mx-lineup-for-the-modern-branch/ |archive-date=2025-08-23 |access-date=2026-06-07 |website=Cisco Meraki Blog}}</ref>
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX67W
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX67C
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| rowspan="3" align="left" |MX68
| align="left" |MX68
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68W
| align="left" |
| align="left" |Yes<ref>{{Cite web |date=2022-08-19 |title=Cisco Meraki MX68W - #3 by hurricos - For Developers - OpenWrt Forum |url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/3 |url-status=live |access-date=2026-06-07}}</ref>
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895 Cisco Meraki MX68W - For Developers - OpenWrt Forum]
|-
| align="left" |MX68CW
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3 Meraki Mx105 lets see if we can figure this out - #3 by broncosis - For Developers - OpenWrt Forum]
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/support-for-meraki-mx85/207538 Support for Meraki MX85? - For Developers - OpenWrt Forum]
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |[https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26 Adding OpenWrt support for Meraki MR53 - #26 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr52 [OpenWrt Wiki] Meraki MR52]
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |[https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11 Flash Meraki MR32 NEW Method - #11 by darkm4n - Installing and Using OpenWrt - OpenWrt Forum]
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr18 [OpenWrt Wiki] Meraki MR18]
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |[https://openwrt.org/toh/meraki/mr34 [OpenWrt Wiki] Meraki MR34]
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr42 [OpenWrt Wiki] Meraki MR42]
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409 OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum]
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21 OpenWrt support for Meraki MR46 - #21 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |[https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097 MR36 bootloader uboot source code - For Developers - OpenWrt Forum]
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 Cisco Meraki MX68W - #13 by hmartin - For Developers - OpenWrt Forum] [https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 Support for Meraki MS120-8LP - For Developers - OpenWrt Forum] [https://github.com/halmartin/meraki-builder/issues/11 MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |[https://github.com/halmartin/meraki-builder/issues/23 Support Meraki MS225 (brumby)? · Issue #23 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:GPL violations]]

Cisco Meraki

2026-06-07T16:45:50Z

Wownyc: /* MX Series */ split products

{{StubNotice}}
{{Incomplete}}
{{Cleanup|Issue 1 = References and links do not have proper formatting.}}
{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by [[Cisco Systems, Inc.|Cisco]] in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==
Since around 2017, hardware has been locked down with SecureBoot.<ref>{{Cite web|url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895|title=Cisco Meraki MX68W - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881|title=MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub|access-date=2026-06-07}}</ref> Hardware released before 2017, without SecureBoot enabled, or with SecureBoot exploits may be reflashable to OpenWrt.<ref name="watchmysys" />

The company was previously friendly to open-source.<ref name="watchmysys">{{Cite web|url=https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/|title=Breaking secure boot on the Meraki Z3 and Meraki Go GX20 {{!}} «WatchMySys» Blog|access-date=2026-06-07}}</ref><ref name="only_took_four_months">{{Cite web|url=https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4|title=Adding OpenWrt support for Meraki MR53 - #4 by e97 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://forum.archive.openwrt.org/viewtopic.php?id=63838|title=Cisco Meraki MS220-8P|access-date=2026-06-07}}</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref name="mr44">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5|title=OpenWrt support for Meraki MR44 - #5 by sumo - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64|title=OpenWrt support for Meraki MR46 - #64 by hmartin - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref> and/or releases source code that doesn't build.<ref>{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60|title=OpenWrt support for Meraki MR46 - #60 by hmartin - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46" />

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>{{Cite web|url=https://github.com/riptidewave93/LEDE-MR33/issues/13|title=Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub|access-date=2026-06-07}}</ref>

===User freedom===
{{Incomplete section}}

===User privacy===
{{Incomplete section}}

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===
{{Incomplete section}}

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx60 [OpenWrt Wiki] Meraki MX60]
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |[https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32 Support for Cisco Meraki MX80 - #30 by meshpoint - For Developers - OpenWrt Forum]
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx64 [OpenWrt Wiki] Meraki MX64 and MX64W]
|-
| align="left" |MX64
| align="left" |MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx64 [OpenWrt Wiki] Meraki MX64 and MX64W]
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx65w [OpenWrt Wiki] Meraki MX65 and MX65W]
|-
| align="left" |MX65
| align="left" |MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx65w [OpenWrt Wiki] Meraki MX65 and MX65W]
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67W
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68W
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes<ref>{{Cite web |date=2022-08-19 |title=Cisco Meraki MX68W - #3 by hurricos - For Developers - OpenWrt Forum |url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/3 |url-status=live |access-date=2026-06-07}}</ref>
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895 Cisco Meraki MX68W - For Developers - OpenWrt Forum]
|-
| align="left" |MX68
| align="left" |MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3 Meraki Mx105 lets see if we can figure this out - #3 by broncosis - For Developers - OpenWrt Forum]
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/support-for-meraki-mx85/207538 Support for Meraki MX85? - For Developers - OpenWrt Forum]
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |[https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26 Adding OpenWrt support for Meraki MR53 - #26 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr52 [OpenWrt Wiki] Meraki MR52]
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |[https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11 Flash Meraki MR32 NEW Method - #11 by darkm4n - Installing and Using OpenWrt - OpenWrt Forum]
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr18 [OpenWrt Wiki] Meraki MR18]
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |[https://openwrt.org/toh/meraki/mr34 [OpenWrt Wiki] Meraki MR34]
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr42 [OpenWrt Wiki] Meraki MR42]
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409 OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum]
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21 OpenWrt support for Meraki MR46 - #21 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |[https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097 MR36 bootloader uboot source code - For Developers - OpenWrt Forum]
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 Cisco Meraki MX68W - #13 by hmartin - For Developers - OpenWrt Forum] [https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 Support for Meraki MS120-8LP - For Developers - OpenWrt Forum] [https://github.com/halmartin/meraki-builder/issues/11 MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |[https://github.com/halmartin/meraki-builder/issues/23 Support Meraki MS225 (brumby)? · Issue #23 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:GPL violations]]

Cisco Meraki

2026-06-07T16:38:26Z

Wownyc: /* MS Series */ oop

{{StubNotice}}
{{Incomplete}}
{{Cleanup|Issue 1 = References and links do not have proper formatting.}}
{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by [[Cisco Systems, Inc.|Cisco]] in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==
Since around 2017, hardware has been locked down with SecureBoot.<ref>{{Cite web|url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895|title=Cisco Meraki MX68W - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881|title=MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub|access-date=2026-06-07}}</ref> Hardware released before 2017, without SecureBoot enabled, or with SecureBoot exploits may be reflashable to OpenWrt.<ref name="watchmysys" />

The company was previously friendly to open-source.<ref name="watchmysys">{{Cite web|url=https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/|title=Breaking secure boot on the Meraki Z3 and Meraki Go GX20 {{!}} «WatchMySys» Blog|access-date=2026-06-07}}</ref><ref name="only_took_four_months">{{Cite web|url=https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4|title=Adding OpenWrt support for Meraki MR53 - #4 by e97 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://forum.archive.openwrt.org/viewtopic.php?id=63838|title=Cisco Meraki MS220-8P|access-date=2026-06-07}}</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref name="mr44">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5|title=OpenWrt support for Meraki MR44 - #5 by sumo - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64|title=OpenWrt support for Meraki MR46 - #64 by hmartin - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref> and/or releases source code that doesn't build.<ref>{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60|title=OpenWrt support for Meraki MR46 - #60 by hmartin - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46" />

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>{{Cite web|url=https://github.com/riptidewave93/LEDE-MR33/issues/13|title=Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub|access-date=2026-06-07}}</ref>

===User freedom===
{{Incomplete section}}

===User privacy===
{{Incomplete section}}

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===
{{Incomplete section}}

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx60 [OpenWrt Wiki] Meraki MX60]
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |[https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32 Support for Cisco Meraki MX80 - #30 by meshpoint - For Developers - OpenWrt Forum]
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx64 [OpenWrt Wiki] Meraki MX64 and MX64W]
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx65w [OpenWrt Wiki] Meraki MX65 and MX65W]
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895 Cisco Meraki MX68W - For Developers - OpenWrt Forum]
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3 Meraki Mx105 lets see if we can figure this out - #3 by broncosis - For Developers - OpenWrt Forum]
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/support-for-meraki-mx85/207538 Support for Meraki MX85? - For Developers - OpenWrt Forum]
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |[https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26 Adding OpenWrt support for Meraki MR53 - #26 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr52 [OpenWrt Wiki] Meraki MR52]
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |[https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11 Flash Meraki MR32 NEW Method - #11 by darkm4n - Installing and Using OpenWrt - OpenWrt Forum]
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr18 [OpenWrt Wiki] Meraki MR18]
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |[https://openwrt.org/toh/meraki/mr34 [OpenWrt Wiki] Meraki MR34]
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr42 [OpenWrt Wiki] Meraki MR42]
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409 OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum]
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21 OpenWrt support for Meraki MR46 - #21 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |[https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097 MR36 bootloader uboot source code - For Developers - OpenWrt Forum]
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 Cisco Meraki MX68W - #13 by hmartin - For Developers - OpenWrt Forum] [https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 Support for Meraki MS120-8LP - For Developers - OpenWrt Forum] [https://github.com/halmartin/meraki-builder/issues/11 MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |[https://github.com/halmartin/meraki-builder/issues/23 Support Meraki MS225 (brumby)? · Issue #23 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:GPL violations]]

Cisco Meraki

2026-06-07T16:37:13Z

Wownyc: /* Other products */ title

{{StubNotice}}
{{Incomplete}}
{{Cleanup|Issue 1 = References and links do not have proper formatting.}}
{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by [[Cisco Systems, Inc.|Cisco]] in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==
Since around 2017, hardware has been locked down with SecureBoot.<ref>{{Cite web|url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895|title=Cisco Meraki MX68W - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881|title=MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub|access-date=2026-06-07}}</ref> Hardware released before 2017, without SecureBoot enabled, or with SecureBoot exploits may be reflashable to OpenWrt.<ref name="watchmysys" />

The company was previously friendly to open-source.<ref name="watchmysys">{{Cite web|url=https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/|title=Breaking secure boot on the Meraki Z3 and Meraki Go GX20 {{!}} «WatchMySys» Blog|access-date=2026-06-07}}</ref><ref name="only_took_four_months">{{Cite web|url=https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4|title=Adding OpenWrt support for Meraki MR53 - #4 by e97 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://forum.archive.openwrt.org/viewtopic.php?id=63838|title=Cisco Meraki MS220-8P|access-date=2026-06-07}}</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref name="mr44">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5|title=OpenWrt support for Meraki MR44 - #5 by sumo - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64|title=OpenWrt support for Meraki MR46 - #64 by hmartin - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref> and/or releases source code that doesn't build.<ref>{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60|title=OpenWrt support for Meraki MR46 - #60 by hmartin - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46"/>

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>{{Cite web|url=https://github.com/riptidewave93/LEDE-MR33/issues/13|title=Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub|access-date=2026-06-07}}</ref>

===User freedom===
{{Incomplete section}}

===User privacy===
{{Incomplete section}}

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===
{{Incomplete section}}

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx60 [OpenWrt Wiki] Meraki MX60]
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |[https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32 Support for Cisco Meraki MX80 - #30 by meshpoint - For Developers - OpenWrt Forum]
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx64 [OpenWrt Wiki] Meraki MX64 and MX64W]
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx65w [OpenWrt Wiki] Meraki MX65 and MX65W]
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895 Cisco Meraki MX68W - For Developers - OpenWrt Forum]
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3 Meraki Mx105 lets see if we can figure this out - #3 by broncosis - For Developers - OpenWrt Forum]
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/support-for-meraki-mx85/207538 Support for Meraki MX85? - For Developers - OpenWrt Forum]
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |[https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26 Adding OpenWrt support for Meraki MR53 - #26 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr52 [OpenWrt Wiki] Meraki MR52]
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |[https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11 Flash Meraki MR32 NEW Method - #11 by darkm4n - Installing and Using OpenWrt - OpenWrt Forum]
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr18 [OpenWrt Wiki] Meraki MR18]
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |[https://openwrt.org/toh/meraki/mr34 [OpenWrt Wiki] Meraki MR34]
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr42 [OpenWrt Wiki] Meraki MR42]
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409 OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum]
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21 OpenWrt support for Meraki MR46 - #21 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |[https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097 MR36 bootloader uboot source code - For Developers - OpenWrt Forum]
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 Cisco Meraki MX68W - #13 by hmartin - For Developers - OpenWrt Forum] [https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 Support for Meraki MS120-8LP - For Developers - OpenWrt Forum] [https://github.com/halmartin/meraki-builder/issues/11 MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |[https://github.com/halmartin/meraki-builder/issues/23 Support Meraki MS225 (brumby)? · Issue #23 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:GPL violations]]

Cisco Meraki

2026-06-07T16:36:11Z

Wownyc: title

{{StubNotice}}
{{Incomplete}}
{{Cleanup|Issue 1 = References and links do not have proper formatting.}}
{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by [[Cisco Systems, Inc.|Cisco]] in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==
Since around 2017, hardware has been locked down with SecureBoot.<ref>{{Cite web|url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895|title=Cisco Meraki MX68W - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881|title=MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub|access-date=2026-06-07}}</ref> Hardware released before 2017, without SecureBoot enabled, or with SecureBoot exploits may be reflashable to OpenWrt.<ref name="watchmysys" />

The company was previously friendly to open-source.<ref name="watchmysys">{{Cite web|url=https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/|title=Breaking secure boot on the Meraki Z3 and Meraki Go GX20 {{!}} «WatchMySys» Blog|access-date=2026-06-07}}</ref><ref name="only_took_four_months">{{Cite web|url=https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4|title=Adding OpenWrt support for Meraki MR53 - #4 by e97 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://forum.archive.openwrt.org/viewtopic.php?id=63838|title=Cisco Meraki MS220-8P|access-date=2026-06-07}}</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref name="mr44">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5|title=OpenWrt support for Meraki MR44 - #5 by sumo - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64|title=OpenWrt support for Meraki MR46 - #64 by hmartin - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref> and/or releases source code that doesn't build.<ref>{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60|title=OpenWrt support for Meraki MR46 - #60 by hmartin - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46"/>

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>{{Cite web|url=https://github.com/riptidewave93/LEDE-MR33/issues/13|title=Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub|access-date=2026-06-07}}</ref>

===User freedom===
{{Incomplete section}}

===User privacy===
{{Incomplete section}}

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===
{{Incomplete section}}

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx60 [OpenWrt Wiki] Meraki MX60]
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |[https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32 Support for Cisco Meraki MX80 - #30 by meshpoint - For Developers - OpenWrt Forum]
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx64 [OpenWrt Wiki] Meraki MX64 and MX64W]
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx65w [OpenWrt Wiki] Meraki MX65 and MX65W]
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895 Cisco Meraki MX68W - For Developers - OpenWrt Forum]
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3 Meraki Mx105 lets see if we can figure this out - #3 by broncosis - For Developers - OpenWrt Forum]
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/support-for-meraki-mx85/207538 Support for Meraki MX85? - For Developers - OpenWrt Forum]
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |[https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26 Adding OpenWrt support for Meraki MR53 - #26 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr52 [OpenWrt Wiki] Meraki MR52]
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |[https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11 Flash Meraki MR32 NEW Method - #11 by darkm4n - Installing and Using OpenWrt - OpenWrt Forum]
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr18 [OpenWrt Wiki] Meraki MR18]
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |[https://openwrt.org/toh/meraki/mr34 [OpenWrt Wiki] Meraki MR34]
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr42 [OpenWrt Wiki] Meraki MR42]
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409 OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum]
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21 OpenWrt support for Meraki MR46 - #21 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |[https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097 MR36 bootloader uboot source code - For Developers - OpenWrt Forum]
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 Cisco Meraki MX68W - #13 by hmartin - For Developers - OpenWrt Forum] [https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 Support for Meraki MS120-8LP - For Developers - OpenWrt Forum] [https://github.com/halmartin/meraki-builder/issues/11 MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |[https://github.com/halmartin/meraki-builder/issues/23 Support Meraki MS225 (brumby)? · Issue #23 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20]
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:GPL violations]]

Cisco Meraki

2026-06-07T16:35:30Z

Wownyc: titles

{{StubNotice}}
{{Incomplete}}
{{Cleanup|Issue 1 = References and links do not have proper formatting.}}
{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by [[Cisco Systems, Inc.|Cisco]] in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==
Since around 2017, hardware has been locked down with SecureBoot.<ref>{{Cite web|url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895|title=Cisco Meraki MX68W - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881|title=MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub|access-date=2026-06-07}}</ref> Hardware released before 2017, without SecureBoot enabled, or with SecureBoot exploits may be reflashable to OpenWrt.<ref name="watchmysys" />

The company was previously friendly to open-source.<ref name="watchmysys">{{Cite web|url=https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/|title=Breaking secure boot on the Meraki Z3 and Meraki Go GX20 {{!}} «WatchMySys» Blog|access-date=2026-06-07}}</ref><ref name="only_took_four_months">{{Cite web|url=https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4|title=Adding OpenWrt support for Meraki MR53 - #4 by e97 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://forum.archive.openwrt.org/viewtopic.php?id=63838|title=Cisco Meraki MS220-8P|access-date=2026-06-07}}</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref name="mr44">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5|title=OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64|title=OpenWrt support for Meraki MR46 - #64 by hmartin - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref> and/or releases source code that doesn't build.<ref>{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60|title=OpenWrt support for Meraki MR46 - #60 by hmartin - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46"/>

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>{{Cite web|url=https://github.com/riptidewave93/LEDE-MR33/issues/13|title=Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub|access-date=2026-06-07}}</ref>

===User freedom===
{{Incomplete section}}

===User privacy===
{{Incomplete section}}

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===
{{Incomplete section}}

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx60 [OpenWrt Wiki] Meraki MX60]
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |[https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32 Support for Cisco Meraki MX80 - #30 by meshpoint - For Developers - OpenWrt Forum]
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx64 [OpenWrt Wiki] Meraki MX64 and MX64W]
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx65w [OpenWrt Wiki] Meraki MX65 and MX65W]
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895 Cisco Meraki MX68W - For Developers - OpenWrt Forum]
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3 Meraki Mx105 lets see if we can figure this out - #3 by broncosis - For Developers - OpenWrt Forum]
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/support-for-meraki-mx85/207538 Support for Meraki MX85? - For Developers - OpenWrt Forum]
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |[https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26 Adding OpenWrt support for Meraki MR53 - #26 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr52 [OpenWrt Wiki] Meraki MR52]
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |[https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11 Flash Meraki MR32 NEW Method - #11 by darkm4n - Installing and Using OpenWrt - OpenWrt Forum]
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr18 [OpenWrt Wiki] Meraki MR18]
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |[https://openwrt.org/toh/meraki/mr34 [OpenWrt Wiki] Meraki MR34]
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr42 [OpenWrt Wiki] Meraki MR42]
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409 OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum]
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21 OpenWrt support for Meraki MR46 - #21 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |[https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097 MR36 bootloader uboot source code - For Developers - OpenWrt Forum]
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 Cisco Meraki MX68W - #13 by hmartin - For Developers - OpenWrt Forum] [https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 Support for Meraki MS120-8LP - For Developers - OpenWrt Forum] [https://github.com/halmartin/meraki-builder/issues/11 MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |[https://github.com/halmartin/meraki-builder/issues/23 Support Meraki MS225 (brumby)? · Issue #23 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20]
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:GPL violations]]

Cisco Meraki

2026-06-07T16:31:07Z

Wownyc: year

{{StubNotice}}
{{Incomplete}}
{{Cleanup|Issue 1 = References and links do not have proper formatting.}}
{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by [[Cisco Systems, Inc.|Cisco]] in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==
Since around 2017, hardware has been locked down with SecureBoot.<ref>{{Cite web|url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895|title=Cisco Meraki MX68W - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881|title=MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub|access-date=2026-06-07}}</ref> Hardware released before 2017, without SecureBoot enabled, or with SecureBoot exploits may be reflashable to OpenWrt.<ref name="watchmysys" />

The company was previously friendly to open-source.<ref name="watchmysys">{{Cite web|url=https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/|title=Breaking secure boot on the Meraki Z3 and Meraki Go GX20 {{!}} «WatchMySys» Blog|access-date=2026-06-07}}</ref><ref name="only_took_four_months">{{Cite web|url=https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4|title=Adding OpenWrt support for Meraki MR53 - #4 by e97 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://forum.archive.openwrt.org/viewtopic.php?id=63838|title=Cisco Meraki MS220-8P|access-date=2026-06-07}}</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref name="mr44">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5|title=OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64|title=OpenWrt support for Meraki MR46 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref> and/or releases source code that doesn't build.<ref>{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60|title=OpenWrt support for Meraki MR46 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46"/>

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>{{Cite web|url=https://github.com/riptidewave93/LEDE-MR33/issues/13|title=Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub|access-date=2026-06-07}}</ref>

===User freedom===
{{Incomplete section}}

===User privacy===
{{Incomplete section}}

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===
{{Incomplete section}}

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx60 [OpenWrt Wiki] Meraki MX60]
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |[https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32 Support for Cisco Meraki MX80 - #30 by meshpoint - For Developers - OpenWrt Forum]
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx64 [OpenWrt Wiki] Meraki MX64 and MX64W]
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx65w [OpenWrt Wiki] Meraki MX65 and MX65W]
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895 Cisco Meraki MX68W - For Developers - OpenWrt Forum]
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3 Meraki Mx105 lets see if we can figure this out - #3 by broncosis - For Developers - OpenWrt Forum]
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/support-for-meraki-mx85/207538 Support for Meraki MX85? - For Developers - OpenWrt Forum]
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |[https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26 Adding OpenWrt support for Meraki MR53 - #26 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr52 [OpenWrt Wiki] Meraki MR52]
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |[https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11 Flash Meraki MR32 NEW Method - #11 by darkm4n - Installing and Using OpenWrt - OpenWrt Forum]
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr18 [OpenWrt Wiki] Meraki MR18]
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |[https://openwrt.org/toh/meraki/mr34 [OpenWrt Wiki] Meraki MR34]
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr42 [OpenWrt Wiki] Meraki MR42]
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409 OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum]
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21 OpenWrt support for Meraki MR46 - #21 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |[https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097 MR36 bootloader uboot source code - For Developers - OpenWrt Forum]
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 Cisco Meraki MX68W - #13 by hmartin - For Developers - OpenWrt Forum] [https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 Support for Meraki MS120-8LP - For Developers - OpenWrt Forum] [https://github.com/halmartin/meraki-builder/issues/11 MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |[https://github.com/halmartin/meraki-builder/issues/23 Support Meraki MS225 (brumby)? · Issue #23 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20]
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:GPL violations]]

Cisco Meraki

2026-06-07T16:30:03Z

Wownyc: cleanup

{{StubNotice}}
{{Incomplete}}
{{Cleanup|Issue 1 = References and links do not have proper formatting.}}
{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by [[Cisco Systems, Inc.|Cisco]] in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==
Since around 2017, hardware has been locked down with SecureBoot.<ref>{{Cite web|url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895|title=Cisco Meraki MX68W - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881|title=MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub|access-date=2026-06-07}}</ref> Hardware before 2018, or with SecureBoot exploits may be reflashable to OpenWrt.<ref name="watchmysys" />

The company was previously friendly to open-source.<ref name="watchmysys">{{Cite web|url=https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/|title=Breaking secure boot on the Meraki Z3 and Meraki Go GX20 {{!}} «WatchMySys» Blog|access-date=2026-06-07}}</ref><ref name="only_took_four_months">{{Cite web|url=https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4|title=Adding OpenWrt support for Meraki MR53 - #4 by e97 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://forum.archive.openwrt.org/viewtopic.php?id=63838|title=Cisco Meraki MS220-8P|access-date=2026-06-07}}</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref name="mr44">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5|title=OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64|title=OpenWrt support for Meraki MR46 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref> and/or releases source code that doesn't build.<ref>{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60|title=OpenWrt support for Meraki MR46 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46"/>

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>{{Cite web|url=https://github.com/riptidewave93/LEDE-MR33/issues/13|title=Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub|access-date=2026-06-07}}</ref>

===User freedom===
{{Incomplete section}}

===User privacy===
{{Incomplete section}}

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===
{{Incomplete section}}

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx60 [OpenWrt Wiki] Meraki MX60]
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |[https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32 Support for Cisco Meraki MX80 - #30 by meshpoint - For Developers - OpenWrt Forum]
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx64 [OpenWrt Wiki] Meraki MX64 and MX64W]
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx65w [OpenWrt Wiki] Meraki MX65 and MX65W]
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895 Cisco Meraki MX68W - For Developers - OpenWrt Forum]
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3 Meraki Mx105 lets see if we can figure this out - #3 by broncosis - For Developers - OpenWrt Forum]
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/support-for-meraki-mx85/207538 Support for Meraki MX85? - For Developers - OpenWrt Forum]
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |[https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26 Adding OpenWrt support for Meraki MR53 - #26 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr52 [OpenWrt Wiki] Meraki MR52]
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |[https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11 Flash Meraki MR32 NEW Method - #11 by darkm4n - Installing and Using OpenWrt - OpenWrt Forum]
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239 Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/ OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr18 [OpenWrt Wiki] Meraki MR18]
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |[https://openwrt.org/toh/meraki/mr34 [OpenWrt Wiki] Meraki MR34]
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr42 [OpenWrt Wiki] Meraki MR42]
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409 OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum]
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21 OpenWrt support for Meraki MR46 - #21 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |[https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097 MR36 bootloader uboot source code - For Developers - OpenWrt Forum]
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 Cisco Meraki MX68W - #13 by hmartin - For Developers - OpenWrt Forum] [https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 Support for Meraki MS120-8LP - For Developers - OpenWrt Forum] [https://github.com/halmartin/meraki-builder/issues/11 MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |[https://github.com/halmartin/meraki-builder/issues/23 Support Meraki MS225 (brumby)? · Issue #23 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/ Breaking secure boot on the Meraki Z3 and Meraki Go GX20]
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:GPL violations]]

Cisco Meraki

2026-06-07T16:26:52Z

Wownyc: continue cleanup

{{StubNotice}}
{{Incomplete}}
{{Cleanup|Issue 1 = References and links do not have proper formatting.}}
{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by [[Cisco Systems, Inc.|Cisco]] in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==
Since around 2017, hardware has been locked down with SecureBoot.<ref>{{Cite web|url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895|title=Cisco Meraki MX68W - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881|title=MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub|access-date=2026-06-07}}</ref> Hardware before 2018, or with SecureBoot exploits may be reflashable to OpenWrt.<ref name="watchmysys" />

The company was previously friendly to open-source.<ref name="watchmysys">{{Cite web|url=https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/|title=Breaking secure boot on the Meraki Z3 and Meraki Go GX20 {{!}} «WatchMySys» Blog|access-date=2026-06-07}}</ref><ref name="only_took_four_months">{{Cite web|url=https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4|title=Adding OpenWrt support for Meraki MR53 - #4 by e97 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://forum.archive.openwrt.org/viewtopic.php?id=63838|title=Cisco Meraki MS220-8P|access-date=2026-06-07}}</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref name="mr44">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5|title=OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64|title=OpenWrt support for Meraki MR46 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref> and/or releases source code that doesn't build.<ref>{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60|title=OpenWrt support for Meraki MR46 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46"/>

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>{{Cite web|url=https://github.com/riptidewave93/LEDE-MR33/issues/13|title=Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub|access-date=2026-06-07}}</ref>

===User freedom===
{{Incomplete section}}

===User privacy===
{{Incomplete section}}

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===
{{Incomplete section}}

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx60| [OpenWrt Wiki] Meraki MX60]
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |[https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32| Support for Cisco Meraki MX80 - #30 by meshpoint - For Developers - OpenWrt Forum]
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx64| [OpenWrt Wiki] Meraki MX64 and MX64W]
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx65w| [OpenWrt Wiki] Meraki MX65 and MX65W]
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895| Cisco Meraki MX68W - For Developers - OpenWrt Forum]
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3| Meraki Mx105 lets see if we can figure this out - #3 by broncosis - For Developers - OpenWrt Forum]
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/support-for-meraki-mx85/207538| Support for Meraki MX85? - For Developers - OpenWrt Forum]
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |[https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26| Adding OpenWrt support for Meraki MR53 - #26 by hmartin - For Developers - OpenWrt Forum]
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr52| [OpenWrt Wiki] Meraki MR52]
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |[https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11| Flash Meraki MR32 NEW Method - #11 by darkm4n - Installing and Using OpenWrt - OpenWrt Forum]
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13| Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239| Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/| OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/| OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr18| [OpenWrt Wiki] Meraki MR18]
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |[https://openwrt.org/toh/meraki/mr34| [OpenWrt Wiki] Meraki MR34]
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr42| [OpenWrt Wiki] Meraki MR42]
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409| OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum]
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21| OpenWrt support for Meraki MR46 - For Developers - OpenWrt Forum]
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |[https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097| MR36 bootloader uboot source code - For Developers - OpenWrt Forum]
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13| Cisco Meraki MX68W - #13 by hmartin - For Developers - OpenWrt Forum] [https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212| Support for Meraki MS120-8LP - For Developers - OpenWrt Forum] [https://github.com/halmartin/meraki-builder/issues/11| MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |[https://github.com/halmartin/meraki-builder/issues/23| Support Meraki MS225 (brumby)? · Issue #23 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/| Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/| Breaking secure boot on the Meraki Z3 and Meraki Go GX20]
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:GPL violations]]

Cisco Meraki

2026-06-07T16:23:48Z

Wownyc: continue cleanup

{{StubNotice}}
{{Incomplete}}
{{Cleanup|Issue 1 = References and links do not have proper formatting.}}
{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by [[Cisco Systems, Inc.|Cisco]] in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==
Since around 2017, hardware has been locked down with SecureBoot.<ref>{{Cite web|url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895|title=Cisco Meraki MX68W - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881|title=MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub|access-date=2026-06-07}}</ref> Hardware before 2018, or with SecureBoot exploits may be reflashable to OpenWrt.<ref name="watchmysys" />

The company was previously friendly to open-source.<ref name="watchmysys">{{Cite web|url=https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/|title=Breaking secure boot on the Meraki Z3 and Meraki Go GX20 {{!}} «WatchMySys» Blog|access-date=2026-06-07}}</ref><ref name="only_took_four_months">{{Cite web|url=https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4|title=Adding OpenWrt support for Meraki MR53 - #4 by e97 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://forum.archive.openwrt.org/viewtopic.php?id=63838|title=Cisco Meraki MS220-8P|access-date=2026-06-07}}</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref name="mr44">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5|title=OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64|title=OpenWrt support for Meraki MR46 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref> and/or releases source code that doesn't build.<ref>{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60|title=OpenWrt support for Meraki MR46 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46"/>

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>{{Cite web|url=https://github.com/riptidewave93/LEDE-MR33/issues/13|title=Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub|access-date=2026-06-07}}</ref>

===User freedom===
{{Incomplete section}}

===User privacy===
{{Incomplete section}}

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===
{{Incomplete section}}

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx60| [OpenWrt Wiki] Meraki MX60]
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |[https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32| Support for Cisco Meraki MX80 - #30 by meshpoint - For Developers - OpenWrt Forum]
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx64| [OpenWrt Wiki] Meraki MX64 and MX64W]
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx65w| [OpenWrt Wiki] Meraki MX65 and MX65W]
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/support-for-meraki-mx85/207538
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr52| [OpenWrt Wiki] Meraki MR52]
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |[https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11| Flash Meraki MR32 NEW Method - #11 by darkm4n - Installing and Using OpenWrt - OpenWrt Forum]
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13| Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |[https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239| Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub]
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/| OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |[https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/| OpenWrt for Meraki MR20, MR70, Go GR10, and Go GR60 | «WatchMySys» Blog]
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr18| [OpenWrt Wiki] Meraki MR18]
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |[https://openwrt.org/toh/meraki/mr34| [OpenWrt Wiki] Meraki MR34]
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mr42| [OpenWrt Wiki] Meraki MR42]
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409| OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum]
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |[https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21| OpenWrt support for Meraki MR46 - For Developers - OpenWrt Forum]
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |[https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097| MR36 bootloader uboot source code - For Developers - OpenWrt Forum]
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |[https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13| Cisco Meraki MX68W - #13 by hmartin - For Developers - OpenWrt Forum] [https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212| Support for Meraki MS120-8LP - For Developers - OpenWrt Forum] [https://github.com/halmartin/meraki-builder/issues/11| MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |[https://github.com/halmartin/meraki-builder/issues/23| Support Meraki MS225 (brumby)? · Issue #23 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/| Breaking secure boot on the Meraki Z3 and Meraki Go GX20 | «WatchMySys» Blog]
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/| Breaking secure boot on the Meraki Z3 and Meraki Go GX20]
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:GPL violations]]

Cisco Meraki

2026-06-07T16:13:44Z

Wownyc: continue cleanup

{{StubNotice}}
{{Incomplete}}
{{Cleanup|Issue 1 = References and links do not have proper formatting.}}
{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by [[Cisco Systems, Inc.|Cisco]] in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==
Since around 2017, hardware has been locked down with SecureBoot.<ref>{{Cite web|url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895|title=Cisco Meraki MX68W - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881|title=MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub|access-date=2026-06-07}}</ref> Hardware before 2018, or with SecureBoot exploits may be reflashable to OpenWrt.<ref name="watchmysys" />

The company was previously friendly to open-source.<ref name="watchmysys">{{Cite web|url=https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/|title=Breaking secure boot on the Meraki Z3 and Meraki Go GX20|access-date=2026-06-07}}</ref><ref name="only_took_four_months">{{Cite web|url=https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4|title=Adding OpenWrt support for Meraki MR53|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://forum.archive.openwrt.org/viewtopic.php?id=63838|title=Cisco Meraki MS220-8P|access-date=2026-06-07}}</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref name="mr44">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5|title=OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64|title=OpenWrt support for Meraki MR46 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref> and/or releases source code that doesn't build.<ref>{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60|title=OpenWrt support for Meraki MR46 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46"/>

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>{{Cite web|url=https://github.com/riptidewave93/LEDE-MR33/issues/13|title=Not working on U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700) · Issue #13 · riptidewave93/LEDE-MR33 · GitHub|access-date=2026-06-07}}</ref>

===User freedom===
{{Incomplete section}}

===User privacy===
{{Incomplete section}}

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===
{{Incomplete section}}

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |[https://openwrt.org/toh/meraki/mx60| [OpenWrt Wiki] Meraki MX60]
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |[https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32| Support for Cisco Meraki MX80 - #30 by meshpoint - For Developers - OpenWrt Forum]
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx64
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/support-for-meraki-mx85/207538
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr52
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr18
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |https://openwrt.org/toh/meraki/mr34
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr42
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 https://github.com/halmartin/meraki-builder/issues/11
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |[https://github.com/halmartin/meraki-builder/issues/23| Support Meraki MS225 (brumby)? · Issue #23 · halmartin/meraki-builder · GitHub]
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/| Breaking secure boot on the Meraki Z3 and Meraki Go GX20]
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |[https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/| Breaking secure boot on the Meraki Z3 and Meraki Go GX20]
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:GPL violations]]

Cisco Meraki

2026-06-07T16:05:03Z

Wownyc: cleanup

{{StubNotice}}
{{Incomplete}}
{{Cleanup|Issue 1 = References and links do not have proper formatting.}}
{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by [[Cisco Systems, Inc.|Cisco]] in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==
Since around 2017, hardware has been locked down with SecureBoot.<ref>{{Cite web|url=https://forum.openwrt.org/t/cisco-meraki-mx68w/134895|title=Cisco Meraki MX68W - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881|title=MS120-8LP Compatibility · Issue #11 · halmartin/meraki-builder · GitHub|access-date=2026-06-07}}</ref> Hardware before 2018, or with SecureBoot exploits may be reflashable to OpenWrt.<ref name="watchmysys" />

The company was previously friendly to open-source.<ref name="watchmysys">{{Cite web|url=https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/|title=Breaking secure boot on the Meraki Z3 and Meraki Go GX20|access-date=2026-06-07}}</ref><ref name="only_took_four_months">{{Cite web|url=https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4|title=Adding OpenWrt support for Meraki MR53|access-date=2026-06-07}}</ref><ref>{{Cite web|url=https://forum.archive.openwrt.org/viewtopic.php?id=63838|title=Cisco Meraki MS220-8P|access-date=2026-06-07}}</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref name="mr44">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5|title=OpenWrt support for Meraki MR44 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref><ref name="mr46">{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64|title=OpenWrt support for Meraki MR46 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref> and/or releases source code that doesn't build.<ref>{{Cite web|url=https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60|title=OpenWrt support for Meraki MR46 - For Developers - OpenWrt Forum|access-date=2026-06-07}}</ref>

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>https://github.com/riptidewave93/LEDE-MR33/issues/13</ref>

===User freedom===
{{Incomplete section}}

===User privacy===
{{Incomplete section}}

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===
{{Incomplete section}}

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx60
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx64
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/support-for-meraki-mx85/207538
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr52
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr18
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |https://openwrt.org/toh/meraki/mr34
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr42
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 https://github.com/halmartin/meraki-builder/issues/11
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |https://github.com/halmartin/meraki-builder/issues/23
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:GPL violations]]

Flashforge Flash Studio mandatory slicer advertising and third-party slicer lockout

2026-06-07T02:14:14Z

Wownyc: add category

{{IncidentCargo
|IncidentName=FlashForge Flash Studio mandatory slicer advertising and third-party slicer lockout
|Company=FlashForge
|StartDate=2025-03-26
|EndDate=
|IncidentType=Vendor lock-in via firmware update; in-app advertising; software license dispute
|Description=FlashForge firmware updates broke mainline OrcaSlicer network printing on Adventurer 5M & AD5X printers; replacement Flash Studio slicer carries banner ads.
|AffectedProducts=Adventurer 5M, Adventurer 5M Pro, AD5X, Creator 5, Guider 3 Ultra
|Status=Ongoing
}}

'''FlashForge Flash Studio mandatory slicer advertising and third-party slicer lockout''' refers to a sequence of FlashForge software & firmware changes between March 2025 & May 2026 that forced owners of the Adventurer 5M, Adventurer 5M Pro, AD5X, Creator 5, & Guider 3 Ultra onto FlashForge's Flash Studio slicer (a rebranded fork of OrcaSlicer) while progressively breaking remote-print connectivity from mainline OrcaSlicer & earlier FlashForge slicer versions.<ref name="ff-service-notice">{{Cite web |url=https://www.flashforge.com/blogs/news/service-upgrade-notification |title=Service Upgrade Notification |date=2025-02-22 |website=Flashforge |access-date=May 22, 2026}}</ref><ref name="orca-10260">{{Cite web |url=https://github.com/OrcaSlicer/OrcaSlicer/issues/10260 |title=Device Section of Orca Slicer not working with Flashforge AD5M (Issue #10260) |date=2025-07-28 |website=GitHub: OrcaSlicer/OrcaSlicer |access-date=May 22, 2026}}</ref> The replacement slicer carries a banner promoting a paid Meshy.ai subscription inside its printer-management view.<ref name="ff-meshy">{{Cite web |url=https://www.flashforge.com/blogs/news/flashforge-meshy-ai |title=Flashforge × Meshy AI: From AI Ideas to Real Prints |date=2026-05-20 |website=Flashforge |access-date=May 22, 2026}}</ref>

==Background==

Before the March 2025 service migration, FlashForge's Adventurer 5M series shipped with an open network architecture that exposed a slicer socket on TCP port 8899. The port assignment is documented in an October 13, 2025 comment on OrcaSlicer issue #10260 by user Jarli01, who posted nmap output against an Adventurer 5M reading ''"8899/tcp open ospf-lite"'' alongside ''"8898/tcp open unknown"'' and an ephemeral port. It is further documented in OrcaSlicer issue #10112, whose body contains a user-supplied Python snippet (placed inside a collapsed `<details>` block on the GitHub UI) initialising a socket client with ''<code>def __init__(self, printer_ip, printer_port=8899)</code>'' and issuing G-code queries such as `~M105` and `~M27` directly to the printer. The open socket allowed mainline OrcaSlicer & third-party tools to discover printers, send sliced jobs, & query printer status directly over the local network.<ref name="orca-10260" /><ref name="orca-10112">{{Cite web |url=https://github.com/OrcaSlicer/OrcaSlicer/issues/10112 |title=Flashforge adventurer (5M) Device menu (Issue #10112) |date=2025-07-10 |website=GitHub: OrcaSlicer/OrcaSlicer |access-date=May 22, 2026}}</ref><ref name="klipper-xblax">{{Cite web |url=https://github.com/xblax/flashforge_ad5m_klipper_mod |title=Unofficial mod for Flashforge Adventurer 5M (Pro) 3D printers to run Moonraker, custom Klipper, Mainsail and Fluidd |website=GitHub: xblax/flashforge_ad5m_klipper_mod |access-date=May 22, 2026}}</ref> FlashForge distributed a desktop slicer called Orca-Flashforge (a fork of the GPL/AGPL-licensed OrcaSlicer by SoftFever) & a companion mobile app called Flash Maker; an August 15, 2024 FlashForge blog post described Orca-Flashforge as tailored for the Adventurer 5M series & Guider 3 Ultra with Flash Maker integration.<ref name="ff-orca-guide">{{Cite web |url=https://www.flashforge.com/blogs/news/orca-and-orca-flashforge-a-comprehensive-guide |title=Orca and Orca-Flashforge: A Comprehensive Guide |date=2024-08-15 |website=Flashforge |access-date=May 22, 2026}}</ref> Adventurer 5M firmware 2.6.5 (April 11, 2024) explicitly added ''"Support Orca-Flashforge connection"'' & a LAN mode, & version 2.7.2 (July 5, 2024) added Orca-Flashforge online connection support.<ref name="ff-5m-changelog">{{Cite web |url=https://www.flashforge.com/a/docs/adventurer-5m-series/adventurer-5m-series-firmware-update-log |title=Adventurer 5M Series Firmware Update Log |website=Flashforge |access-date=May 22, 2026}}</ref>

==Mandatory migration to Flash Studio==

In early 2025 FlashForge published a ''"Service Upgrade Notification"'' announcing the retirement of its legacy server infrastructure on March 26, 2025, & requiring owners to update by March 25, 2025. The notification set hard version floors: Adventurer 5M, Adventurer 5M Pro, & Guider 3 Ultra firmware to v3.1.0 or later; Orca-Flashforge desktop slicer to v1.3.0 or later; & the Flash Maker mobile app to v2.0.0 or later.<ref name="ff-service-notice" /> FlashForge described the change as ''"domain adjustments and enhanced testing protocols"'' & ''"rigorous interface validation and cross-version testing,"'' without itemising which third-party clients would be affected.<ref name="ff-service-notice" /> Orca-Flashforge was subsequently rebranded to '''Flash Studio Desktop''' & Flash Maker was rebranded to '''Flash Studio Mobile'''; the rename appears in the FlashForge website's software navigation menu, which lists ''"Flash Studio Desktop (formerly Orca-Flashforge)"'' & ''"Flash Studio Mobile (formerly Flash Maker)"'' on the May 20, 2026 Meshy.ai partnership announcement & adjacent pages.<ref name="ff-meshy" /> FlashForge's published Adventurer 5M firmware changelog does not explicitly document the port-access changes that block mainline OrcaSlicer; the connection failures are documented in third-party GitHub issues opened on or after July 10, 2025, against printers running post-migration firmware.<ref name="ff-5m-changelog" /><ref name="orca-10112" /><ref name="orca-10260" /> Rossmann noted that the undocumented removal is compounded by auto-update defaults, arguing that expecting consumers to read a changelog before every firmware update is unreasonable.<ref name="rossmann-ff" />

==In-app advertising==

On May 20, 2026 FlashForge announced a partnership with Meshy.ai, an AI image-to-3D-model service, with integration surfaced inside Flash Studio.<ref name="ff-meshy" /><ref name="prnewswire-meshy">{{Cite web |url=https://www.prnewswire.com/news-releases/flashforge-and-meshy-partner-to-bring-ai-image-to-3d-directly-into-consumer-multi-color-printing-302778460.html |title=FlashForge and Meshy Partner to Bring AI Image-to-3D Directly Into Consumer Multi-Color Printing |date=2026-05-21 |website=PR Newswire |access-date=May 22, 2026}}</ref> The blog post promoted a discounted Meshy subscription via Flash Studio.<ref name="ff-meshy" />

FlashForge wrote in the partnership announcement:

<blockquote>''By downloading Flash Studio, users can unlock a special $1 Meshy membership offer and explore AI-powered 3D creation for themselves.''</blockquote><ref name="ff-meshy" />

The promotion is presented as a banner inside the printer-management view of Flash Studio Desktop, where users monitor their printers' status.<ref name="ff-meshy" /> The banner is visible above the fleet list in the screenshot below.

[[File:Flashforge-flash-studio-meshy-banner.webp|thumb|center|600px|Meshy.ai banner advertisement promoting the $1 monthly membership offer, shown above the Flash Studio Desktop printer-management view containing eleven Adventurer 5M-series printers.]]

Trade-press coverage by Joris Peels at 3DPrint.com (May 20, 2026) described the Meshy integration as a software feature rather than advertising,<ref name="3dprint-peels">{{Cite web |url=https://3dprint.com/326162/flashforge-bets-on-meshy-ai-as-desktop-3d-printing-battle-intensifies/ |title=Flashforge Bets on Meshy AI as Desktop 3D Printing Battle Intensifies |last=Peels |first=Joris |date=2026-05-20 |website=3DPrint.com |access-date=May 22, 2026}}</ref> while VoxelMatters' coverage on the same day focused on the functional workflow & did not mention the $1 promotional offer.<ref name="voxelmatters-meshy">{{Cite web |url=https://www.voxelmatters.com/flashforge-integrates-meshy-ai-into-flash-studio-enabling-image-to-3d-to-multi-color-print-in-one-click/ |title=FlashForge integrates Meshy AI into Flash Studio, enabling image-to-3D to multi-color print in one click |date=2026-05-20 |website=VoxelMatters |access-date=May 22, 2026}}</ref>

Consumer advocate Louis Rossmann criticized the banner, asking how many FlashForge buyers had asked for, or wanted, an AI service advertisement to appear in their printer after the sale, and drawing a parallel to robot-vacuum companion apps that similarly serve ads to owners of paid hardware.<ref name="rossmann-ff">{{Cite web |url=https://www.youtube.com/watch?v=higSOW0-N24 |title=Flashforge closes ecosystem & puts AI ads into printing software 🤦 |last=Rossmann |first=Louis |date=2026-05-22 |website=YouTube |access-date=May 25, 2026}}</ref>
==Third-party slicer lockout==

After the firmware migration, mainline OrcaSlicer can no longer reach Adventurer 5M-series printers for remote print, monitoring, or camera viewing. OrcaSlicer issue #10260, opened July 28, 2025, documents OrcaSlicer 2.3.0 on Windows 10 receiving ''"ERR_CONNECTION_REFUSED"'' when attempting to monitor an Adventurer 5M.<ref name="orca-10260" /> OrcaSlicer issue #10112, opened July 10, 2025, reports that the Adventurer 5M device menu in mainline OrcaSlicer redirects to a 404 error, & includes user-supplied Python code demonstrating that direct socket communication on port 8899 still works against the printer, confirming the printer protocol remains operational while OrcaSlicer's plugin path is broken.<ref name="orca-10112" /> An earlier issue, #4834, opened April 1, 2024, recorded send-model failures from OrcaSlicer 2.0.0 to the Adventurer 5M & was closed as not planned.<ref name="orca-4834">{{Cite web |url=https://github.com/SoftFever/OrcaSlicer/issues/4834 |title=Error Send Model to FlashForge Adventurer 5M (Issue #4834) |date=2024-04-01 |website=GitHub: SoftFever/OrcaSlicer |access-date=May 22, 2026}}</ref>

FlashForge's quick-start documentation distinguishes two connection pathways. In WAN mode the slicer routes through FlashForge's cloud & requires the user to log in to a FlashForge account: ''"Before logging into the printer on the same network, you need to log in to your Flashforge account."'' In LAN-only mode the documentation instructs the user to ''"click [+] on the device page to find the corresponding printer"'' & enter the Printer-ID token displayed on the printer; no FlashForge account login is described as required.<ref name="ff-quickstart">{{Cite web |url=https://www.flashforge.com/a/docs/orca-flashforge/orca-flashforge-quick-start-guide |title=Orca-Flashforge Quick Start Guide |website=Flashforge |access-date=May 22, 2026}}</ref>

Tom's Hardware reviewer Denise Bertacchi, in a review published October 12, 2025, described the bundled Orca-Flashforge as the least stable build of OrcaSlicer she had used, crashing roughly every third print, & noted that mainline OrcaSlicer carries an AD5X profile but ''"the printer is still not passing along critical information, like wasted filament,"'' constraining users to the bundled fork.<ref name="tomshardware-ad5x">{{Cite web |url=https://www.tomshardware.com/3d-printing/flashforge-ad5x-review |title=Flashforge AD5X review: An affordable option for fast color 3D printing |last=Bertacchi |first=Denise |date=2025-10-12 |website=Tom's Hardware |access-date=May 22, 2026}}</ref> OrcaSlicer issue #11658, opened December 16, 2025 against OrcaSlicer 2.3.2 on Windows 11, separately documents that an Adventurer 5M owner can still send sliced jobs to the printer through mainline OrcaSlicer but cannot access the printer camera or pause prints from the device tab, with the slicer reporting that the printer ''"couldn't respond"'' and prompting the user to investigate firewall & proxy settings.<ref name="orca-11658">{{Cite web |url=https://github.com/OrcaSlicer/OrcaSlicer/issues/11658 |title=Orca slicer camara (Issue #11658) |date=2025-12-16 |website=GitHub: OrcaSlicer/OrcaSlicer |access-date=May 22, 2026}}</ref>

==GPL & AGPL concerns==

Orca-Flashforge (now Flash Studio Desktop) is a fork of SoftFever's OrcaSlicer, which is distributed under GPLv3 with AGPL-3.0 components. OrcaSlicer issue #5154, opened April 26, 2024, alleges that FlashForge violated the licenses by packaging Orca-Flashforge with a commercial end-user license agreement prohibiting commercial use, transfer, modification, & reverse engineering, & by failing to publish source code corresponding to the distributed binaries.<ref name="orca-5154">{{Cite web |url=https://github.com/SoftFever/OrcaSlicer/issues/5154 |title=Flashforge is violating OrcaSlicer's GPLv3 license (Issue #5154) |date=2024-04-26 |website=GitHub: SoftFever/OrcaSlicer |access-date=May 22, 2026}}</ref> The reporter quoted a FlashForge aftersales email stating ''"We have consulted our engineer, we don't have the Orca-Flashforge source code."'' FlashForge subsequently published source at github.com/FlashForge/Orca-Flashforge but the binary distribution continued to ship the restrictive commercial EULA, which the reporter characterised as still incompatible with GPLv3.<ref name="orca-5154" /><ref name="ff-eula">{{Cite web |url=https://github.com/FlashForge/Orca-Flashforge/blob/main/EULA/Orca-Flashforge-EULA-en.rtf |title=Orca-Flashforge EULA (English) |website=GitHub: FlashForge/Orca-Flashforge |access-date=May 22, 2026}}</ref>

A separate issue, Orca-Flashforge #26 opened November 15, 2025, documents that the compiled Orca-Flashforge binary opens outbound connections to roughly twenty hostnames, including api.auth.flashforge.com, api.fdmcloud.flashforge.com, link.netease.im, statistic.live.126.net, api.bambulab.com, ishare3d.com, & sz3dp.com, plus undocumented IPs over port 443 without TLS, & states that most of these hostnames do not appear in FlashForge's published source code.<ref name="orca-ff-26">{{Cite web |url=https://github.com/FlashForge/Orca-Flashforge/issues/26 |title=Provide actual codebase which exposes all connections (Issue #26) |date=2025-11-15 |website=GitHub: FlashForge/Orca-Flashforge |access-date=May 22, 2026}}</ref> Commenters identified an `nim.dll` file in the installer as the NetEase IM (instant messaging) library & questioned why a slicer needs a voice & video messaging API.<ref name="orca-ff-26" /> A January 28, 2025 issue, Orca-Flashforge #11, separately requested that FlashForge upload source code corresponding to the 1.3.0 & 1.3.1 binaries; FlashForge software engineer linnaiyuan replied that ''"The code for the 1.3 branch was pushed to the repository a few days ago"'' & later that ''"The code from the 1.3 branch has now been merged into the main branch,"'' & the issue was closed as completed.<ref name="orca-ff-11">{{Cite web |url=https://github.com/FlashForge/Orca-Flashforge/issues/11 |title=Orca Flashforge 1.3.0 and 1.3.1 update source (Issue #11) |date=2025-01-28 |website=GitHub: FlashForge/Orca-Flashforge |access-date=May 22, 2026}}</ref> These are open-source license concerns raised by users; no court has ruled on the GPL or AGPL compliance of the FlashForge fork.

==FlashForge response==

As of May 2026, no public FlashForge response has been located on the Meshy.ai banner placement, the loss of mainline OrcaSlicer remote-print & camera support on post-update firmware, or the GPL & AGPL compliance concerns raised in OrcaSlicer issue #5154 & Orca-Flashforge issue #26. Those issues were closed as ''"not planned"'' or auto-closed by a stale-bot after ninety days of inactivity without a FlashForge staff reply, in contrast to Orca-Flashforge issue #11, which a FlashForge engineer answered & closed once the requested 1.3-branch source was pushed.<ref name="orca-5154" /><ref name="orca-ff-26" /><ref name="orca-ff-11" /> The "Service Upgrade Notification" page frames the March 2025 changes as backend modernization & does not address third-party slicer compatibility.<ref name="ff-service-notice" />

==Consumer response==

Owners of the affected printers have pursued open-source firmware replacement as the documented workaround. The community Klipper Mod at github.com/xblax/flashforge_ad5m_klipper_mod installs Moonraker, custom Klipper, Mainsail, & Fluidd on the Adventurer 5M & 5M Pro, restoring open networking at the cost of voiding the manufacturer warranty.<ref name="klipper-xblax" /> A second mod, github.com/DrA1ex/ff5m ("Forge-X"), takes a similar firmware-replacement approach for the Adventurer 5M series; its README describes the goal as providing ''"a stable, feature-rich platform tailored to this printer's unique hardware and user needs."''<ref name="klipper-dra1ex">{{Cite web |url=https://github.com/DrA1ex/ff5m |title=Forge-X: Flashforge Adventurer 5M (Pro) Firmware mod |website=GitHub: DrA1ex/ff5m |access-date=May 22, 2026}}</ref> Another mod known as Z-mod enhances the existing FlashForge firmware and is available at github.com/ghzserg/zmod.

Early users of the 5M & 5M Pro documented many reverse-engineering efforts (including obtaining root on the included Linux OS running on the machine) at the github repo here: github.com/g992/flashforge-ad5m-5mpro-research

Rossmann framed the situation as a digital-freedom issue, arguing that if a manufacturer can remotely remove functionality after the sale, owners should be permitted to modify the device to restore it, & characterising Section 1201 of the DMCA as creating an asymmetry in which manufacturers may degrade products without consequence while owners who reverse-engineer those changes risk federal criminal penalties.<ref name="rossmann-ff" />
==See also==

*[[Bambu Lab Authorization Control System]]

==References==

{{reflist}}

[[Category:Incidents]]
[[Category:FlashForge]]
[[Category:3D printing]]
[[Category:GPL_Violations]]

Nanoleaf

2026-06-07T02:13:34Z

Wownyc: add category

{{StubNotice}}
{{CompanyCargo
|Description=Canadian electronics company specialized in LED lighting.
|Founded=2012
|Industry=Electronics
|Logo=Nanoleaf logo.png
|ParentCompany=
|Type=Private
|Website=https://nanoleaf.me/
}}
{{Wplink|Nanoleaf|'''Nanoleaf'''}} is a company that specializes in {{Wplink|Light-emitting diode|LED}} lighting. It was founded in 2012 and launched its first products with {{Wplink|Kickstarter}} funding.<ref>https://www.crowdfundinsider.com/2014/09/48447-nanoleaf-bloom-dimming-bulbs-over-160000-during-final-days-on-kickstarter/ ([http://web.archive.org/web/20250226155807/https://www.crowdfundinsider.com/2014/09/48447-nanoleaf-bloom-dimming-bulbs-over-160000-during-final-days-on-kickstarter/ Archived])</ref>

==Consumer impact summary==
===GPL violation===
Nanoleaf is using GPL-licensed software in its smart home products, which are based on [https://openwrt.org/ OpenWrt]. However, the company is not complying with the terms of the {{Wplink|GNU General Public License}} (GPL)<ref>https://www.gnu.org/licenses/gpl-3.0.html ([http://web.archive.org/web/20260128220745/http://www.gnu.org/licenses/gpl-3.0.html Archived])</ref> by failing to contribute back the modified source code or allowing users to run their own software on the hardware.<ref>https://forum.nanoleaf.me/forum/community-support/usage-of-openwrt-and-its-copyright-license ([http://web.archive.org/web/20250708203100/https://forum.nanoleaf.me/forum/community-support/usage-of-openwrt-and-its-copyright-license Archived])</ref><ref>https://www.reddit.com/r/Nanoleaf/comments/mbhudb/nanoleaf_aurora_run_linux_openwrt_and_nanoleaf_is/ ([http://web.archive.org/web/20250118190432/https://old.reddit.com/r/Nanoleaf/comments/mbhudb/nanoleaf_aurora_run_linux_openwrt_and_nanoleaf_is/ Archived])</ref><ref>https://forum.openwrt.org/t/nanoleaf-light-panels/81748 ([http://web.archive.org/web/20250708203102/https://forum.openwrt.org/t/nanoleaf-light-panels/81748 Archived])</ref>

===Aggressive data collection===
Nanoleaf devices collect information about the network environment they are connected to and transmit this data to the manufacturer. This data collection is not disclosed during the device setup process. Since the device maintains a constant network connection via {{Wplink|Wi-Fi}}, it operates continuously and sends metrics aggressively. This behavior was highlighted by members of the {{Wplink|Pi-Hole}} community, who observed that Nanoleaf devices were among the top consumers of {{Wplink|Domain Name System|DNS}} traffic on their networks.<ref>https://www.reddit.com/r/Nanoleaf/comments/m35bv5/collectornanoleafme_top_talker_on_network/ ([http://web.archive.org/web/20210322050252/https://old.reddit.com/r/Nanoleaf/comments/m35bv5/collectornanoleafme_top_talker_on_network/ Archived])</ref><ref>https://www.reddit.com/r/Nanoleaf/comments/m8g50y/my_4_aurora_are_creating_a_total_of_137000_dns/ ([http://web.archive.org/web/20210321224033/https://old.reddit.com/r/Nanoleaf/comments/m8g50y/my_4_aurora_are_creating_a_total_of_137000_dns/ Archived])</ref> For example, a single Nanoleaf bridge was found to generate 100,000 to 300,000 DNS requests per day, attempting to reach endpoints such as:

*collector.nanoleaf.com
*apollo.nanoleaf.com
*iaso.nanoleaf.com

This traffic persists even when users configure their light panels to operate in {{Wplink|Local area network|LAN}} mode. Additionally, completely disconnecting the light panels from the internet does not hinder their functionality, as control is managed locally via the HomeKit protocol, which does not rely on Nanoleaf's servers. This local control remains unaffected regardless of whether cloud integrations are set up or used. Notably, these DNS requests occur even when automatic firmware updates are disabled.

In response to a customer inquiry, Nanoleaf stated that the frequent communication (occurring every few seconds) is for "communicating with our cloud for various functionalities, including firmware upgrades and integration with third-party services such as {{Wplink|Google Assistant}} and {{Wplink|Amazon Alexa|Alexa}}.<ref>https://forum.nanoleaf.me/forum/community-support/homecalls ([http://web.archive.org/web/20250708203103/https://forum.nanoleaf.me/forum/community-support/homecalls Archived])</ref>

Following public scrutiny, Nanoleaf released a firmware update (version 5.2.1)<ref>https://helpdesk.nanoleaf.me/en-US/light-panels-firmware-release-notes-15633 ([http://web.archive.org/web/20250419175710/https://helpdesk.nanoleaf.me/en-US/light-panels-firmware-release-notes-15633 Archived])</ref> for the original Nanoleaf Aurora panels, which were discontinued two years prior. This update appears to disable the data collection behavior, however it remains unconfirmed whether newer, currently sold models have also had this telemetry removed.

==See also==
*[https://nanoleaf.me/en-EU/about-us/privacy-policy/#introduction Nanoleaf Privacy Policy]

==References==
{{Reflist}}

[[Category:Nanoleaf]]
[[Category:GPL_Violations]]

Entities refusing to distribute copyleft licensed software under license terms

2026-06-07T02:13:05Z

Wownyc: add category

{{Incomplete}}{{ToneWarning}}

Many open-source software licenses require you to license your modified copies under the same license, thus maintaining the freedom of the end-user and preventing use of the source code without any contribution.<ref>{{Cite web |title=What is Copyleft? |url=https://www.gnu.org/licenses/copyleft.en.html |url-status=live |archive-url=http://web.archive.org/web/20260207162655/https://www.gnu.org/licenses/copyleft.en.html |archive-date=7 Feb 2026}}</ref><ref>{{Cite web |date=2025-08-23 |title=What Is a Copyleft License and How Does It Work? |url=https://legalclarity.org/what-is-a-copyleft-license-and-how-does-it-work/ |url-status=live |archive-url=http://web.archive.org/web/20260210165636/https://legalclarity.org/what-is-a-copyleft-license-and-how-does-it-work/ |archive-date=10 Feb 2026}}</ref><ref>{{Cite web |last=Cotton |first=Ben |date=12 Aug 2016 |title=What is copyleft? |url=https://opensource.com/resources/what-is-copyleft |url-status=live |website=opensource.com |archive-url=http://web.archive.org/web/20260114215359/https://opensource.com/resources/what-is-copyleft |archive-date=14 Jan 2026}}</ref> However, this practice is rarely enforced and some companies actively refuse to distribute source code in flagrant violation of the law.<ref>{{Cite web |title=The Principles of Community-Oriented GPL Enforcement |url=https://sfconservancy.org/copyleft-compliance/principles.html |url-status=live |archive-url=http://web.archive.org/web/20260219070907/https://sfconservancy.org/copyleft-compliance/principles.html |archive-date=19 Feb 2026}}</ref>

A company may refuse to comply with a copyleft license to reduce user freedom regarding it's product, locking the end-user inside an ecosystem that only works with that company's product or products from it's partners.


==License examples==

===Permissive licenses===
One may confuse permissive licenses with copyleft licenses. The difference is that permissively licensed software does not require distribution of source code upon modification. If a company redistributes a modified version of open-source software that's under a permissive license, you may request for their source code.<ref name=":1">Gangadharan, G. R., et al. "Managing license compliance in free and open source software development." ''Information Systems Frontiers'' 14.2 (2012): 143-154.</ref>

===Copyleft licenses===
Copyleft licenses require the modified code to be distributed under the same license as the original. It does not matter if it is from the original vendor or from a distributor.<ref name=":1" /> Examples of such licenses include:

*GPL v2 and GPL v3
*MPL

==Enforcement and precedents==
The [https://sfconservancy.org/ Software Freedom Conservancy] is a nonprofit organization in order to combat this issue. However, in practice, they usually have long lead times and encourage the user to file a suit instead. Below are listed some precedent cases of enforcement of software licenses:

;SFC and Vizio's SmartCast TVs
:After the company Vizio failed to comply with the requirements of GPL v2 and LGPL in it's television software, SFC has filled a lawsuit against the company. Even though SFC is not the copyright holder of the used code, it's claiming to be third-party beneficiary of the said code, and if the judge decides that this is a valid claim, the case would set precedent for more rigid enforcement of open-source software licenses.<ref>{{Cite web |last=Drukarev |first=Andy |date=2025-06-29 |title=Analyzing 5 Major OSS License Compliance Lawsuits |url=https://fossa.com/blog/analyzing-5-major-oss-license-compliance-lawsuits/ |url-status=live |archive-url=https://web.archive.org/web/20250907181317/https://fossa.com/blog/analyzing-5-major-oss-license-compliance-lawsuits/ |archive-date=2025-09-07 |access-date=2025-09-07 |website=Fossa}}</ref><ref>{{Cite web |last=Lee |first=Victoria |last2=Stevenson |first2=Christopher |last3=Williams |first3=Glen |date=2024-01-16 |title=SFC v. Vizio survives motion for summary judgment on third-party beneficiary issue |url=https://www.dlapiper.com/en/insights/publications/2024/01/sfc-v-vizio-survives-motion-for-summary-judgment-on-third-party-beneficiary-issue |url-status=live |archive-url=https://web.archive.org/web/20250907181629/https://www.dlapiper.com/en/insights/publications/2024/01/sfc-v-vizio-survives-motion-for-summary-judgment-on-third-party-beneficiary-issue |archive-date=2025-09-07 |access-date=2025-09-07 |website=DLA Piper}}</ref>

==Examples==

===Linux kernel===
Linux is licensed under GPL-2.0-only.<ref name=":0">[https://github.com/torvalds/linux/blob/master/COPYING "Linux Copying Terms"] - github.com - accessed 2025-01-29 ([http://web.archive.org/web/20260212194557/https://github.com/torvalds/linux/blob/master/COPYING Archived])</ref><ref>{{Cite web |title=COPYING |url=https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/COPYING |url-status=live |archive-url=http://web.archive.org/web/20260122214149/https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/COPYING |archive-date=22 Jan 2026}}</ref> Refusing to provide the Linux kernel source code under it's original license is not allowed<ref>[https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html "GNU GPL Clause 3a"] - gnu.org - accessed 2025-01-29 ([http://web.archive.org/web/20260128144723/https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html Archived])</ref> and limits the end-user's usage of a device, for example, customers may not be able to build custom operating systems like LineageOS or postmarketOS for their phones as the result of this.

;Alarm.com
:''Alarm.com'' is a ''[[Software as a service]]'' company. They collaborate with multiple hardware vendors to get their security software running on their devices, which primarily run Android. In relation to ''Qolsys''<nowiki/>'s experience, they actively refused to provide the Linux kernel source code. They also do not have a webpage showcasing where to download source code.

;AVM
:''AVM'' is a German company that produces routers and smart home devices. While they disclosed their modified Linux Kernel source code, key build scripts were missing. It was only after they were sued by a software developer that they released them.<ref>{{Cite web |last=Faust |first=Mike |date=2025-01-11 |title=Auch Skripte für Kompilierung gehören zum Quellcode [Scripts for compilation are part of source code as well] |url=https://www.golem.de/news/klage-gegen-avm-auch-skripte-fuer-kompilierung-gehoeren-zum-quellcode-2501-192338.html |access-date=2025-09-03 |website=Golem |archive-url=https://web.archive.org/web/20260223041926/https://www.golem.de/sonstiges/zustimmung/auswahl.html?from=https%3A%2F%2Fwww.golem.de%2Fnews%2Fklage-gegen-avm-auch-skripte-fuer-kompilierung-gehoeren-zum-quellcode-2501-192338.html |archive-date=23 Feb 2026}}</ref>

;Cricket
:''Cricket'' is a mobile network carrier that also sells Android phones. As they are a distributor of Android phones, which run Linux, they are required by law to distribute the source code to customers who ask for it. However, in practice, customers are actively turned away by customer support. They also do not have a webpage showcasing where to download source code.

;Qolsys
:Most of ''Qolsys''<nowiki/>'s products run Android, however when asking customer support for the source code for the ''IQ Panel 4'', they actively refused to provide it. When pressed they will ignore you. They also do not have a webpage showcasing where to download source code.

;Xiaomi
:[[Xiaomi]]'s devices are running Android, which is built on top of the [https://kernel.org Linux kernel]. Xiaomi does release the kernel sources for many of their devices in their [https://github.com/MiCode/Xiaomi_Kernel_OpenSource GitHub repository], but not for all.
:The kernel sources for some Xiaomi devices are unavailable, they include:
:*Redmi Note 13 4G/NFC
:*Redmi 13C 4G
:*Poco M5
:This, along with [[Xiaomi Phone unlock requirements and procedure]] prevents custom ROMs from being made for these devices.

==References==
<references />
[[Category:Xiaomi]]
[[Category:GPL_Violations]]

Vizio sued over unfairly appropriated software for their SmartCast system

2026-06-07T02:12:35Z

Wownyc: add category

{{IncidentCargo
|Company=Vizio
|StartDate=2021
|EndDate=
|Status=
|ProductLine=
|Product=SmartCast
|ArticleType=
|Type=Source Code, Right to Repair
|Description=
}}
[[Vizio]] was sued by the [https://sfconservancy.org/ SFC] in October 2021 over the alleged unfairly appropriated software in their SmartCast system.<ref name=":0">{{Cite web |title=Vizio Lawsuit Q & A |url=https://sfconservancy.org/press/qanda.html |archive-url=https://web.archive.org/web/20211020053409/https://sfconservancy.org/press/qanda.html |archive-date=20 Oct 2021 |publisher=Software Freedom Conservancy |language=en |format=article}}</ref> The SFC argues that Vizio’s alleged failure to adhere to copyleft-licensing requirements denies rights that are guaranteed to downstream users.<ref name=":1">{{Cite web |author=Steven Vaughan-Nichols |date=19 Oct 2021 |title=Software Freedom Conservancy sues Vizio for GPL violations |url=https://www.zdnet.com/article/software-freedom-conservancy-sues-vizio-for-gpl-violations/ |archive-url=https://web.archive.org/web/20211019203625/https://www.zdnet.com/article/software-freedom-conservancy-sues-vizio-for-gpl-violations/ |archive-date=19 Oct 2021 |publisher=ZDNET |language=en |format=article}}</ref><ref>{{Cite web |author=FOSSA Editorial Team |date=13 May 2022 |title=The Massive Implications of Software Freedom Conservancy vs. Vizio |url=https://fossa.com/blog/massive-implications-software-freedom-conservancy-vs-vizio/ |archive-url=http://web.archive.org/web/20250914204857/https://fossa.com/blog/massive-implications-software-freedom-conservancy-vs-vizio/ |archive-date=14 Sep 2025|publisher=FOSSA |language=en |format=article}}</ref>

==Background==
The company Vizio was first informed that it had violated the GPLv2 license for not releasing SmartCast OS's source code by the SFC in August 2018.<ref name=":1" /> SFC gave a short summary for consumers to explain why they decided to pursue a lawsuit:<ref name=":0" /><blockquote>Right-to-repair software is essential for everyone, even if you don't know how to make the repairs yourself. Once upon a time, we had lots of local vendors that could repair and fix TVs when they broke. That’s because TVs were once analog hardware devices that could be taken apart and understood merely by inspection from someone with the sufficient knowledge. TVs today are simply a little computer attached to a large display. As such, the most important part that needs repairs is usually when the software malfunctions, has bugs, or otherwise needs upgrades and changes. The GPL was specifically designed to assure such fixes could be done, and that consumers (or agents those consumers hire on the open market) can make such repairs and changes.

Time and time again, companies stop supporting the software build for the device long before the computer inside the device fails. In other words, these devices are built for planned premature obsolescence.

By refusing to comply with the pro-consumer terms of the GPL, Vizio has the power to disable your TV at any time it wants, over your internet connection, without your knowledge or consent. If Vizio complied with the GPL, all would not be lost in this scenario: volunteers and third-party entities could take GPL’d software as a basis for a replacement for SmartCast. Without these rights, consumers are essentially forced to purchase new devices when they could be repaired.</blockquote>

==Lawsuits==
There was initial contact between the two parties from 2018 up to 2020, which lead to a lawsuit being filed by the SFC in 2021.<ref name=":0" /> Vizio wanted the case to go to the federal court to avoid the contract issue and defend its corner using just federal copyright law.<ref name=":2">{{Cite web |author=Thomas Claburn |date=16 May 2022 |title=GPL legal battle: Vizio told by judge it will have to answer breach-of-contract claims |url=https://www.theregister.com/2022/05/16/vizio_gpl_contract/ |archive-url=https://web.archive.org/web/20220516233852/https://www.theregister.com/2022/05/16/vizio_gpl_contract/ |archive-date=16 May 2022 |publisher=The Register |language=en |format=article}}</ref> In 2022 however, a federal court judge ruled that the GPL functions as both a copyright license and a contract, and remanded the case back to state court.<ref name=":2" /> The judge decided the federal Copyright Act did not preempt the SFC's breach-of-contract allegations, because a contractual obligation for the rights stated in the license are beyond what's required by copyright law.<ref name=":2" />

In 2023, this was confirmed in state court and Vizio's motion for summary judgement was denied.<ref>{{Cite web |author1=Victoria Lee |author2=Christopher Stevenson |author3=Glen Williams |date=16 Jan 2024 |title=SFC v. Vizio survives motion for summary judgment on third-party beneficiary issue |url=https://www.dlapiper.com/en/insights/publications/2024/01/sfc-v-vizio-survives-motion-for-summary-judgment-on-third-party-beneficiary-issue |archive-url=https://web.archive.org/web/20240407160619/https://www.dlapiper.com/en/insights/publications/2024/01/sfc-v-vizio-survives-motion-for-summary-judgment-on-third-party-beneficiary-issue |archive-date=7 Apr 2024 |publisher=DLA Piper |language=en |format=article}}</ref> The court decided that users need to be able to enforce these rights themselves. This is because the original creators of the software wouldn't have any financial reason to enforce these rights. If only creators could enforce the rights, they would have to pay all the legal costs without getting any benefit. This would mean the rights would rarely be enforced, which would defeat the purpose of the GPL license.

The case's expected trial date is in September 2025, as it is still an ongoing case.<ref>{{Cite web |title=Current Status of Vizio Case |url=https://sfconservancy.org/copyleft-compliance/vizio.html |archive-url=http://web.archive.org/web/20260127154926/https://sfconservancy.org/copyleft-compliance/vizio.html |archive-date=27 Jan 2026|publisher=Software Freedom Conservancy |language=en |format=article}}</ref>

==References==
{{reflist}}
[[Category:Lawsuits]]
[[Category:Software licensing]]
[[Category:Right to repair]]
[[Category:Vizio]]
[[Category:GPL_Violations]]

Category:GPL violations

2026-06-07T02:11:51Z

Wownyc: move to software licensing category

[[Category:Software licensing]]

Cisco Meraki

2026-06-07T02:09:41Z

Wownyc: add to gpl violations category

{{StubNotice}}
{{Incomplete}}

{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by [[Cisco Systems, Inc.|Cisco]] in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==

Since ~2018, hardware has been locked down with SecureBoot. <ref>https://forum.openwrt.org/t/cisco-meraki-mx68w/134895</ref><ref>https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881</ref> Hardware before 2018, or with SecureBoot exploits may be reflashable to OpenWrt.<ref name="watchmysys" /><ref>https://openwrt.org/toh/meraki/start</ref>

The company was previously friendly to open-source.<ref name="watchmysys">https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/</ref><ref name="only_took_four_months">https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4</ref><ref>https://forum.archive.openwrt.org/viewtopic.php?id=63838</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5</ref><ref name="mr46">https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64</ref> and/or releases source code that doesn't build.<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60</ref><ref name="mr46" />

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>https://github.com/riptidewave93/LEDE-MR33/issues/13</ref>

===User freedom===

===User privacy===

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx60
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx64
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/support-for-meraki-mx85/207538
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr52
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr18
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |https://openwrt.org/toh/meraki/mr34
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr42
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 https://github.com/halmartin/meraki-builder/issues/11
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |https://github.com/halmartin/meraki-builder/issues/23
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other Products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{reflist}}

[[Category:{{PAGENAME}}]]
[[Category:GPL_Violations]]

Meraki MS390

2026-06-07T02:09:17Z

Wownyc: link

{{Stub}}
{{ProductCargo
|Company=Cisco Systems, Inc., Meraki
|ProductLine=MS
|ReleaseYear=2019
|InProduction=No
|ArticleType=Product
|Category=Subscription, Computers
|Logo=Ms390.png
|Website=https://documentation.meraki.com/Switching/MS_-_Switches/Product_Information/Overviews_and_Datasheets/MS390_Datasheet
|Description=Top of the line Enterprise grade cloud managed layer 3 ethernet network switch.
}}

The '''Meraki MS390''' is a high-end series of Layer 3 network switches manufactured by [[Cisco Meraki]] from 2019-2025. Unlike every other switch sold under the Meraki branding at the time, it was based on Catalyst hardware and software. There are many variants in the MS390 series, but all share the same platform and firmware. These switches share identical hardware and software based off of the Cisco Catalyst 9300 series of switches. The 9300 series was originally designed to be configured locally with a console port. The MS390 has a functional console port and runs a very similar firmware, but [[Cisco]] has locked all access to it via software blocks.

==Consumer impact summary==
{{Ph-C-CIS}}
The following are some concerns regarding end-user rights for this series of switches:

*Cloud licensing is required to use product.
*Product will be non-functional after EOL date of Mar 28, 2032.<ref>{{Cite web |author= |title=Meraki End-of-Life (EOL) Products and Dates |url=https://documentation.meraki.com/Platform_Management/Product_Information/End-of-Life_Notices/Meraki_End-of-Life_(EOL)_Products_and_Dates |website=[[Cisco Meraki]] |date= |access-date=11 Apr 2026 |url-status=live |archive-url=https://web.archive.org/web/20260212035817/https://documentation.meraki.com/Platform_Management/Product_Information/End-of-Life_Notices/Meraki_End-of-Life_%28EOL%29_Products_and_Dates |archive-date=12 Feb 2026}}</ref>
*There is no official way to configure device locally using the console port or otherwise.

==See also==
{{Ph-C-SA}}

==References==
{{Reflist}}

[[Category:{{PAGENAME}}]]
[[Category:Discontinued products]]

Category:GPL violations

2026-06-07T02:08:34Z

Wownyc: Created page with "Category:Wiki_root"

[[Category:Wiki_root]]

Creality K2 series GPLv3 violation

2026-06-07T02:08:00Z

Wownyc: create gpl violation category

{{IncidentCargo
|Company=Creality
|StartDate=2025-02-03
|Status=Active
|ProductLine=K2 Series 3D Printers
|Product=Creality K2 SE, K2, K2 Pro, K2 Plus
|ArticleType=Product
|Type=Repairability,Software Licensing
|Description=Creality K2 firmware ships Cython-compiled binary blobs inside GPLv3 Klipper without source; developers allege a GPLv3 violation
}}

The Creality K2 series 3D printer firmware (covering the K2 SE, K2, K2 Pro, & K2 Plus) ships proprietary modules compiled with Cython into the GPLv3-licensed Klipper host environment without releasing the corresponding source code.<ref name="creality_forum_tracker" /><ref name="cfs_github" /> Klipper's community developers & the independent reverse-engineering project fake-name/cfs-reverse-engineering have documented these closed binaries as a violation of the GNU General Public License v3 (GPLv3), the license under which Klipper is distributed.<ref name="creality_forum_tracker" /><ref name="cfs_github" /> [[Creality]] opened a public GitHub repository for the K2 line in December 2025 & markets it as open source, but the published code lacks the source for several hardware communication modules.<ref name="creality_forum_launch" /> A correspondence log uploaded to the Internet Archive in May 2026 records Creality support telling a requester it was ''unable to directly provide the corresponding source code,'' & shows the requester copying the [[Software Freedom Conservancy]] (SFC) & the Free Software Foundation (FSF) on the demand.<ref name="email_demand" />

==Background==
The K2 series firmware is built on Klipper, the open-source 3D-printer host software that its creator Kevin O'Connor distributes under the GPLv3.<ref name="klipper_discourse_violation" /> In December 2025, Creality opened a public GitHub repository for the K2 series & promoted the line as open source.<ref name="creality_forum_launch" /> Community developers found that the published code was outdated, out of sync with shipping printer configurations, & missing the source for several hardware communication modules.<ref name="creality_forum_launch" /><ref name="creality_forum_tracker" /> The dispute predates that repository: a Creality-forum thread asking where the required K2 Klipper sources were had been open since February 2025.<ref name="creality_forum_tracker" />

The missing modules ship as Cython-compiled shared objects. The reverse-engineering project fake-name/cfs-reverse-engineering describes these files as compiled with Cython ''to make them opaque.''<ref name="cfs_github" /> Because the wrappers sit inside Klipper's own process directory, the GPLv3-licensed Klipper host loads & executes the closed binaries at runtime.<ref name="creality_forum_tracker" /><ref name="cfs_github" />

The missing source affects the firmware images shipped across the K2 line:
*'''K2 SE:''' V2.3.6.49 (<code>CR4CU220812S11_ota_img_V2.3.6.49.img</code>) <ref name="email_demand" />
*'''K2:''' V1.1.5.5 (<code>CR0CN200400C10_R_202605061516_ota_img_V1.1.5.5.img</code>) <ref name="email_demand" />
*'''K2 Pro:''' V1.1.5.5 (<code>CR0CN200400C10_R_202605061516_ota_img_V1.1.5.5.img</code>) <ref name="email_demand" />
*'''K2 Plus:''' V1.1.5.5 (<code>CR0CN240110C10_R_202605081127_ota_img_V1.1.5.5.img</code>) <ref name="email_demand" />

==Incident==
Creality distributes Cython-compiled shared objects (<code>.so</code>) inside Klipper's process directory at <code>/usr/share/klipper/klippy/extras/</code> without the matching source.<ref name="creality_forum_tracker" /><ref name="extracted_fw" /> Extracted K2 Plus firmware lists six such wrappers in that directory:
*<code>serial_485_wrapper.cpython-39.so</code>, which the cfs project ties to the RS-485 serial link between the mainboard and the CFS feeder bus <ref name="creality_forum_tracker" /><ref name="cfs_github" />
*<code>box_wrapper.cpython-39.so</code> <ref name="creality_forum_tracker" />
*<code>filament_rack_wrapper.cpython-39.so</code> <ref name="creality_forum_tracker" />
*<code>motor_control_wrapper.cpython-39.so</code> <ref name="creality_forum_tracker" />
*<code>prtouch_v2_wrapper.cpython-39.so</code> <ref name="creality_forum_tracker" />
*<code>prtouch_v3_wrapper.cpython-39.so</code> <ref name="creality_forum_tracker" />
A Klipper community thread on the K2 Plus documents that these compiled modules implement the printer's automatic filament-changing feature & ship only as shared-object files, & a moderator there describes Creality as in violation of the GPLv3.<ref name="klipper_discourse_k2" />

According to a correspondence log uploaded to the Internet Archive in May 2026, a requester pressed Creality for the complete GPLv3 source code, & Creality support acknowledged the request on May 15, 2026.<ref name="email_demand" /> The log's outgoing letters, signed by a sender identifying himself as Alex Mercer, were copied to the [[Software Freedom Conservancy]] (compliance@sfconservancy.org) & the Free Software Foundation (license-violation@gnu.org) on May 27 & May 29, 2026, & state that the violation is ''logged with the Software Freedom Conservancy and the Free Software Foundation.''<ref name="email_demand" /> The log records a single recurring demand, that Creality either release the source or stop shipping the firmware. The May 29, 2026 letter reads:
<blockquote>''I reiterate my demand: immediately provide the complete corresponding source code or halt all distribution of the K2 series firmware until compliance is achieved.''</blockquote><ref name="email_demand" />
Creality continues to distribute the same firmware images while the source remains unreleased.<ref name="creality_forum_tracker" />

===Creality's response===
Through May 2026, community members documented a repeating set of stalling & denial templates from Creality's front-line support on GPL inquiries.<ref name="creality_forum_tracker" />

In the correspondence log, a May 15, 2026 reply from Creality Customer Service reads:
<blockquote>''We have officially forwarded your application for the complete GPLv3 source code for all firmware versions of the K2 series to our R&D team for processing. ... Please stay tuned for further announcements on our official website.''</blockquote><ref name="email_demand" />

A May 24, 2026 reply in the same log, attributed to Creality Service, reads:
<blockquote>''Due to the involvement of custom firmware modules, underlying dependencies, and the need to clarify copyrights from multiple parties, the compilation of relevant materials requires a considerable period of time. Currently, we are unable to directly provide the corresponding source code or updated repository links.''</blockquote><ref name="email_demand" />

A May 29, 2026 follow-up in the log states:
<blockquote>''cleaning up a fully compliant source code package without affecting commercial proprietary code does require an internal process that, for now, does not have a publicly available timeline.''</blockquote><ref name="email_demand" />

The log records no substantive reply after May 29, 2026; per the log, Creality forwarded the case to its internal legal department & R&D manager without giving a compliance timeline.<ref name="email_demand" />

==Consumer response & hardware bypass==
The K2 firmware drew criticism on the Creality forums, where the cfs project author argued that withholding the source for the parts that matter moved Creality from incompetent to ''actively malicious'': promoting a printer as open source while keeping its core features behind closed binaries.<ref name="creality_forum_tracker" />

The closed binaries created practical problems for owners: blocked hardware repair, no support for third-party toolheads, & restricted access to the printer's underlying Linux system.<ref name="creality_forum_tracker" />

Creality had faced the same complaint over the earlier K1 series. Issue #9 on its K1_Series_Klipper GitHub repository flagged binary-only extensions as a GPLv3 violation & demanded the corresponding source; the issue remained open as of March 2025.<ref name="k1_github_issue" /> On the later K1C, Creality removed root access; owners on the Creality forum note that the printer's own documentation describes the removal as intentional.<ref name="creality_k1c_forum" />

Independent developers started the fake-name/cfs-reverse-engineering project to map the Creality Filament System (CFS) feeder bus.<ref name="cfs_github" /> The project documents that the CFS uses a GigaDevice GD32F303VET6 microcontroller, which its firmware notes describe as binary-compatible with an ''STM32F106VET6''.<ref name="cfs_github" /> By building a hardware interposer board to reroute the isolated RS-485 lines to an unused MCU header, the developers converted the CFS link into a standard CAN bus running candleLight_fw & upstream Klipper, bypassing Creality's closed serial protocol.<ref name="cfs_github" />

Kevin O'Connor, the creator of Klipper, restated the license terms on the Klipper Discourse forum:
<blockquote>''Klipper is licensed under the GNU GPLv3. Any redistribution of that code is required to follow the license. I have not dual-licensed the code nor provided any exceptions.''</blockquote><ref name="klipper_discourse_violation" />

==Prior violations & the Bambu Lab AGPLv3 case==
Creality already appears on TH3D Studio LLC's 3D Printer GPL Violation List for withholding source code on its Marlin-based printers & the Klipper-based Sonic Pad.<ref name="th3d_list" /><ref name="klipper_discourse_violation" />

Creality's open-source disputes go back to 2018. After it shipped its CR-10 line with Marlin, a GPLv3-licensed firmware, without releasing complete corresponding source, US distributor Printed Solid stopped selling Creality printers over the non-compliance.<ref name="hackaday_marlin" /> Community pressure followed, & technology figure Naomi Wu was credited, alongside that pressure, with getting Creality to release the Marlin source for the CR-10S, including its filament-sensor & power-loss-recovery code, in April 2018.<ref name="3dprintingnerd_nw" />

On May 18, 2026, the Software Freedom Conservancy published a response to violations of the GNU Affero General Public License v3 (AGPLv3) by [[Bambu Lab]] over its proprietary networking library <code>libbambu_networking.so</code>.<ref name="sfc_bambu" /><ref name="toms_hardware_bambu" /> After Bambu issued a cease-and-desist to Pawel Jarczak, the developer of an OrcaSlicer fork, the SFC announced Project baltobu (''Bringing Affero Licensed Things (On)to Bambu Users'') to reverse-engineer the closed library & host an independent slicer fork.<ref name="sfc_bambu" />

==References==
<references>
<ref name="creality_forum_launch">[https://forum.creality.com/t/creality-open-source-3d-printer-firmware-is-here/47218 "Creality Open-Source 3D Printer Firmware is Here!"], Official Creality Forum.</ref>
<ref name="creality_forum_tracker">[https://forum.creality.com/t/where-are-the-required-to-be-released-sources-for-crealitys-modifications-to-klipper-the-k2/30019 "Where are the (required to be released) sources for Creality's modifications to Klipper the K2"], Creality Forum.</ref>
<ref name="email_demand">[https://archive.org/details/creality-k-2-gplv-3-compliance-demand-may-2026 "Creality K2 GPLv3 Compliance Demand Correspondence Logs (May 2026)"], correspondence log uploaded to the Internet Archive.</ref>
<ref name="extracted_fw">[https://github.com/Guilouz/Creality-K2Plus-Extracted-Firmwares/tree/main/Firmware/usr/share/klipper/klippy/extras Guilouz/Creality-K2Plus-Extracted-Firmwares, /Firmware/usr/share/klipper/klippy/extras directory], GitHub Repository.</ref>
<ref name="k1_github_issue">[https://github.com/CrealityOfficial/K1_Series_Klipper/issues/9 "This repository contains binary-only extensions, violating the Klipper GPLv3 license"], K1 Series GitHub Issue #9.</ref>
<ref name="klipper_discourse_k2">[https://klipper.discourse.group/t/creality-k2-plus-and-gpl-violations/22402 "Creality K2 Plus and GPL violations"], Klipper Discourse Group.</ref>
<ref name="creality_k1c_forum">[https://forum.creality.com/t/k1c-2025-orcaslicer-workarounds-for-missing-web-interface/47164 "K1C 2025 + OrcaSlicer: Workarounds for Missing Web Interface"], Creality Community Forum.</ref>
<ref name="hackaday_marlin">[https://hackaday.com/2018/08/27/gpl-violations-cost-creality-a-us-distributor/ "GPL Violations Cost Creality A US Distributor"], Hackaday, Tom Nardi, August 27, 2018.</ref>
<ref name="3dprintingnerd_nw">[https://web.archive.org/web/20210509124858/https://the3dprintingnerd.com/creality-gpl-update-naomi-wu-released-cr-10s-marlin-source-code/ "Creality GPL Update: Naomi Wu Released CR-10S Marlin Source Code"], 3D Printing Nerd, April 9, 2018 (archived).</ref>
<ref name="klipper_discourse_violation">[https://klipper.discourse.group/t/creality-violating-klipper-license/8990 "Creality Violating Klipper License"], Klipper Discourse Group.</ref>
<ref name="cfs_github">[https://github.com/fake-name/cfs-reverse-engineering fake-name/cfs-reverse-engineering], GitHub Repository.</ref>
<ref name="th3d_list">[https://web.archive.org/web/20231109014621/https://www.th3dstudio.com/3d-printer-gpl-violation-list/ "3D Printer GPL Violation List"], TH3D Studio LLC (archived November 9, 2023).</ref>
<ref name="sfc_bambu">[https://sfconservancy.org/news/2026/may/18/bambu-studio-3d-printer-agpl-violation-response/ "Comprehensive Response to Bambu's AGPLv3 Violations"], Software Freedom Conservancy.</ref>
<ref name="toms_hardware_bambu">[https://www.tomshardware.com/3d-printing/open-source-non-profit-claims-bambu-lab-violated-license-move-follows-cease-and-desist-demand-on-orcaslicer-fork-that-restored-cloud-printing-features-without-using-bambu-connect "Open-source non-profit claims Bambu Lab violated license"], Tom's Hardware.</ref>
</references>

[[Category:GPL Violations]]

Cisco Meraki

2026-06-07T01:51:18Z

Wownyc: /* Consumer impact summary */

List of products bricked by discontinuation

2026-06-07T01:49:48Z

Wownyc: /* List of products */

{{StubNotice}}

A list of products [[Discontinuation bricking|bricked by discontinuation]].

==List of products==
{| class="wikitable"
|+
!Product or line
!Company
!Release date
!End date
!Reasoning
|-
|[[Bosch Spexor]]
|[[Bosch]]
|2019
|2023 (sales)
2025 (support)
|Low demand in combination with high operational and app development costs
|-
|[[Discontinuation of Ikawa Home Roasters|Ikawa Home Roasters]]
|[[Ikawa Coffee]]
|2017
|2026
|"After careful consideration, we have made the decision to discontinue our '''IKAWA Home''' range of products. The '''IKAWA Home''' website will officially close on '''September 30, 2025'''."
|-
|[[Sandisk Wireless Flash Drives]]
|Sandisk
|2015
|18 Mar 2021
|"...as an effort to retire legacy apps and migrate users to newer products, services, and apps."<ref>{{Cite web |date=2022-09-13 |title=Wireless Flash Drive End of Support |url=https://support-en.sandisk.com/app/answers/detailweb/a_id/48977 |archive-url=https://web.archive.org/web/20250612204620/https://support-en.sandisk.com/app/answers/detailweb/a_id/48977 |archive-date=2025-06-12 |access-date=2025-10-25 |website=Sandisk}}</ref>
|-
|[[Data_lock-in#Telekom_Entertain_media_receiver_recordings|Telekom Entertain media receivers]]
|German Telekom
|2011
|2019
|The operating system required access to Telekom servers to be able to boot. When the service was discontinued, its users could no longer access their locally stored recordings. The recordings were stored in a proprietary format and there was no way to copy or move them to external media.
|-
|[[Cisco Meraki]]
|[[Cisco Meraki]]
|
|
|"for a number of reasons, including product line enhancements, market demands, technology innovation, or the products simply mature over time and are replaced by functionally richer products."<ref>{{Cite web |author= |title=Meraki End-of-Life (EOL) Products and Dates |url=https://meraki.cisco.com/meraki-support/policies/#product-end-of-life-eol-policy |website=[[Cisco Meraki]] |date= |access-date=5 Jun 2026 |url-status=live |archive-url=https://web.archive.org/web/20260605143637/https://meraki.cisco.com/meraki-support/policies/#product-end-of-life-eol-policy |archive-date=5 Jun 2026 }}</ref>
|}

==References==
{{reflist}}
[[Category:Lists]]
[[Category:Discontinuation bricking]]

List of products bricked by discontinuation

2026-06-07T01:48:16Z

Wownyc: /* List of products */

{{StubNotice}}

A list of products [[Discontinuation bricking|bricked by discontinuation]].

==List of products==
{| class="wikitable"
|+
!Product or line
!Company
!Release date
!End date
!Reasoning
|-
|[[Bosch Spexor]]
|[[Bosch]]
|2019
|2023 (sales)
2025 (support)
|Low demand in combination with high operational and app development costs
|-
|[[Discontinuation of Ikawa Home Roasters|Ikawa Home Roasters]]
|[[Ikawa Coffee]]
|2017
|2026
|"After careful consideration, we have made the decision to discontinue our '''IKAWA Home''' range of products. The '''IKAWA Home''' website will officially close on '''September 30, 2025'''."
|-
|[[Sandisk Wireless Flash Drives]]
|Sandisk
|2015
|18 Mar 2021
|"...as an effort to retire legacy apps and migrate users to newer products, services, and apps."<ref>{{Cite web |date=2022-09-13 |title=Wireless Flash Drive End of Support |url=https://support-en.sandisk.com/app/answers/detailweb/a_id/48977 |archive-url=https://web.archive.org/web/20250612204620/https://support-en.sandisk.com/app/answers/detailweb/a_id/48977 |archive-date=2025-06-12 |access-date=2025-10-25 |website=Sandisk}}</ref>
|-
|[[Data_lock-in#Telekom_Entertain_media_receiver_recordings|Telekom Entertain media receivers]]
|German Telekom
|2011
|2019
|The operating system required access to Telekom servers to be able to boot. When the service was discontinued, its users could no longer access their locally stored recordings. The recordings were stored in a proprietary format and there was no way to copy or move them to external media.
|-
|[[Cisco Meraki]]
|[[Cisco Meraki]]
|
|
|"The device-specific licenses corresponding to discontinued hardware products will be available for purchase after the EOS Date unless the license(s) is/are listed in the “End-of-Life Products” list provided below."<ref>{{Cite web |author= |title=Meraki End-of-Life (EOL) Products and Dates |url=https://meraki.cisco.com/meraki-support/policies/#product-end-of-life-eol-policy |website=[[Cisco Meraki]] |date= |access-date=5 Jun 2026 |url-status=live |archive-url=https://web.archive.org/web/20260605143637/https://meraki.cisco.com/meraki-support/policies/#product-end-of-life-eol-policy |archive-date=5 Jun 2026 }}</ref>
|}

==References==
{{reflist}}
[[Category:Lists]]
[[Category:Discontinuation bricking]]

List of products bricked by discontinuation

2026-06-07T01:47:22Z

Wownyc: add cisco meraki

{{StubNotice}}

A list of products [[Discontinuation bricking|bricked by discontinuation]].

==List of products==
{| class="wikitable"
|+
!Product or line
!Company
!Release date
!End date
!Reasoning
|-
|[[Bosch Spexor]]
|[[Bosch]]
|2019
|2023 (sales)
2025 (support)
|Low demand in combination with high operational and app development costs
|-
|[[Discontinuation of Ikawa Home Roasters|Ikawa Home Roasters]]
|[[Ikawa Coffee]]
|2017
|2026
|"After careful consideration, we have made the decision to discontinue our '''IKAWA Home''' range of products. The '''IKAWA Home''' website will officially close on '''September 30, 2025'''."
|-
|[[Sandisk Wireless Flash Drives]]
|Sandisk
|2015
|18 Mar 2021
|"...as an effort to retire legacy apps and migrate users to newer products, services, and apps."<ref>{{Cite web |date=2022-09-13 |title=Wireless Flash Drive End of Support |url=https://support-en.sandisk.com/app/answers/detailweb/a_id/48977 |archive-url=https://web.archive.org/web/20250612204620/https://support-en.sandisk.com/app/answers/detailweb/a_id/48977 |archive-date=2025-06-12 |access-date=2025-10-25 |website=Sandisk}}</ref>
|-
|[[Data_lock-in#Telekom_Entertain_media_receiver_recordings|Telekom Entertain media receivers]]
|German Telekom
|2011
|2019
|The operating system required access to Telekom servers to be able to boot. When the service was discontinued, its users could no longer access their locally stored recordings. The recordings were stored in a proprietary format and there was no way to copy or move them to external media.
|-
|[[Cisco Meraki]]
|[[Cisco Meraki]]
|
|
|"The device-specific licenses corresponding to discontinued hardware products will be available for purchase after the EOS Date unless the license(s) is/are listed in the “End-of-Life Products” list provided below."<ref>{{Cite web |author= |title=Meraki End-of-Life (EOL) Products and Dates |url=https://meraki.cisco.com/meraki-support/policies/#product-end-of-life-eol-policy |website=[[Cisco Meraki]] |date= |access-date=05 Jun 2026 |url-status=live |archive-url=https://web.archive.org/web/20260605143637/https://meraki.cisco.com/meraki-support/policies/#product-end-of-life-eol-policy |archive-date=05 Jun 2026 }}</ref>
|}

==References==
{{reflist}}
[[Category:Lists]]
[[Category:Discontinuation bricking]]

3D Printing restrictions and bans

2026-06-07T01:40:27Z

Wownyc: again with the safety

'''3D Printing restrictions and bans''' are legal, technical, and policy limits that governments, platforms, and manufacturers place on how consumer 3D printers may be bought, modified, or used. The most far-reaching example is a New York law, enacted in May 2026, that will require every 3D printer sold in the state to carry ''"blocking technology"'' which checks each print file against a firearms blueprint detection algorithm before the machine will run the job.<ref name="bill" /> The Governor's office and the gun-control group Everytown for Gun Safety described the measure as first-in-the-nation.<ref name="gov" /><ref name="everytown" /> The printer-sales requirement is not yet in force. It takes effect one year after state rules are written, those rules cannot begin until an expert working group reports, and a feasibility clause lets that group shelve the mandate if it finds the scanning technology does not work.<ref name="bill" /><ref name="bill-pdf" />

==How restrictions are imposed==

Restrictions on consumer 3D printers take several forms, often combined:

*'''Legislation.''' State laws and bills can restrict how printers are sold or used. New York's budget law requires printers sold in the state to carry firearm-blocking technology, and Washington and California have advanced similar bills.<ref name="bill" /><ref name="toms-wa" /><ref name="toms-ca" />
*'''Firmware and software locks.''' Manufacturers can gate printer functionality behind signed firmware, mandatory cloud connections, or authorization checks, as documented with [[Bambu Lab Authorization Control System|Bambu Lab's Authorization Control System]].
*'''Platform and service dependency.''' Printers can depend on a proprietary slicer, a cloud account, or an online authorization server to remain fully functional.
*'''Content and model filtering.''' Software can scan, flag, or refuse particular model files or print jobs. New York's blocking-technology mandate would require this kind of per-file screening by law.<ref name="bill" />
*'''Support withdrawal.''' A manufacturer can declare a device unsupported and disable features through software updates or by shutting down the servers the device depends on, a [[Planned obsolescence|planned-obsolescence]] risk for any cloud-tied printer.

==Firearm-blocking printer mandates==

In 2026 several states moved to regulate 3D-printed firearms through the printer itself rather than only the design file or the finished weapon. New York enacted the first such law; Washington and California advanced bills along the same lines, and Colorado and the Manhattan District Attorney pursued narrower measures.<ref name="bill" /><ref name="toms-wa" /><ref name="toms-ca" /><ref name="co-bill" /><ref name="manhattanda" />

===New York blocking-technology mandate===

{{Main|New York 3D printer blocking technology mandate}}

New York's mandate was enacted as Part C of the FY2026-2027 budget, bills S.9005-C and A.10005-C, and signed by Governor Kathy Hochul on May 27, 2026.<ref name="gov" /><ref name="bill" /> The operative command is in the new General Business Law section 396-eeee (1):

<blockquote>''No person, firm, partnership, association, or corporation shall sell or deliver any three-dimensional printer in the state of New York unless such printer is equipped with blocking technology.''</blockquote><ref name="bill-pdf" />

Executive Law section 837-aa (1)(b) defines that blocking technology as integrated measures that keep a printer from running any job unless the file has been evaluated by a firearms blueprint detection algorithm and found not to produce a firearm or illegal firearm parts.<ref name="bill" /> The algorithm, defined in section 837-aa (1)(c), reads printing files ''"whether in the form of stereolithography (STL) files or other computer aided design files or geometric code."''<ref name="bill" /> To supply data for those checks, section 837-aa (3)(b) authorizes the Division of Criminal Justice Services to build a library of firearms blueprint files ''"including scans of seized firearms."''<ref name="bill-pdf" />

The statute defines the regulated machine in two prongs at Penal Law section 265.00 (38): any machine that renders an object from a digital design file using additive manufacturing, or any machine that modifies an object from a digital file using subtractive manufacturing.<ref name="bill" /> Writing in Techdirt, Karl Bode argued that the two-prong definition, drafted without a carve-out for machine size or consumer use, would reach CNC milling machines, offline printers, and open-source firmware projects such as Marlin, Klipper, and RepRap.<ref name="techdirt" />

The device-sales requirement is not yet in force. Under section 837-aa, the Division of Criminal Justice Services, the Department of State, and the State University of New York must convene a working group within 90 days of enactment; the group has up to one year to recommend minimum safety standards; the Division then has up to nine months to promulgate performance-standard rules; and the section 396-eeee sales requirement takes effect one year after those rules are promulgated.<ref name="bill-pdf" /> Stacked end to end, those intervals place the earliest possible effective date more than two years after enactment.<ref name="bill-pdf" /> The chain can also stop entirely. Section 837-aa (2) provides a feasibility off-ramp:

<blockquote>''[I]f the working group determines that it is not technologically feasible to require three-dimensional printers sold in the state of New York to include blocking technology, the working group shall so report, and no regulations shall be required to be promulgated pursuant to this section, until such time as the working group determines that it is technologically feasible.''</blockquote><ref name="bill-pdf" />

If the working group makes that finding, no rules issue and the sales requirement is deferred indefinitely.<ref name="bill-pdf" /> Enforcement of the sales requirement is civil and runs through the Attorney General: a gun-industry member found by a court to have violated section 396-eeee is liable for a civil penalty of $5,000 for each qualified product unlawfully sold, and the Attorney General may also sue to enjoin violations and obtain restitution.<ref name="bill-pdf" /> The requirement does not apply to a buyer who holds both a New York gunsmith license under Penal Law section 400.00 and a federal firearms license, and only after the Attorney General verifies the licenses and issues written authorization.<ref name="bill-pdf" />

Alongside the device rule, the budget added digital-file offenses. Penal Law section 265.10 (11) and (12) make it a class A misdemeanor to sell or possess ''"digital firearm manufacturing code"'' outside the licensed channels the statute names.<ref name="bill-pdf" /> The one felony in the package targets hardware rather than files: under section 265.10 (10), a dealer or gunsmith who, on or after May 31, 2027, sells, transfers, or ships a ''"convertible pistol"'', defined as a semi-automatic pistol with a cruciform trigger bar that a pistol converter can turn into a machine gun, commits a class D felony.<ref name="bill-pdf" />

===Other state and local efforts===

{| class="wikitable"
|-
!Measure!!Year!!Jurisdiction!!Status and substance
|-
|HB 2321||2025-26||Washington||Bill titled ''Requiring three-dimensional printers be equipped with certain blocking technologies.'' As reported by Tom's Hardware, it would bar printer sales after July 1, 2027 and set penalties as a class C felony carrying up to five years in prison and a $15,000 fine.<ref name="toms-wa" /><ref name="wa-bill" />
|-
|HB 2320||2025-26||Washington||Companion measure addressing 3D-printed firearms in the same session.<ref name="wa-2320" />
|-
|AB-2047||2026||California||Authored by Assemblymember Rebecca Bauer-Kahan, it would require firearm blocking technology on printers sold in the state and add Penal Code section 29187 making it a misdemeanor to disable or circumvent that technology with intent to manufacture firearms. The Assembly passed the bill, last amended May 18, 2026, and sent it to the Senate.<ref name="ca-bill" /><ref name="toms-ca" />
|-
|HB26-1144||2026||Colorado||Proposed bill that would prohibit using a 3D printer to manufacture a firearm, frame, receiver, large-capacity magazine, or rapid-fire device.<ref name="co-bill" />
|-
|Letter to Creality||2025||New York County||On March 26, 2025, Manhattan District Attorney Alvin Bragg sent a letter to the printer manufacturer Creality urging it to make firearm-detection software a default, remove gun blueprints from its cloud platform, and ban illicit-weapon files in its user agreement; the letter cited Print&Go's "3D GUN'T" software as a model.<ref name="manhattanda" />
|}

===Advocacy & Legislative Support: Everytown for Gun Safety===

Everytown for Gun Safety has served as a principal advocate for upstream regulations that target 3D printer hardware and file distribution. Since 2024, the organization has led advocacy in ten separate bills across eight states, supporting both printer-blocking mandates and manufacturing bans. New York's S.9005-C/A.10005-C, signed into law in May 2026, represents a model of printer-blocking regulation.<ref name="everytown" /> Everytown championed the measure through direct testimony to budget committees, framing the requirement as shutting down the ''plastic pipeline'' of do-it-yourself firearms.<ref name="testimony" /> California's AB 2047, which would require firearm-blocking technology on all printers sold in the state, passed the Assembly in May 2026 with Everytown as a named legislative partner and co-sponsor.<ref name="everytown-ca" />

Washington pursued two approaches: a blocking-technology bill, HB 2321, which was referred to committee in January 2026 and did not advance,<ref name="wa-hb2321" /> and a manufacturing ban, ESHB 2320, signed into law in March 2026, which Everytown supported.<ref name="everytown-wa" /> Colorado's HB26-1144, a manufacturing ban on 3D-printed firearm components, received Everytown advocacy and was signed into law in May 2026.<ref name="everytown-co" />

Everytown also supported manufacturing bans and Glock switch restrictions in Connecticut, Illinois, and Maryland through coalition advocacy with Moms Demand Action and Students Demand Action.<ref name="everytown-ct" /> Vermont's S. 209, a ghost gun prohibition signed into law in May 2024, received written testimony from gun violence prevention advocates.<ref name="everytown-vt" />

For a comprehensive state-by-state breakdown of Everytown-supported 3D printer and manufacturing-restriction bills, including bill status and Everytown's specific role in each jurisdiction, see the companion page [[User:Louis/Everytown for Gun Safety and the 3D printer blocking mandates]].

===Reactions===

Supporters framed the New York law as a public-safety floor. The Governor's office said the budget set ''"first-in-the-nation minimum safety standards for 3D printers sold in New York to be equipped with basic technology that prevents the unlicensed, illegal production of lethal firearms and firearm parts."''<ref name="gov" /> Everytown for Gun Safety praised the package as nation-leading action and described it as shutting down the ''"plastic pipeline"'' of do-it-yourself firearms.<ref name="everytown" /> The National Rifle Association's Institute for Legislative Action objected to enacting the measure through the budget, calling it a ''"strategic move to put divisive legislation into an all-or-nothing budget bill"'' rather than a standalone vote.<ref name="nra" />

Maker and digital-rights groups opposed the printer-side approach. The Electronic Frontier Foundation campaigned against the proposal under the banner ''"Stop New York's Attack on 3D Printing,"'' calling the requirement ''"an unfeasible tech solution"'' and describing print-blocking as ''"censorware"'' that ''"surveils every print."''<ref name="eff" /> Writing in Techdirt, Karl Bode relayed analysis from Phillip Torrone of the open-source hardware company Adafruit, who argued that detection from raw geometry is a classification problem with high error rates.<ref name="techdirt" />

==Technical feasibility==

===What 3D printers can and cannot make===

A firearm concentrates the force of a fired cartridge in a small set of metal parts. The Sporting Arms and Ammunition Manufacturers' Institute sets the maximum average pressure for the 9mm Luger cartridge at 35,000 pounds per square inch, contained on every shot by the barrel, chamber, bolt, and slide.<ref name="saami" /> The frame or lower receiver, which houses the trigger group and keeps the metal parts aligned, bears far less. In its assessment of 3D-printed firearm components, the Small Arms Survey described the division of labor in the AR-15:

<blockquote>''In the AR-15 design, for example, the thermal and mechanical stresses of firing are borne mainly by the barrel, bolt, and upper-receiver assemblies. The lower receiver is primarily intended to ensure the correct alignment and interface of the operating parts of the firearm, and to house the trigger and fire selector and safety mechanisms.''</blockquote><ref name="smallarms" />

Consumer fused-deposition printers can make that low-stress frame in thermoplastic. They cannot make a barrel or chamber that survives a centerfire cartridge.<ref name="smallarms" /> Under federal law the frame or receiver is the regulated part: 18 U.S.C. section 921 (a)(3) includes ''"the frame or receiver of any such weapon,"'' and the Bureau of Alcohol, Tobacco, Firearms and Explosives defines a handgun frame at 27 CFR section 478.12 (a)(1).<ref name="usc921" /><ref name="cfr47812" /> The pressure-bearing barrel and slide carry no such status and are sold online as ordinary parts; a California legislative committee analysis, citing a Department of Justice Office of the Inspector General estimate, put the cost of 3D-printing a 9mm handgun frame and adding unregulated metal components at around $700.<ref name="oig" />

Because the printer makes only the frame, the firearms tied to harm are hybrids. A 2024 study in ''Forensic Science International: Synergy'' catalogued 186 law-enforcement encounters with 3D-printed firearms and recorded only 14 in the fully-3D-printed category, the smallest of its object types, with no discharged firearms among the seizures.<ref name="forensic" /> The Combating Terrorism Center at West Point described hybrid designs as weapons that ''"incorporate 3D-printed components with readily available and unregulated components such as steel tubing, metal bar stocks, and springs."''<ref name="ctc" /> WIRED's Andy Greenberg built and test-fired a clone of the firearm allegedly used by Luigi Mangione and reported that only the frame was printed while the slide, barrel, and trigger parts were purchased metal components; the cycling faults he encountered traced to the purchased slide, not the printed frame.<ref name="wired" />

Machine-gun conversion devices, often called Glock switches, are the category with the largest documented harm record. The ATF reported that recoveries of conversion devices rose from 814 in the 2012 through 2016 period to 5,454 in 2017 through 2021, a 570 percent increase.<ref name="nfcta-news" /> New York's budget reflected that category by making convertible-pistol sales a class D felony.<ref name="bill-pdf" /> At national scale, the Department of Justice reported in January 2025 that ''"Between 2017 and 2023, 92,702 suspected PMFs,"'' untraceable privately made firearms, ''"were recovered and reported"'' to the ATF.<ref name="doj-pmf" />

===Detection methods and their failure modes===

The central technical objection to the scanning mandate is that a printing file describes geometry, not purpose, so a scanner cannot reliably separate a restricted part from an ordinary one. Phillip Torrone of Adafruit, whose analysis Techdirt reproduced, framed the task as a classification problem:

<blockquote>''A firearms blueprint detection algorithm would need to identify every possible firearm component from raw STL/GCODE files, while not flagging pipes, tubes, blocks, brackets, gears, or any of the millions of legitimate shapes that happen to share geometric properties with gun parts. This is a classification problem with enormous false positive and false negative rates.''</blockquote><ref name="techdirt" />

Techdirt also noted that many printers run offline or on community-maintained firmware that no state library reaches, so a scanning requirement could not be enforced on them.<ref name="techdirt" /> The Electronic Frontier Foundation summarized the approach as ''"an unfeasible tech solution."''<ref name="eff" />

===Legitimate prints misflagged as firearm parts===

Critics argue that setting a scanner wide enough to catch a firearm part necessarily flags benign objects built to the same proportions. Torrone's list of shapes that share geometry with gun parts named pipes, tubes, blocks, brackets, and gears.<ref name="techdirt" /> One illustration, developed in a [[User:Louis/3D printer firearm-blocking mandates and geometric false positives|companion essay]], pairs a firearm sound-suppressor baffle, drawn in US Patent 7,987,944 as a conical bell with a central aperture, with the internal cones of Nikola Tesla's 1920 valvular conduit, US Patent 1,329,559.<ref name="baffle" /><ref name="tesla" /> Critics likewise argue that a per-file scan is easily defeated by editing a file slightly or splitting a part into pieces that each resemble nothing in particular.<ref name="techdirt" /><ref name="eff" />

==Consumer-rights and ownership concerns==

The consumer-rights objection is that a blocking mandate puts a state-defined filter between owners and hardware they bought. The Electronic Frontier Foundation framed print-blocking as a return of digital rights management, writing that the New York approach repeats ''"the mistakes of DRM."''<ref name="eff" /> In its ''"Permission to Print"'' series the group tied the tactic to the [[Digital Millennium Copyright Act]], which it said made bypassing code that restricts the use of copyrighted content a federal crime, and treated a mandated filter on an owner's machine as a restriction on lawful use of property.<ref name="eff-permission" />

A second concern is loss of functionality through server dependency. The Electronic Frontier Foundation argued that restricting a device to manufacturer-provided software leaves owners dependent on the vendor and able to use the hardware only on the manufacturer's terms, a dependency illustrated by the cloud-authorization model documented in the [[Bambu Lab Authorization Control System]].<ref name="eff-permission" />

A third concern is copyleft compliance. The slicer and firmware that drive most consumer printers are open-source projects under copyleft licenses. PrusaSlicer and Bambu Studio are released under the GNU Affero General Public License version 3 (AGPLv3), and the firmware projects Marlin and Klipper are released under the GNU General Public License version 3 (GPLv3).<ref name="prusaslicer-lic" /><ref name="bambustudio-lic" /><ref name="marlin-lic" /><ref name="klipper-lic" /> GPLv3 Section 6 requires a distributor of a consumer product to provide the ''"Installation Information"'' needed to install and run a modified version of the covered software on that product, and AGPLv3 Section 13 requires that users interacting with modified software over a network be offered its source.<ref name="gpl3" /><ref name="agpl3" /> Those source-disclosure obligations have been enforced against printer makers: in August 2018 the US distributor Printed Solid stopped selling Creality machines over an unreleased Marlin source violation, and on May 18, 2026 the Software Freedom Conservancy alleged that Bambu Lab violated AGPLv3 by combining Bambu Studio with a proprietary library.<ref name="hackaday-marlin" /><ref name="sfc-bambu" /> A separate dispute over compiled binary modules on Creality's K1 and K2 printers is documented in the [[Creality K2 series GPLv3 violation]] article.

==Court cases==

Whether a firearm design file is protected speech has been litigated apart from the printer mandates.<ref name="ca3" /> In ''Defense Distributed v. Attorney General New Jersey'', No. 23-3058, decided February 12, 2026, the United States Court of Appeals for the Third Circuit affirmed the dismissal of a challenge by Defense Distributed and the Second Amendment Foundation to New Jersey's restrictions on distributing 3D-printed gun code.<ref name="ca3" /><ref name="courthouse" /> The court held that ''"Purely functional code with no expressive purpose, use, or intent is simply not covered by the First Amendment,"'' and affirmed because the plaintiffs had not pleaded that their files were expressive.<ref name="ca3" />

A related question, the federal status of an unfinished frame or receiver, reached the Supreme Court the year before. In ''Bondi v. VanDerStok'', No. 23-852, decided March 26, 2025, the Court upheld the ATF's 2022 frame-or-receiver rule and restated the statutory scheme, writing that under 18 U.S.C. section 921 (a)(3)(B), ''"a frame or receiver is, even when sold separately, subject to the Act's requirements."''<ref name="vanderstok" />

==Manufacturer and platform policies==

Some companies market the kind of filtering that the state mandates would require. Print&Go, a 3D-printing workflow company, sells a product called "3D GUN'T" that it describes as a solution to prevent the printing of 3D-printed ghost guns, and the Manhattan District Attorney's 2025 letter pointed to that software as a model for printer makers to adopt.<ref name="printandgo" /><ref name="manhattanda" /> Other restrictive practices come from the printer makers themselves rather than from third-party filters: cloud-authorization and firmware locks are documented in the [[Bambu Lab Authorization Control System]], and a copyleft-compliance dispute over locked firmware in the [[Creality K2 series GPLv3 violation]].

==See also==
*[[New York 3D printer blocking technology mandate]]
*[[User:Louis/3D-printed firearms and the technical basis for printer mandates]]
*[[User:Louis/3D printer firearm-blocking mandates and geometric false positives]]
*[[Digital Millennium Copyright Act]]
*[[DMCA Section 1201]]
*[[Right to Repair]]
*[[Bambu Lab Authorization Control System]]
*[[FlashForge#Flashforge_threatens_to_report_customers_for_printing_firearms_or_weapon_components|Flashforge threatens to report customers for printing firearms or weapon components]]

==References==
<references>
<ref name="bill">{{Cite web |date=2026-05-27 |title=Senate Bill S9005C, FY2026-2027 budget (Public Protection and General Government), Part C |url=https://www.nysenate.gov/legislation/bills/2025/S9005/amendment/C |url-status=live |archive-url=https://web.archive.org/web/20260529034821/https://www.nysenate.gov/legislation/bills/2025/S9005/amendment/C |archive-date=2026-05-29 |access-date=2026-06-02 |publisher=New York State Senate}} The two-prong three-dimensional printer definition (Penal Law section 265.00(38)), the section 837-aa(1)(b) blocking-technology definition, the section 837-aa(1)(c) firearms blueprint detection algorithm and STL/CAD/geometric-code clause, and the May 27, 2026 signing status appear on this page.</ref>
<ref name="bill-pdf">{{Cite web |date=2026-05-27 |title=Enacted text of A. 10005-C / S. 9005-C, FY2026-2027 budget, Part C |url=https://assembly.ny.gov/2026budget/2026_bills/enacted/A10005c.pdf |url-status=live |archive-url=https://web.archive.org/web/20260603041033/https://assembly.ny.gov/2026budget/2026_bills/enacted/A10005c.pdf |archive-date=2026-06-03 |access-date=2026-06-02 |publisher=New York State Assembly}} The enacted text contains the General Business Law section 396-eeee(1) sales prohibition; the section 396-eeee(5) gunsmith-and-federal-license exemption with written Attorney General authorization; the section 396-eeee(3) $5,000-per-qualified-product civil penalty against a gun industry member and the section 396-eeee(2) Attorney General injunction and restitution authority; the section 837-aa(2) working group, its 90-day convening and one-year recommendation intervals and feasibility clause; the section 837-aa(3) nine-month rulemaking duty and section 837-aa(3)(b) library "including scans of seized firearms"; the Subpart B clause providing that section 396-eeee "shall take effect one year after the promulgation of rules"; and the criminal provisions at Penal Law section 265.10(10)-(12), including the class D felony for convertible-pistol sales on or after May 31, 2027.</ref>
<ref name="gov">{{Cite web |date=2026-05-27 |title=Keeping New Yorkers Safe: Governor Hochul Signs Legislation to Strengthen Public Safety |url=https://www.governor.ny.gov/news/keeping-new-yorkers-safe-governor-hochul-signs-legislation-strengthen-public-safety-and-make |url-status=live |archive-url=https://web.archive.org/web/20260602163827/https://www.governor.ny.gov/news/keeping-new-yorkers-safe-governor-hochul-signs-legislation-strengthen-public-safety-and-make |archive-date=2026-06-02 |access-date=2026-06-02 |publisher=Office of Governor Kathy Hochul}}</ref>
<ref name="everytown">{{Cite web |date=2026-05-21 |title=New York Shuts Down the 'Plastic Pipeline': Governor Hochul and Lawmakers Pass Nation-Leading Measures to Stop the Spread of DIY Machine Guns and 3D-Printed Firearms in FY27 Budget |url=https://www.everytown.org/press/new-york-shuts-down-the-plastic-pipeline-governor-hochul-and-lawmakers-pass-nation-leading-measures-to-stop-the-spread-of-diy-machine-guns-and-3d-printed-firearms-in-fy27-budget/ |url-status=live |archive-url=https://web.archive.org/web/20260603041034/https://www.everytown.org/press/new-york-shuts-down-the-plastic-pipeline-governor-hochul-and-lawmakers-pass-nation-leading-measures-to-stop-the-spread-of-diy-machine-guns-and-3d-printed-firearms-in-fy27-budget/ |archive-date=2026-06-03 |access-date=2026-06-02 |publisher=Everytown for Gun Safety}}</ref>
<ref name="nra">{{Cite web |url=https://www.nraila.org/articles/20260527/new-york-gov-kathy-hochul-signs-gun-ban-in-state-budget-process |title=New York: Gov. Kathy Hochul Signs Gun Ban in State Budget Process |publisher=NRA Institute for Legislative Action |date=2026-05-27 |access-date=2026-06-02}}</ref>
<ref name="wa-bill">{{Cite web |url=https://app.leg.wa.gov/billsummary?BillNumber=2321&Year=2025 |title=HB 2321 - Requiring three-dimensional printers be equipped with certain blocking technologies |publisher=Washington State Legislature |date=2026 |access-date=2026-06-02}}</ref>
<ref name="wa-2320">{{Cite web |url=https://app.leg.wa.gov/billsummary?Year=2025&BillNumber=2320 |title=HB 2320 - 2025-26 |publisher=Washington State Legislature |date=2026 |access-date=2026-06-02}}</ref>
<ref name="toms-wa">{{Cite web |author=Stephen Warwick |date=2026-01-19 |title=Washington state proposes new 3D-printed gun controls with blocking features and blueprint detection algorithm |url=https://www.tomshardware.com/3d-printing/washington-state-proposes-new-3d-printed-gun-controls-with-blocking-features-and-blueprint-detection-algorithm-proposal-would-carry-sentences-of-five-years-in-prison-usd15-000-fine-for-violation |url-status=live |archive-url=https://web.archive.org/web/20260605000447/https://www.tomshardware.com/3d-printing/washington-state-proposes-new-3d-printed-gun-controls-with-blocking-features-and-blueprint-detection-algorithm-proposal-would-carry-sentences-of-five-years-in-prison-usd15-000-fine-for-violation |archive-date=2026-06-05 |access-date=2026-06-02 |publisher=Tom's Hardware}}</ref>
<ref name="ca-bill">{{Cite web |url=https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260AB2047 |title=AB-2047 Firearms: 3-dimensional printing blocking technology |publisher=California Legislative Information |date=2026-05-18 |access-date=2026-06-02}}</ref>
<ref name="toms-ca">{{Cite web |url=https://www.tomshardware.com/3d-printing/california-assembly-passes-3d-printer-bill-that-would-criminalize-bypassing-mandated-gun-blocking-software |title=California Assembly passes 3D printer bill that would criminalize bypassing mandated gun-blocking software |author=Luke James |publisher=Tom's Hardware |date=2026-05-30 |access-date=2026-06-02}}</ref>
<ref name="co-bill">{{Cite web |url=https://leg.colorado.gov/bills/HB26-1144 |title=HB26-1144: Prohibit Three-Dimensional Printing Firearms and Components |publisher=Colorado General Assembly |date=2026 |access-date=2026-06-02}}</ref>
<ref name="manhattanda">{{Cite web |url=https://manhattanda.org/wp-content/uploads/2025/03/Letter-Creality-3.26.25.pdf |title=Letter to Shenzhen Creality 3D Technology Co. |author=Alvin L. Bragg, Jr. |publisher=New York County District Attorney's Office |date=2025-03-26 |access-date=2026-06-02}} The March 26, 2025 letter urges Creality to make firearm-detection software a default, remove gun blueprints from its cloud platform, and ban illicit-weapon files in its user agreement, and cites Print&GO's "3D GUN'T" software as a model.</ref>
<ref name="printandgo">{{Cite web |url=https://printandgo.tech/blog/3d-gunt-solution-to-prevent-3d-printed-ghost-guns |title=3D GUN'T: Print&Go's solution to prevent 3D printed 'Ghost Guns' |publisher=Print&Go |date=2024-11-04 |access-date=2026-06-02}}</ref>
<ref name="saami">{{Cite web |url=https://www.outdoorlife.com/guns/what-is-p-ammo/ |title=What Is +P Ammo? |publisher=Outdoor Life |date=2021-06-01 |access-date=2026-06-02}} States the SAAMI maximum average pressure of 35,000 psi for the 9mm Luger cartridge.</ref>
<ref name="smallarms">{{Cite web |url=https://www.smallarmssurvey.org/sites/default/files/resources/SAS-OP32-Behind-the-Curve.pdf |title=Behind the Curve: New Technologies, New Control Challenges (Occasional Paper 32) |author=N.R. Jenzen-Jones |publisher=Small Arms Survey |date=2015 |access-date=2026-06-02}} Page 68 states that the AR-15 lower receiver "is primarily intended to ensure the correct alignment and interface of the operating parts of the firearm, and to house the trigger and fire selector and safety mechanisms."</ref>
<ref name="usc921">{{Cite web |url=https://www.law.cornell.edu/uscode/text/18/921 |title=18 U.S.C. section 921, Definitions |publisher=Legal Information Institute, Cornell Law School |date=2024 |access-date=2026-06-02}} Defines a firearm to include "(B) the frame or receiver of any such weapon."</ref>
<ref name="cfr47812">{{Cite web |url=https://www.ecfr.gov/current/title-27/chapter-II/subchapter-B/part-478/subject-group-ECFR0f9b5e597e57820/section-478.12 |title=27 CFR section 478.12, Definition of frame or receiver |publisher=Code of Federal Regulations |date=2022 |access-date=2026-06-02}}</ref>
<ref name="oig">{{Cite web |url=https://apsf.assembly.ca.gov/sites/apsf.assembly.ca.gov/files/AB%201089%20PCA%20Revised%20Version%20Final%20PDF.pdf |title=Assembly Bill 1089 committee analysis |publisher=California State Assembly Committee on Public Safety |date=2023 |access-date=2026-06-02}} Page 5 states that the Office of the Inspector General "estimated that the full cost for 3D printing a 9 millimeter handgun frame and adding unregulated firearm components (such as the barrel, trigger, slide, magazine, etc.) was around $700."</ref>
<ref name="forensic">{{Cite web |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC10998078/ |title=The emergence of 3D-printed firearms: a forensic and criminological overview |publisher=Forensic Science International: Synergy |date=2024 |access-date=2026-06-02}} Catalogues 186 law-enforcement encounters; records 14 cases in the fully-3D-printed (F3DP) category, the fewest of its object types, and reports no discharged firearms among the seizures.</ref>
<ref name="ctc">{{Cite web |url=https://ctc.westpoint.edu/printing-terror-an-empirical-overview-of-the-use-of-3d-printed-firearms-by-right-wing-extremists/ |title=Printing Terror: An Empirical Overview of the Use of 3D-Printed Firearms by Right-Wing Extremists |publisher=Combating Terrorism Center at West Point |date=2024 |access-date=2026-06-02}}</ref>
<ref name="wired">{{Cite web |url=https://www.wired.com/story/luigi-mangione-ghost-gun-built-tested/ |title=We Built the Ghost Gun Luigi Mangione Allegedly Used, and Tested It |author=Andy Greenberg |publisher=WIRED |date=2025-05-19 |access-date=2026-06-02}} Reports that only the frame was printed while the slide, barrel, and trigger components were purchased metal parts, and that cycling faults traced to the purchased slide rather than the printed frame.</ref>
<ref name="nfcta-news">{{Cite web |url=https://www.news4jax.com/news/local/2023/02/14/atf-number-of-confiscated-illegal-machine-gun-conversion-devices-jump-570-in-5-years/ |title=ATF: Number of confiscated illegal machine gun conversion devices jump 570% in 5 years |author=Erik Avanier |publisher=News4JAX (WJXT) |date=2023-02-14 |access-date=2026-06-02}} Reports the ATF figures of 814 conversion devices confiscated 2012 to 2016 and 5,454 in 2017 to 2021, a 570% increase.</ref>
<ref name="doj-pmf">{{Cite web |url=https://www.justice.gov/archives/opa/pr/justice-department-announces-atfs-publication-final-volume-national-firearms-commerce-and |title=Justice Department Announces ATF's Publication of the Final Volume of the National Firearms Commerce and Trafficking Assessment |publisher=United States Department of Justice |date=2025-01-16 |access-date=2026-06-02}} States that "Between 2017 and 2023, 92,702 suspected PMFs ... were recovered and reported."</ref>
<ref name="eff">{{Cite web |url=https://www.eff.org/deeplinks/2026/04/stop-new-yorks-attack-3d-printing |title=Stop New York's Attack on 3D Printing |author=Rory Mir and Nathan Sheard |publisher=Electronic Frontier Foundation |date=2026-04-16 |access-date=2026-06-02}} Calls the requirement "an unfeasible tech solution," describes print-blocking "censorware" that "surveils every print," and writes that the approach repeats "the mistakes of DRM."</ref>
<ref name="eff-permission">{{Cite web |url=https://www.eff.org/deeplinks/2026/04/print-blocking-anti-consumer-permission-print-part-1 |title=Print Blocking is Anti-Consumer: Permission to Print Part 1 |publisher=Electronic Frontier Foundation |date=2026-04-02 |access-date=2026-06-02}}</ref>
<ref name="techdirt">{{Cite web |url=https://www.techdirt.com/2026/02/19/new-yorks-new-3d-printing-law-as-written-is-extremely-harmful-and-annoying/ |title=New York's New 3D Printing Law, As Written, Is Extremely Harmful And Annoying |author=Karl Bode |publisher=Techdirt |date=2026-02-19 |access-date=2026-06-02}} Reproduces Phillip Torrone of Adafruit on detection as "a classification problem with enormous false positive and false negative rates," on G-code as tool paths, and on the law reaching open-source firmware such as Marlin, Klipper, and RepRap and offline machines.</ref>
<ref name="baffle">{{Cite web |url=https://patents.google.com/patent/US7987944B1 |title=US Patent 7,987,944 B1, Firearm sound suppressor baffle |publisher=United States Patent and Trademark Office |date=2011-08-02 |access-date=2026-06-02}} Figures show a conical bell with a central aperture and a rear plate within an outer tube.</ref>
<ref name="tesla">{{Cite web |url=https://patents.google.com/patent/US1329559A |title=US Patent 1,329,559, Valvular Conduit |author=Nikola Tesla |publisher=United States Patent and Trademark Office |date=1920-02-03 |access-date=2026-06-02}} Drawings show internal cones that pass fluid one way and resist it the other.</ref>
<ref name="gpl3">{{Cite web |url=https://www.gnu.org/licenses/gpl-3.0.html |title=GNU General Public License, version 3 |publisher=Free Software Foundation |date=2007-06-29 |access-date=2026-06-02 |archive-url=https://web.archive.org/web/20260602103622/https://www.gnu.org/licenses/gpl-3.0.html |archive-date=2026-06-02 |url-status=live}} Section 6 defines the Installation Information a distributor must provide with a User Product and defines a User Product to include a consumer product.</ref>
<ref name="agpl3">{{Cite web |url=https://www.gnu.org/licenses/agpl-3.0.html |title=GNU Affero General Public License, version 3 |publisher=Free Software Foundation |date=2007-11-19 |access-date=2026-06-02 |archive-url=https://web.archive.org/web/20260602064947/https://www.gnu.org/licenses/agpl-3.0.html |archive-date=2026-06-02 |url-status=live}} Section 13 requires a modified version that supports remote network interaction to offer interacting users an opportunity to receive the Corresponding Source.</ref>
<ref name="prusaslicer-lic">{{Cite web |url=https://github.com/prusa3d/PrusaSlicer/blob/master/LICENSE |title=PrusaSlicer LICENSE file |publisher=Prusa Research (GitHub) |access-date=2026-06-02}} Identifies PrusaSlicer as licensed under the GNU Affero General Public License v3.0.</ref>
<ref name="bambustudio-lic">{{Cite web |url=https://github.com/bambulab/BambuStudio/blob/master/LICENSE |title=BambuStudio LICENSE file |publisher=Bambu Lab (GitHub) |access-date=2026-06-02}} Identifies bambulab/BambuStudio as licensed under the GNU Affero General Public License v3.0.</ref>
<ref name="marlin-lic">{{Cite web |url=https://github.com/MarlinFirmware/Marlin/blob/2.1.x/LICENSE |title=Marlin LICENSE file |publisher=MarlinFirmware (GitHub) |access-date=2026-06-02}} Reproduces the GNU General Public License Version 3.</ref>
<ref name="klipper-lic">{{Cite web |url=https://github.com/Klipper3d/klipper/blob/master/COPYING |title=Klipper COPYING file |publisher=Klipper3d (GitHub) |access-date=2026-06-02}} Reproduces the GNU General Public License Version 3.</ref>
<ref name="hackaday-marlin">{{Cite web |url=https://hackaday.com/2018/08/27/gpl-violations-cost-creality-a-us-distributor/ |title=GPL Violations Cost Creality A US Distributor |author=Tom Nardi |publisher=Hackaday |date=2018-08-27 |access-date=2026-06-02}} Reports that US distributor Printed Solid stopped selling Creality printers over unreleased Marlin (GPLv3) corresponding source on the CR-10 line.</ref>
<ref name="sfc-bambu">{{Cite web |url=https://sfconservancy.org/news/2026/may/18/bambu-studio-3d-printer-agpl-violation-response/ |title=Comprehensive Response to Bambu's AGPLv3 Violations |publisher=Software Freedom Conservancy |date=2026-05-18 |access-date=2026-06-02}} States that Bambu does not provide the complete Corresponding Source for Bambu Studio and combines it with a proprietary library.</ref>
<ref name="ca3">{{Cite web |url=https://www2.ca3.uscourts.gov/opinarch/233058p.pdf |title=Defense Distributed v. Attorney General New Jersey, No. 23-3058 |publisher=United States Court of Appeals for the Third Circuit |date=2026-02-12 |access-date=2026-06-02}} Page 30 states "Purely functional code with no expressive purpose, use, or intent is simply not covered by the First Amendment"; the court affirmed dismissal because the plaintiffs failed to plead that their files were expressive.</ref>
<ref name="courthouse">{{Cite web |url=https://www.courthousenews.com/third-circuit-backs-new-jerseys-crackdown-on-3d-printed-gun-code/ |title=Third Circuit backs New Jersey's crackdown on 3D-printed gun code |publisher=Courthouse News Service |date=2026-02-12 |access-date=2026-06-02}}</ref>
<ref name="vanderstok">{{Cite web |url=https://www.supremecourt.gov/opinions/24pdf/23-852_c07d.pdf |title=Bondi v. VanDerStok, No. 23-852 |publisher=Supreme Court of the United States |date=2025-03-26 |access-date=2026-06-02}} Page 7 states that "a frame or receiver is, even when sold separately, subject to the Act's requirements"; the Court upheld the ATF's 2022 frame-or-receiver rule.</ref>
<ref name="testimony">{{Cite web |url=https://www.nysenate.gov/sites/default/files/admin/structure/media/manage/filefile/a/2026-03/everytown-for-gun-safety.pdf |title=Testimony of Everytown for Gun Safety to the Senate Finance Committee and Assembly Ways and Means Committee in Support of PPGG Part C |author=Elisabeth Ryan |publisher=Everytown for Gun Safety |date=2026-02-12 |access-date=2026-06-02}} Policy counsel Elisabeth Ryan's written testimony on behalf of Everytown for Gun Safety supporting New York's 3D printer blocking mandate.</ref>
<ref name="pipeline">{{Cite web |url=https://www.everytown.org/press/new-york-shuts-down-the-plastic-pipeline-governor-hochul-and-lawmakers-pass-nation-leading-measures-to-stop-the-spread-of-diy-machine-guns-and-3d-printed-firearms-in-fy27-budget/ |title=New York Shuts Down the 'Plastic Pipeline': Governor Hochul and Lawmakers Pass Nation-Leading Measures to Stop the Spread of DIY Machine Guns and 3D-Printed Firearms in FY27 Budget |publisher=Everytown for Gun Safety |date=2026-05-21 |access-date=2026-06-02}}</ref>
<ref name="everytown-ca">{{Cite web |url=https://www.everytown.org/press/california-assembly-passes-landmark-bill-to-stop-the-rise-of-3d-printed-ghost-guns/ |title=California Assembly Passes Landmark Bill to Stop the Rise of 3D-Printed Ghost Guns |publisher=Everytown for Gun Safety |date=2026-05-27 |access-date=2026-06-02}} States that AB 2047 "would require that consumer 3D printers sold in California include existing technology capable of blocking attempts to print firearms and illegal gun parts."</ref>
<ref name="wa-hb2321">{{Cite web |url=https://app.leg.wa.gov/billsummary?BillNumber=2321&Year=2025 |title=HB 2321 - Requiring three-dimensional printers be equipped with certain blocking technologies |publisher=Washington State Legislature |access-date=2026-06-02}}</ref>
<ref name="everytown-wa">{{Cite web |url=https://www.everytown.org/press/washington-legislature-passes-critical-bill-to-address-threat-of-3d-printed-ghost-guns/ |title=Washington Legislature Passes Critical Bill to Address Threat of 3D-Printed Ghost Guns |publisher=Everytown for Gun Safety |date=2026-03-11 |access-date=2026-06-02}}</ref>
<ref name="everytown-co">{{Cite web |url=https://www.everytown.org/press/governor-polis-signs-hb-1144-into-law-marking-step-forward-on-tackling-the-spread-of-3d-printed-guns-as-advocates-push-for-stronger-action/ |title=Governor Polis Signs HB 1144 Into Law, Marking Step Forward on Tackling the Spread of 3D-Printed Guns as Advocates Push for Stronger Action |publisher=Everytown for Gun Safety |date=2026-05-04 |access-date=2026-06-02}}</ref>
<ref name="everytown-ct">{{Cite web |url=https://www.everytown.org/press/connecticut-chapters-of-moms-demand-action-students-demand-action-applaud-governor-ned-lamonts-bold-move-to-stop-the-spread-of-diy-machine-guns/ |title=Connecticut Chapters of Moms Demand Action, Students Demand Action Applaud Governor Ned Lamont's Bold Move to Stop the Spread of DIY Machine Guns |publisher=Everytown for Gun Safety |date=2026 |access-date=2026-06-02}}</ref>
<ref name="everytown-vt">{{Cite web |url=https://www.everytown.org/press/victory-for-gun-safety-vermont-governor-phil-scott-allows-bill-to-prohibit-unserialized-ghost-guns-to-become-law-moms-demand-action-and-students-demand-action-respond/ |title=Victory for Gun Safety: Vermont Governor Phil Scott Allows Bill to Prohibit Unserialized Ghost Guns to Become Law |publisher=Everytown for Gun Safety |date=2024-05-28 |access-date=2026-06-02}}</ref>
</references>

[[Category:Anti-consumer practices]]
[[Category:Right to Repair]]
[[Category:Legislation]]
[[Category:Digital rights management]]

Flashforge

2026-06-07T01:38:17Z

Wownyc: the second f is lowercase

{{CompanyCargo
|Description=Forces Adventurer 5M/AD5X owners onto proprietary Flash Studio slicer with banner ads; class action filed over heating & extruder defects
|Founded=2011
|Industry=3D printing,Consumer electronics
|Logo=FlashForge.png
|ParentCompany=
|CompanyAlias=Zhejiang Flashforge 3D Technology Co. Ltd.,Flashforge
|Type=Private
|Website=https://www.flashforge.com/
}}

'''Flashforge''' (legal name: '''Zhejiang Flashforge 3D Technology Co., Ltd.''') is a Chinese desktop & industrial 3D printer manufacturer founded in 2011.<ref name="ff-about">{{Cite web |url=https://www.flashforge.com/pages/about-us |title=About Us - Flashforge |website=Flashforge |access-date=May 22, 2026}}</ref> Between February 2025 and May 2026, Flashforge progressively closed the network architecture of its Adventurer 5M & AD5X consumer 3D printers, pushing owners towards a proprietary slicer carrying a banner advertisement for a $1 Meshy.ai membership offer, and which broke third-party slicer compatibility documented in OrcaSlicer GitHub issues #5154, #10112, #10260, & #11658.<ref name="ff-service-notice">{{Cite web |url=https://www.flashforge.com/blogs/news/service-upgrade-notification |title=Service Upgrade Notification |website=Flashforge |access-date=May 22, 2026}}</ref><ref name="ff-meshy">{{Cite web |url=https://www.flashforge.com/blogs/news/flashforge-meshy-ai |title=Flashforge × Meshy AI: From AI Ideas to Real Prints |date=2026-05-20 |website=Flashforge |access-date=May 22, 2026}}</ref> The same printers are the subject of a February 2026 class-action investigation by the Washington, D.C. consumer-protection firm Migliaccio & Rathod LLP over recurring heating, extruder, and auto-leveling failures.<ref name="classlaw-ff">{{Cite web |url=https://classlawdc.com/2026/02/25/flashforge-3d-printer-investigation/ |title=Flashforge 3D Printer Investigation |date=2026-02-25 |website=Migliaccio & Rathod LLP |access-date=May 22, 2026}}</ref>

== Consumer-impact summary ==

* '''Vendor lock-in via firmware update.''' The March 25, 2025 ''"Service Upgrade Notification"'' set hard version floors that retired the open networking pathways previously used by mainline OrcaSlicer and third-party tooling.<ref name="ff-service-notice" />
* '''In-app advertising.''' Flash Studio Desktop (the rebranded Orca-Flashforge) carries a banner promoting a $1 Meshy.ai membership offer inside its printer-management view.<ref name="ff-meshy" />
* '''Open-source license dispute.''' OrcaSlicer issue #5154 alleges Flashforge bundled the GPLv3-licensed OrcaSlicer fork with a restrictive commercial EULA prohibiting redistribution, modification, and reverse engineering.<ref name="orca-5154">{{Cite web |url=https://github.com/SoftFever/OrcaSlicer/issues/5154 |title=Flashforge is violating OrcaSlicer's GPLv3 license (Issue #5154) |date=2024-04-26 |website=GitHub: SoftFever/OrcaSlicer |access-date=May 22, 2026}}</ref>
* '''Class-action investigation.''' Migliaccio & Rathod LLP solicits Adventurer 5M & AD5X owners reporting nozzle heating failures, premature extruder breakage, and auto-leveling crashes that gouge the build plate.<ref name="classlaw-ff" />
* '''Telemetry without disclosed source.''' Orca-Flashforge issue #26 documents the desktop slicer making outbound connections to roughly twenty hostnames (including a competitor API and the NetEase IM library) that do not appear in the company's published source repository.<ref name="orca-ff-26">{{Cite web |url=https://github.com/FlashForge/Orca-Flashforge/issues/26 |title=Provide actual codebase which exposes all connections (Issue #26) |date=2025-11-15 |website=GitHub: FlashForge/Orca-Flashforge |access-date=May 22, 2026}}</ref>

== Background ==

Flashforge was incorporated in 2011 as Zhejiang Flashforge 3D Technology Co., Ltd.<ref name="ff-about" /> The company manufactures desktop FDM 3D printers (the Adventurer, Creator, Guider, and Inventor lines), resin and DLP printers (the Foto and Hunter lines), and industrial wax 3D printers (the WaxJet series).<ref name="ff-about" /> Its budget sub-brand '''Voxelab''' targets entry-level consumers, and a U.S. distribution arm operates under the name Flashforge USA.<ref name="ff-usa">{{Cite web |url=https://www.flashforge-usa.com/ |title=Flashforge USA |website=Flashforge USA |access-date=May 22, 2026}}</ref>

Flashforge originally shipped open network protocols on its FDM printers. An August 15, 2024, a Flashforge blog post described Orca-Flashforge (a fork of SoftFever's open-source OrcaSlicer) as the recommended slicer for the Adventurer 5M series & Guider 3 Ultra,<ref name="ff-orca-guide" /> & Adventurer 5M firmware 2.6.5 (April 11, 2024) added ''"Support Orca-Flashforge connection"'' & a LAN mode.<ref name="ff-orca-guide">{{Cite web |url=https://www.flashforge.com/blogs/news/orca-and-orca-flashforge-a-comprehensive-guide |title=Orca and Orca-Flashforge: A Comprehensive Guide |date=2024-08-15 |website=Flashforge |access-date=May 22, 2026}}</ref><ref name="ff-5m-changelog">{{Cite web |url=https://www.flashforge.com/a/docs/adventurer-5m-series/adventurer-5m-series-firmware-update-log |title=Adventurer 5M Series Firmware Update Log |website=Flashforge |access-date=May 22, 2026}}</ref> The 2025 service migration replaced that posture with a closed, cloud-mediated architecture.

== Incidents ==

=== Flash Studio mandatory slicer advertising and third-party slicer lockout ===

{{Main|FlashForge Flash Studio mandatory slicer advertising and third-party slicer lockout}}

In early 2025 Flashforge published a ''"Service Upgrade Notification"'' announcing the retirement of its legacy server services on March 26, 2025 & requiring Adventurer 5M, Adventurer 5M Pro, & Guider 3 Ultra owners to update firmware to v3.1.0 or later & the Orca-Flashforge desktop slicer to v1.3.0 or later.<ref name="ff-service-notice" /> Orca-Flashforge was subsequently rebranded to Flash Studio Desktop, & on May 20, 2026 the company announced a Meshy.ai partnership that embedded a banner promoting a $1 Meshy membership offer inside the slicer's printer-management view.<ref name="ff-meshy" /> Owners running mainline OrcaSlicer 2.3.0 against post-migration firmware report ''"ERR_CONNECTION_REFUSED"'' errors on the device tab (OrcaSlicer issue #10260, July 28, 2025).<ref name="orca-10260">{{Cite web |url=https://github.com/OrcaSlicer/OrcaSlicer/issues/10260 |title=Device Section of Orca Slicer not working with Flashforge AD5M (Issue #10260) |date=2025-07-28 |website=GitHub: OrcaSlicer/OrcaSlicer |access-date=May 22, 2026}}</ref> Two community Klipper-based firmware mods (''xblax/flashforge_ad5m_klipper_mod'' & ''DrA1ex/ff5m'') restore open networking at the cost of voiding the manufacturer warranty.<ref name="klipper-xblax">{{Cite web |url=https://github.com/xblax/flashforge_ad5m_klipper_mod |title=Unofficial mod for Flashforge Adventurer 5M (Pro) 3D printers to run Moonraker, custom Klipper, Mainsail and Fluidd |website=GitHub: xblax/flashforge_ad5m_klipper_mod |access-date=May 22, 2026}}</ref>

=== Flashforge threatens to report customers for printing firearms or weapon components ===

In late 2025, Flashforge posted an infographic titled '''NO to weaponized 3D printing''' on Facebook, threatening to report customers printing firearms or weapon components to "authorities"<ref>https://www.reddit.com/r/3Dprinting/comments/1owqkqs/flashforge_telling_and_threatening_their_users/</ref><ref>https://www.reddit.com/r/Firearms/comments/1oxtrni/3d_printer_manufacturer_flashforge_openly/</ref>, implying that it has the capability to view users prints, or to mitigate liability.

The Facebook post has been reproduced below:
<div style="width: 30vw; color: gray;">
We build tools for creation--never for harm. 
Flashforge stands for safe, responsible 3D printing.
</div>
<div style="width: 30vw; color: gray; text-align: center">
NO to weaponized 3D printing

Flashforge does not support or condone the 3D printing of firearms or weapon components. (Subject to the Flashforge user agreement.)

Flashforge prohibits using our products and services to create firearms or weapon components. Violations may lead to account termination and refer- ral to authorities.
</div>

Privately made firearms are legal in the United States, at least federally.<ref>https://www.atf.gov/firearms/privately-made-firearms</ref>

The Facebook post was later retracted.{{Citation needed}}

=== Adventurer 5M & AD5X hardware-defect class-action investigation ===

On February 25, 2026 the Washington, D.C. consumer-protection law firm Migliaccio & Rathod LLP opened a class-action investigation soliciting Adventurer 5M & AD5X owners whose printers exhibit recurring failures.<ref name="classlaw-ff" /> The firm's intake page lists specific defect patterns: nozzles that fail to heat or hold temperature, printers that stop working within days or months of purchase, premature extruder & filament-feeder breakage, repeated jams & feeding errors, & auto-leveling failures resulting in nozzle scraping & poor first-layer adhesion.<ref name="classlaw-ff" /> The firm solicits affected owners through an online intake form.<ref name="classlaw-ff" /> Tom's Hardware reviewer Denise Bertacchi, in a published October 12, 2025 AD5X review, separately reported that the bundled Orca-Flashforge slicer ''"is perhaps the least stable version"'' of OrcaSlicer she had used, crashing about every third print.<ref name="tomshardware-ad5x">{{Cite web |url=https://www.tomshardware.com/3d-printing/flashforge-ad5x-review |title=Flashforge AD5X review: An affordable option for fast color 3D printing |last=Bertacchi |first=Denise |date=2025-10-12 |website=Tom's Hardware |access-date=May 22, 2026}}</ref> The investigation is open as of May 2026; no class certification or settlement has been announced.<ref name="classlaw-ff" />

== Products ==

Flashforge sells three families of additive-manufacturing hardware plus the proprietary Flash Studio software suite.

* '''Adventurer 5M series.''' CoreXY FDM printers including the Adventurer 5M (open frame) & Adventurer 5M Pro (enclosed with HEPA filtration). Affected by the March 2025 service migration & the Migliaccio & Rathod class-action investigation.<ref name="ff-service-notice" /><ref name="classlaw-ff" />
* '''Adventurer 5X (AD5X).''' Multi-color CoreXY FDM printer with an Intelligent Filament System. Affected by the same firmware lockout & class-action investigation, & the subject of the October 2025 Tom's Hardware stability review.<ref name="tomshardware-ad5x" /><ref name="classlaw-ff" />
* '''Creator 5 / Creator 5 Pro.''' Four-toolhead changing systems heavily promoted in the Meshy.ai partnership materials.<ref name="ff-meshy" /><ref name="prnewswire-meshy">{{Cite web |url=https://www.prnewswire.com/news-releases/flashforge-and-meshy-partner-to-bring-ai-image-to-3d-directly-into-consumer-multi-color-printing-302778460.html |title=FlashForge and Meshy Partner to Bring AI Image-to-3D Directly Into Consumer Multi-Color Printing |date=2026-05-21 |website=PR Newswire |access-date=May 22, 2026}}</ref>
* '''Guider 3 Ultra.''' Enterprise-tier FDM printer also covered by the March 2025 service migration's mandatory firmware floor.<ref name="ff-service-notice" />
* '''Software.''' Flash Studio Desktop (formerly Orca-Flashforge; a GPLv3 fork of SoftFever's OrcaSlicer), Flash Studio Mobile (formerly Flash Maker), & the legacy FlashPrint slicer.<ref name="ff-meshy" /><ref name="orca-5154" />
* '''Legacy & adjacent lines.''' Creator (2011-), Creator Pro, Creator 3, Dreamer, Finder, Adventurer 3 & 4, Inventor, Guider II, Foto 8.9 LCD resin, Hunter S DLP, & the industrial WaxJet 400/510/530 wax-pattern printers.<ref name="ff-about" />

The budget sub-brand Voxelab markets entry-level FDM & resin printers separately from the main Flashforge catalogue.<ref name="ff-about" />

== See also ==

* [[FlashForge Flash Studio mandatory slicer advertising and third-party slicer lockout]]
* [[Bambu Lab Authorization Control System]]

== References ==

<references />

[[Category:Companies]]
[[Category:FlashForge]]
[[Category:3D printing]]
[[Category:Chinese companies]]

3D Printing restrictions and bans

2026-06-07T01:34:56Z

Wownyc: /* See also */

'''3D Printing restrictions and bans''' are legal, technical, and policy limits that governments, platforms, and manufacturers place on how consumer 3D printers may be bought, modified, or used. The most far-reaching example is a New York law, enacted in May 2026, that will require every 3D printer sold in the state to carry ''"blocking technology"'' which checks each print file against a firearms blueprint detection algorithm before the machine will run the job.<ref name="bill" /> The Governor's office and the gun-safety group Everytown for Gun Safety described the measure as first-in-the-nation.<ref name="gov" /><ref name="everytown" /> The printer-sales requirement is not yet in force. It takes effect one year after state rules are written, those rules cannot begin until an expert working group reports, and a feasibility clause lets that group shelve the mandate if it finds the scanning technology does not work.<ref name="bill" /><ref name="bill-pdf" />

==How restrictions are imposed==

Restrictions on consumer 3D printers take several forms, often combined:

*'''Legislation.''' State laws and bills can restrict how printers are sold or used. New York's budget law requires printers sold in the state to carry firearm-blocking technology, and Washington and California have advanced similar bills.<ref name="bill" /><ref name="toms-wa" /><ref name="toms-ca" />
*'''Firmware and software locks.''' Manufacturers can gate printer functionality behind signed firmware, mandatory cloud connections, or authorization checks, as documented with [[Bambu Lab Authorization Control System|Bambu Lab's Authorization Control System]].
*'''Platform and service dependency.''' Printers can depend on a proprietary slicer, a cloud account, or an online authorization server to remain fully functional.
*'''Content and model filtering.''' Software can scan, flag, or refuse particular model files or print jobs. New York's blocking-technology mandate would require this kind of per-file screening by law.<ref name="bill" />
*'''Support withdrawal.''' A manufacturer can declare a device unsupported and disable features through software updates or by shutting down the servers the device depends on, a [[Planned obsolescence|planned-obsolescence]] risk for any cloud-tied printer.

==Firearm-blocking printer mandates==

In 2026 several states moved to regulate 3D-printed firearms through the printer itself rather than only the design file or the finished weapon. New York enacted the first such law; Washington and California advanced bills along the same lines, and Colorado and the Manhattan District Attorney pursued narrower measures.<ref name="bill" /><ref name="toms-wa" /><ref name="toms-ca" /><ref name="co-bill" /><ref name="manhattanda" />

===New York blocking-technology mandate===

{{Main|New York 3D printer blocking technology mandate}}

New York's mandate was enacted as Part C of the FY2026-2027 budget, bills S.9005-C and A.10005-C, and signed by Governor Kathy Hochul on May 27, 2026.<ref name="gov" /><ref name="bill" /> The operative command is in the new General Business Law section 396-eeee (1):

<blockquote>''No person, firm, partnership, association, or corporation shall sell or deliver any three-dimensional printer in the state of New York unless such printer is equipped with blocking technology.''</blockquote><ref name="bill-pdf" />

Executive Law section 837-aa (1)(b) defines that blocking technology as integrated measures that keep a printer from running any job unless the file has been evaluated by a firearms blueprint detection algorithm and found not to produce a firearm or illegal firearm parts.<ref name="bill" /> The algorithm, defined in section 837-aa (1)(c), reads printing files ''"whether in the form of stereolithography (STL) files or other computer aided design files or geometric code."''<ref name="bill" /> To supply data for those checks, section 837-aa (3)(b) authorizes the Division of Criminal Justice Services to build a library of firearms blueprint files ''"including scans of seized firearms."''<ref name="bill-pdf" />

The statute defines the regulated machine in two prongs at Penal Law section 265.00 (38): any machine that renders an object from a digital design file using additive manufacturing, or any machine that modifies an object from a digital file using subtractive manufacturing.<ref name="bill" /> Writing in Techdirt, Karl Bode argued that the two-prong definition, drafted without a carve-out for machine size or consumer use, would reach CNC milling machines, offline printers, and open-source firmware projects such as Marlin, Klipper, and RepRap.<ref name="techdirt" />

The device-sales requirement is not yet in force. Under section 837-aa, the Division of Criminal Justice Services, the Department of State, and the State University of New York must convene a working group within 90 days of enactment; the group has up to one year to recommend minimum safety standards; the Division then has up to nine months to promulgate performance-standard rules; and the section 396-eeee sales requirement takes effect one year after those rules are promulgated.<ref name="bill-pdf" /> Stacked end to end, those intervals place the earliest possible effective date more than two years after enactment.<ref name="bill-pdf" /> The chain can also stop entirely. Section 837-aa (2) provides a feasibility off-ramp:

<blockquote>''[I]f the working group determines that it is not technologically feasible to require three-dimensional printers sold in the state of New York to include blocking technology, the working group shall so report, and no regulations shall be required to be promulgated pursuant to this section, until such time as the working group determines that it is technologically feasible.''</blockquote><ref name="bill-pdf" />

If the working group makes that finding, no rules issue and the sales requirement is deferred indefinitely.<ref name="bill-pdf" /> Enforcement of the sales requirement is civil and runs through the Attorney General: a gun-industry member found by a court to have violated section 396-eeee is liable for a civil penalty of $5,000 for each qualified product unlawfully sold, and the Attorney General may also sue to enjoin violations and obtain restitution.<ref name="bill-pdf" /> The requirement does not apply to a buyer who holds both a New York gunsmith license under Penal Law section 400.00 and a federal firearms license, and only after the Attorney General verifies the licenses and issues written authorization.<ref name="bill-pdf" />

Alongside the device rule, the budget added digital-file offenses. Penal Law section 265.10 (11) and (12) make it a class A misdemeanor to sell or possess ''"digital firearm manufacturing code"'' outside the licensed channels the statute names.<ref name="bill-pdf" /> The one felony in the package targets hardware rather than files: under section 265.10 (10), a dealer or gunsmith who, on or after May 31, 2027, sells, transfers, or ships a ''"convertible pistol"'', defined as a semi-automatic pistol with a cruciform trigger bar that a pistol converter can turn into a machine gun, commits a class D felony.<ref name="bill-pdf" />

===Other state and local efforts===

{| class="wikitable"
|-
!Measure!!Year!!Jurisdiction!!Status and substance
|-
|HB 2321||2025-26||Washington||Bill titled ''Requiring three-dimensional printers be equipped with certain blocking technologies.'' As reported by Tom's Hardware, it would bar printer sales after July 1, 2027 and set penalties as a class C felony carrying up to five years in prison and a $15,000 fine.<ref name="toms-wa" /><ref name="wa-bill" />
|-
|HB 2320||2025-26||Washington||Companion measure addressing 3D-printed firearms in the same session.<ref name="wa-2320" />
|-
|AB-2047||2026||California||Authored by Assemblymember Rebecca Bauer-Kahan, it would require firearm blocking technology on printers sold in the state and add Penal Code section 29187 making it a misdemeanor to disable or circumvent that technology with intent to manufacture firearms. The Assembly passed the bill, last amended May 18, 2026, and sent it to the Senate.<ref name="ca-bill" /><ref name="toms-ca" />
|-
|HB26-1144||2026||Colorado||Proposed bill that would prohibit using a 3D printer to manufacture a firearm, frame, receiver, large-capacity magazine, or rapid-fire device.<ref name="co-bill" />
|-
|Letter to Creality||2025||New York County||On March 26, 2025, Manhattan District Attorney Alvin Bragg sent a letter to the printer manufacturer Creality urging it to make firearm-detection software a default, remove gun blueprints from its cloud platform, and ban illicit-weapon files in its user agreement; the letter cited Print&Go's "3D GUN'T" software as a model.<ref name="manhattanda" />
|}

===Advocacy & Legislative Support: Everytown for Gun Safety===

Everytown for Gun Safety has served as a principal advocate for upstream regulations that target 3D printer hardware and file distribution. Since 2024, the organization has led advocacy in ten separate bills across eight states, supporting both printer-blocking mandates and manufacturing bans. New York's S.9005-C/A.10005-C, signed into law in May 2026, represents a model of printer-blocking regulation.<ref name="everytown" /> Everytown championed the measure through direct testimony to budget committees, framing the requirement as shutting down the ''plastic pipeline'' of do-it-yourself firearms.<ref name="testimony" /> California's AB 2047, which would require firearm-blocking technology on all printers sold in the state, passed the Assembly in May 2026 with Everytown as a named legislative partner and co-sponsor.<ref name="everytown-ca" />

Washington pursued two approaches: a blocking-technology bill, HB 2321, which was referred to committee in January 2026 and did not advance,<ref name="wa-hb2321" /> and a manufacturing ban, ESHB 2320, signed into law in March 2026, which Everytown supported.<ref name="everytown-wa" /> Colorado's HB26-1144, a manufacturing ban on 3D-printed firearm components, received Everytown advocacy and was signed into law in May 2026.<ref name="everytown-co" />

Everytown also supported manufacturing bans and Glock switch restrictions in Connecticut, Illinois, and Maryland through coalition advocacy with Moms Demand Action and Students Demand Action.<ref name="everytown-ct" /> Vermont's S. 209, a ghost gun prohibition signed into law in May 2024, received written testimony from gun violence prevention advocates.<ref name="everytown-vt" />

For a comprehensive state-by-state breakdown of Everytown-supported 3D printer and manufacturing-restriction bills, including bill status and Everytown's specific role in each jurisdiction, see the companion page [[User:Louis/Everytown for Gun Safety and the 3D printer blocking mandates]].

===Reactions===

Supporters framed the New York law as a public-safety floor. The Governor's office said the budget set ''"first-in-the-nation minimum safety standards for 3D printers sold in New York to be equipped with basic technology that prevents the unlicensed, illegal production of lethal firearms and firearm parts."''<ref name="gov" /> Everytown for Gun Safety praised the package as nation-leading action and described it as shutting down the ''"plastic pipeline"'' of do-it-yourself firearms.<ref name="everytown" /> The National Rifle Association's Institute for Legislative Action objected to enacting the measure through the budget, calling it a ''"strategic move to put divisive legislation into an all-or-nothing budget bill"'' rather than a standalone vote.<ref name="nra" />

Maker and digital-rights groups opposed the printer-side approach. The Electronic Frontier Foundation campaigned against the proposal under the banner ''"Stop New York's Attack on 3D Printing,"'' calling the requirement ''"an unfeasible tech solution"'' and describing print-blocking as ''"censorware"'' that ''"surveils every print."''<ref name="eff" /> Writing in Techdirt, Karl Bode relayed analysis from Phillip Torrone of the open-source hardware company Adafruit, who argued that detection from raw geometry is a classification problem with high error rates.<ref name="techdirt" />

==Technical feasibility==

===What 3D printers can and cannot make===

A firearm concentrates the force of a fired cartridge in a small set of metal parts. The Sporting Arms and Ammunition Manufacturers' Institute sets the maximum average pressure for the 9mm Luger cartridge at 35,000 pounds per square inch, contained on every shot by the barrel, chamber, bolt, and slide.<ref name="saami" /> The frame or lower receiver, which houses the trigger group and keeps the metal parts aligned, bears far less. In its assessment of 3D-printed firearm components, the Small Arms Survey described the division of labor in the AR-15:

<blockquote>''In the AR-15 design, for example, the thermal and mechanical stresses of firing are borne mainly by the barrel, bolt, and upper-receiver assemblies. The lower receiver is primarily intended to ensure the correct alignment and interface of the operating parts of the firearm, and to house the trigger and fire selector and safety mechanisms.''</blockquote><ref name="smallarms" />

Consumer fused-deposition printers can make that low-stress frame in thermoplastic. They cannot make a barrel or chamber that survives a centerfire cartridge.<ref name="smallarms" /> Under federal law the frame or receiver is the regulated part: 18 U.S.C. section 921 (a)(3) includes ''"the frame or receiver of any such weapon,"'' and the Bureau of Alcohol, Tobacco, Firearms and Explosives defines a handgun frame at 27 CFR section 478.12 (a)(1).<ref name="usc921" /><ref name="cfr47812" /> The pressure-bearing barrel and slide carry no such status and are sold online as ordinary parts; a California legislative committee analysis, citing a Department of Justice Office of the Inspector General estimate, put the cost of 3D-printing a 9mm handgun frame and adding unregulated metal components at around $700.<ref name="oig" />

Because the printer makes only the frame, the firearms tied to harm are hybrids. A 2024 study in ''Forensic Science International: Synergy'' catalogued 186 law-enforcement encounters with 3D-printed firearms and recorded only 14 in the fully-3D-printed category, the smallest of its object types, with no discharged firearms among the seizures.<ref name="forensic" /> The Combating Terrorism Center at West Point described hybrid designs as weapons that ''"incorporate 3D-printed components with readily available and unregulated components such as steel tubing, metal bar stocks, and springs."''<ref name="ctc" /> WIRED's Andy Greenberg built and test-fired a clone of the firearm allegedly used by Luigi Mangione and reported that only the frame was printed while the slide, barrel, and trigger parts were purchased metal components; the cycling faults he encountered traced to the purchased slide, not the printed frame.<ref name="wired" />

Machine-gun conversion devices, often called Glock switches, are the category with the largest documented harm record. The ATF reported that recoveries of conversion devices rose from 814 in the 2012 through 2016 period to 5,454 in 2017 through 2021, a 570 percent increase.<ref name="nfcta-news" /> New York's budget reflected that category by making convertible-pistol sales a class D felony.<ref name="bill-pdf" /> At national scale, the Department of Justice reported in January 2025 that ''"Between 2017 and 2023, 92,702 suspected PMFs,"'' untraceable privately made firearms, ''"were recovered and reported"'' to the ATF.<ref name="doj-pmf" />

===Detection methods and their failure modes===

The central technical objection to the scanning mandate is that a printing file describes geometry, not purpose, so a scanner cannot reliably separate a restricted part from an ordinary one. Phillip Torrone of Adafruit, whose analysis Techdirt reproduced, framed the task as a classification problem:

<blockquote>''A firearms blueprint detection algorithm would need to identify every possible firearm component from raw STL/GCODE files, while not flagging pipes, tubes, blocks, brackets, gears, or any of the millions of legitimate shapes that happen to share geometric properties with gun parts. This is a classification problem with enormous false positive and false negative rates.''</blockquote><ref name="techdirt" />

Techdirt also noted that many printers run offline or on community-maintained firmware that no state library reaches, so a scanning requirement could not be enforced on them.<ref name="techdirt" /> The Electronic Frontier Foundation summarized the approach as ''"an unfeasible tech solution."''<ref name="eff" />

===Legitimate prints misflagged as firearm parts===

Critics argue that setting a scanner wide enough to catch a firearm part necessarily flags benign objects built to the same proportions. Torrone's list of shapes that share geometry with gun parts named pipes, tubes, blocks, brackets, and gears.<ref name="techdirt" /> One illustration, developed in a [[User:Louis/3D printer firearm-blocking mandates and geometric false positives|companion essay]], pairs a firearm sound-suppressor baffle, drawn in US Patent 7,987,944 as a conical bell with a central aperture, with the internal cones of Nikola Tesla's 1920 valvular conduit, US Patent 1,329,559.<ref name="baffle" /><ref name="tesla" /> Critics likewise argue that a per-file scan is easily defeated by editing a file slightly or splitting a part into pieces that each resemble nothing in particular.<ref name="techdirt" /><ref name="eff" />

==Consumer-rights and ownership concerns==

The consumer-rights objection is that a blocking mandate puts a state-defined filter between owners and hardware they bought. The Electronic Frontier Foundation framed print-blocking as a return of digital rights management, writing that the New York approach repeats ''"the mistakes of DRM."''<ref name="eff" /> In its ''"Permission to Print"'' series the group tied the tactic to the [[Digital Millennium Copyright Act]], which it said made bypassing code that restricts the use of copyrighted content a federal crime, and treated a mandated filter on an owner's machine as a restriction on lawful use of property.<ref name="eff-permission" />

A second concern is loss of functionality through server dependency. The Electronic Frontier Foundation argued that restricting a device to manufacturer-provided software leaves owners dependent on the vendor and able to use the hardware only on the manufacturer's terms, a dependency illustrated by the cloud-authorization model documented in the [[Bambu Lab Authorization Control System]].<ref name="eff-permission" />

A third concern is copyleft compliance. The slicer and firmware that drive most consumer printers are open-source projects under copyleft licenses. PrusaSlicer and Bambu Studio are released under the GNU Affero General Public License version 3 (AGPLv3), and the firmware projects Marlin and Klipper are released under the GNU General Public License version 3 (GPLv3).<ref name="prusaslicer-lic" /><ref name="bambustudio-lic" /><ref name="marlin-lic" /><ref name="klipper-lic" /> GPLv3 Section 6 requires a distributor of a consumer product to provide the ''"Installation Information"'' needed to install and run a modified version of the covered software on that product, and AGPLv3 Section 13 requires that users interacting with modified software over a network be offered its source.<ref name="gpl3" /><ref name="agpl3" /> Those source-disclosure obligations have been enforced against printer makers: in August 2018 the US distributor Printed Solid stopped selling Creality machines over an unreleased Marlin source violation, and on May 18, 2026 the Software Freedom Conservancy alleged that Bambu Lab violated AGPLv3 by combining Bambu Studio with a proprietary library.<ref name="hackaday-marlin" /><ref name="sfc-bambu" /> A separate dispute over compiled binary modules on Creality's K1 and K2 printers is documented in the [[Creality K2 series GPLv3 violation]] article.

==Court cases==

Whether a firearm design file is protected speech has been litigated apart from the printer mandates.<ref name="ca3" /> In ''Defense Distributed v. Attorney General New Jersey'', No. 23-3058, decided February 12, 2026, the United States Court of Appeals for the Third Circuit affirmed the dismissal of a challenge by Defense Distributed and the Second Amendment Foundation to New Jersey's restrictions on distributing 3D-printed gun code.<ref name="ca3" /><ref name="courthouse" /> The court held that ''"Purely functional code with no expressive purpose, use, or intent is simply not covered by the First Amendment,"'' and affirmed because the plaintiffs had not pleaded that their files were expressive.<ref name="ca3" />

A related question, the federal status of an unfinished frame or receiver, reached the Supreme Court the year before. In ''Bondi v. VanDerStok'', No. 23-852, decided March 26, 2025, the Court upheld the ATF's 2022 frame-or-receiver rule and restated the statutory scheme, writing that under 18 U.S.C. section 921 (a)(3)(B), ''"a frame or receiver is, even when sold separately, subject to the Act's requirements."''<ref name="vanderstok" />

==Manufacturer and platform policies==

Some companies market the kind of filtering that the state mandates would require. Print&Go, a 3D-printing workflow company, sells a product called "3D GUN'T" that it describes as a solution to prevent the printing of 3D-printed ghost guns, and the Manhattan District Attorney's 2025 letter pointed to that software as a model for printer makers to adopt.<ref name="printandgo" /><ref name="manhattanda" /> Other restrictive practices come from the printer makers themselves rather than from third-party filters: cloud-authorization and firmware locks are documented in the [[Bambu Lab Authorization Control System]], and a copyleft-compliance dispute over locked firmware in the [[Creality K2 series GPLv3 violation]].

==See also==
*[[New York 3D printer blocking technology mandate]]
*[[User:Louis/3D-printed firearms and the technical basis for printer mandates]]
*[[User:Louis/3D printer firearm-blocking mandates and geometric false positives]]
*[[Digital Millennium Copyright Act]]
*[[DMCA Section 1201]]
*[[Right to Repair]]
*[[Bambu Lab Authorization Control System]]
*[[FlashForge#Flashforge_threatens_to_report_customers_for_printing_firearms_or_weapon_components|Flashforge threatens to report customers for printing firearms or weapon components]]

==References==
<references>
<ref name="bill">{{Cite web |date=2026-05-27 |title=Senate Bill S9005C, FY2026-2027 budget (Public Protection and General Government), Part C |url=https://www.nysenate.gov/legislation/bills/2025/S9005/amendment/C |url-status=live |archive-url=https://web.archive.org/web/20260529034821/https://www.nysenate.gov/legislation/bills/2025/S9005/amendment/C |archive-date=2026-05-29 |access-date=2026-06-02 |publisher=New York State Senate}} The two-prong three-dimensional printer definition (Penal Law section 265.00(38)), the section 837-aa(1)(b) blocking-technology definition, the section 837-aa(1)(c) firearms blueprint detection algorithm and STL/CAD/geometric-code clause, and the May 27, 2026 signing status appear on this page.</ref>
<ref name="bill-pdf">{{Cite web |date=2026-05-27 |title=Enacted text of A. 10005-C / S. 9005-C, FY2026-2027 budget, Part C |url=https://assembly.ny.gov/2026budget/2026_bills/enacted/A10005c.pdf |url-status=live |archive-url=https://web.archive.org/web/20260603041033/https://assembly.ny.gov/2026budget/2026_bills/enacted/A10005c.pdf |archive-date=2026-06-03 |access-date=2026-06-02 |publisher=New York State Assembly}} The enacted text contains the General Business Law section 396-eeee(1) sales prohibition; the section 396-eeee(5) gunsmith-and-federal-license exemption with written Attorney General authorization; the section 396-eeee(3) $5,000-per-qualified-product civil penalty against a gun industry member and the section 396-eeee(2) Attorney General injunction and restitution authority; the section 837-aa(2) working group, its 90-day convening and one-year recommendation intervals and feasibility clause; the section 837-aa(3) nine-month rulemaking duty and section 837-aa(3)(b) library "including scans of seized firearms"; the Subpart B clause providing that section 396-eeee "shall take effect one year after the promulgation of rules"; and the criminal provisions at Penal Law section 265.10(10)-(12), including the class D felony for convertible-pistol sales on or after May 31, 2027.</ref>
<ref name="gov">{{Cite web |date=2026-05-27 |title=Keeping New Yorkers Safe: Governor Hochul Signs Legislation to Strengthen Public Safety |url=https://www.governor.ny.gov/news/keeping-new-yorkers-safe-governor-hochul-signs-legislation-strengthen-public-safety-and-make |url-status=live |archive-url=https://web.archive.org/web/20260602163827/https://www.governor.ny.gov/news/keeping-new-yorkers-safe-governor-hochul-signs-legislation-strengthen-public-safety-and-make |archive-date=2026-06-02 |access-date=2026-06-02 |publisher=Office of Governor Kathy Hochul}}</ref>
<ref name="everytown">{{Cite web |date=2026-05-21 |title=New York Shuts Down the 'Plastic Pipeline': Governor Hochul and Lawmakers Pass Nation-Leading Measures to Stop the Spread of DIY Machine Guns and 3D-Printed Firearms in FY27 Budget |url=https://www.everytown.org/press/new-york-shuts-down-the-plastic-pipeline-governor-hochul-and-lawmakers-pass-nation-leading-measures-to-stop-the-spread-of-diy-machine-guns-and-3d-printed-firearms-in-fy27-budget/ |url-status=live |archive-url=https://web.archive.org/web/20260603041034/https://www.everytown.org/press/new-york-shuts-down-the-plastic-pipeline-governor-hochul-and-lawmakers-pass-nation-leading-measures-to-stop-the-spread-of-diy-machine-guns-and-3d-printed-firearms-in-fy27-budget/ |archive-date=2026-06-03 |access-date=2026-06-02 |publisher=Everytown for Gun Safety}}</ref>
<ref name="nra">{{Cite web |url=https://www.nraila.org/articles/20260527/new-york-gov-kathy-hochul-signs-gun-ban-in-state-budget-process |title=New York: Gov. Kathy Hochul Signs Gun Ban in State Budget Process |publisher=NRA Institute for Legislative Action |date=2026-05-27 |access-date=2026-06-02}}</ref>
<ref name="wa-bill">{{Cite web |url=https://app.leg.wa.gov/billsummary?BillNumber=2321&Year=2025 |title=HB 2321 - Requiring three-dimensional printers be equipped with certain blocking technologies |publisher=Washington State Legislature |date=2026 |access-date=2026-06-02}}</ref>
<ref name="wa-2320">{{Cite web |url=https://app.leg.wa.gov/billsummary?Year=2025&BillNumber=2320 |title=HB 2320 - 2025-26 |publisher=Washington State Legislature |date=2026 |access-date=2026-06-02}}</ref>
<ref name="toms-wa">{{Cite web |author=Stephen Warwick |date=2026-01-19 |title=Washington state proposes new 3D-printed gun controls with blocking features and blueprint detection algorithm |url=https://www.tomshardware.com/3d-printing/washington-state-proposes-new-3d-printed-gun-controls-with-blocking-features-and-blueprint-detection-algorithm-proposal-would-carry-sentences-of-five-years-in-prison-usd15-000-fine-for-violation |url-status=live |archive-url=https://web.archive.org/web/20260605000447/https://www.tomshardware.com/3d-printing/washington-state-proposes-new-3d-printed-gun-controls-with-blocking-features-and-blueprint-detection-algorithm-proposal-would-carry-sentences-of-five-years-in-prison-usd15-000-fine-for-violation |archive-date=2026-06-05 |access-date=2026-06-02 |publisher=Tom's Hardware}}</ref>
<ref name="ca-bill">{{Cite web |url=https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260AB2047 |title=AB-2047 Firearms: 3-dimensional printing blocking technology |publisher=California Legislative Information |date=2026-05-18 |access-date=2026-06-02}}</ref>
<ref name="toms-ca">{{Cite web |url=https://www.tomshardware.com/3d-printing/california-assembly-passes-3d-printer-bill-that-would-criminalize-bypassing-mandated-gun-blocking-software |title=California Assembly passes 3D printer bill that would criminalize bypassing mandated gun-blocking software |author=Luke James |publisher=Tom's Hardware |date=2026-05-30 |access-date=2026-06-02}}</ref>
<ref name="co-bill">{{Cite web |url=https://leg.colorado.gov/bills/HB26-1144 |title=HB26-1144: Prohibit Three-Dimensional Printing Firearms and Components |publisher=Colorado General Assembly |date=2026 |access-date=2026-06-02}}</ref>
<ref name="manhattanda">{{Cite web |url=https://manhattanda.org/wp-content/uploads/2025/03/Letter-Creality-3.26.25.pdf |title=Letter to Shenzhen Creality 3D Technology Co. |author=Alvin L. Bragg, Jr. |publisher=New York County District Attorney's Office |date=2025-03-26 |access-date=2026-06-02}} The March 26, 2025 letter urges Creality to make firearm-detection software a default, remove gun blueprints from its cloud platform, and ban illicit-weapon files in its user agreement, and cites Print&GO's "3D GUN'T" software as a model.</ref>
<ref name="printandgo">{{Cite web |url=https://printandgo.tech/blog/3d-gunt-solution-to-prevent-3d-printed-ghost-guns |title=3D GUN'T: Print&Go's solution to prevent 3D printed 'Ghost Guns' |publisher=Print&Go |date=2024-11-04 |access-date=2026-06-02}}</ref>
<ref name="saami">{{Cite web |url=https://www.outdoorlife.com/guns/what-is-p-ammo/ |title=What Is +P Ammo? |publisher=Outdoor Life |date=2021-06-01 |access-date=2026-06-02}} States the SAAMI maximum average pressure of 35,000 psi for the 9mm Luger cartridge.</ref>
<ref name="smallarms">{{Cite web |url=https://www.smallarmssurvey.org/sites/default/files/resources/SAS-OP32-Behind-the-Curve.pdf |title=Behind the Curve: New Technologies, New Control Challenges (Occasional Paper 32) |author=N.R. Jenzen-Jones |publisher=Small Arms Survey |date=2015 |access-date=2026-06-02}} Page 68 states that the AR-15 lower receiver "is primarily intended to ensure the correct alignment and interface of the operating parts of the firearm, and to house the trigger and fire selector and safety mechanisms."</ref>
<ref name="usc921">{{Cite web |url=https://www.law.cornell.edu/uscode/text/18/921 |title=18 U.S.C. section 921, Definitions |publisher=Legal Information Institute, Cornell Law School |date=2024 |access-date=2026-06-02}} Defines a firearm to include "(B) the frame or receiver of any such weapon."</ref>
<ref name="cfr47812">{{Cite web |url=https://www.ecfr.gov/current/title-27/chapter-II/subchapter-B/part-478/subject-group-ECFR0f9b5e597e57820/section-478.12 |title=27 CFR section 478.12, Definition of frame or receiver |publisher=Code of Federal Regulations |date=2022 |access-date=2026-06-02}}</ref>
<ref name="oig">{{Cite web |url=https://apsf.assembly.ca.gov/sites/apsf.assembly.ca.gov/files/AB%201089%20PCA%20Revised%20Version%20Final%20PDF.pdf |title=Assembly Bill 1089 committee analysis |publisher=California State Assembly Committee on Public Safety |date=2023 |access-date=2026-06-02}} Page 5 states that the Office of the Inspector General "estimated that the full cost for 3D printing a 9 millimeter handgun frame and adding unregulated firearm components (such as the barrel, trigger, slide, magazine, etc.) was around $700."</ref>
<ref name="forensic">{{Cite web |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC10998078/ |title=The emergence of 3D-printed firearms: a forensic and criminological overview |publisher=Forensic Science International: Synergy |date=2024 |access-date=2026-06-02}} Catalogues 186 law-enforcement encounters; records 14 cases in the fully-3D-printed (F3DP) category, the fewest of its object types, and reports no discharged firearms among the seizures.</ref>
<ref name="ctc">{{Cite web |url=https://ctc.westpoint.edu/printing-terror-an-empirical-overview-of-the-use-of-3d-printed-firearms-by-right-wing-extremists/ |title=Printing Terror: An Empirical Overview of the Use of 3D-Printed Firearms by Right-Wing Extremists |publisher=Combating Terrorism Center at West Point |date=2024 |access-date=2026-06-02}}</ref>
<ref name="wired">{{Cite web |url=https://www.wired.com/story/luigi-mangione-ghost-gun-built-tested/ |title=We Built the Ghost Gun Luigi Mangione Allegedly Used, and Tested It |author=Andy Greenberg |publisher=WIRED |date=2025-05-19 |access-date=2026-06-02}} Reports that only the frame was printed while the slide, barrel, and trigger components were purchased metal parts, and that cycling faults traced to the purchased slide rather than the printed frame.</ref>
<ref name="nfcta-news">{{Cite web |url=https://www.news4jax.com/news/local/2023/02/14/atf-number-of-confiscated-illegal-machine-gun-conversion-devices-jump-570-in-5-years/ |title=ATF: Number of confiscated illegal machine gun conversion devices jump 570% in 5 years |author=Erik Avanier |publisher=News4JAX (WJXT) |date=2023-02-14 |access-date=2026-06-02}} Reports the ATF figures of 814 conversion devices confiscated 2012 to 2016 and 5,454 in 2017 to 2021, a 570% increase.</ref>
<ref name="doj-pmf">{{Cite web |url=https://www.justice.gov/archives/opa/pr/justice-department-announces-atfs-publication-final-volume-national-firearms-commerce-and |title=Justice Department Announces ATF's Publication of the Final Volume of the National Firearms Commerce and Trafficking Assessment |publisher=United States Department of Justice |date=2025-01-16 |access-date=2026-06-02}} States that "Between 2017 and 2023, 92,702 suspected PMFs ... were recovered and reported."</ref>
<ref name="eff">{{Cite web |url=https://www.eff.org/deeplinks/2026/04/stop-new-yorks-attack-3d-printing |title=Stop New York's Attack on 3D Printing |author=Rory Mir and Nathan Sheard |publisher=Electronic Frontier Foundation |date=2026-04-16 |access-date=2026-06-02}} Calls the requirement "an unfeasible tech solution," describes print-blocking "censorware" that "surveils every print," and writes that the approach repeats "the mistakes of DRM."</ref>
<ref name="eff-permission">{{Cite web |url=https://www.eff.org/deeplinks/2026/04/print-blocking-anti-consumer-permission-print-part-1 |title=Print Blocking is Anti-Consumer: Permission to Print Part 1 |publisher=Electronic Frontier Foundation |date=2026-04-02 |access-date=2026-06-02}}</ref>
<ref name="techdirt">{{Cite web |url=https://www.techdirt.com/2026/02/19/new-yorks-new-3d-printing-law-as-written-is-extremely-harmful-and-annoying/ |title=New York's New 3D Printing Law, As Written, Is Extremely Harmful And Annoying |author=Karl Bode |publisher=Techdirt |date=2026-02-19 |access-date=2026-06-02}} Reproduces Phillip Torrone of Adafruit on detection as "a classification problem with enormous false positive and false negative rates," on G-code as tool paths, and on the law reaching open-source firmware such as Marlin, Klipper, and RepRap and offline machines.</ref>
<ref name="baffle">{{Cite web |url=https://patents.google.com/patent/US7987944B1 |title=US Patent 7,987,944 B1, Firearm sound suppressor baffle |publisher=United States Patent and Trademark Office |date=2011-08-02 |access-date=2026-06-02}} Figures show a conical bell with a central aperture and a rear plate within an outer tube.</ref>
<ref name="tesla">{{Cite web |url=https://patents.google.com/patent/US1329559A |title=US Patent 1,329,559, Valvular Conduit |author=Nikola Tesla |publisher=United States Patent and Trademark Office |date=1920-02-03 |access-date=2026-06-02}} Drawings show internal cones that pass fluid one way and resist it the other.</ref>
<ref name="gpl3">{{Cite web |url=https://www.gnu.org/licenses/gpl-3.0.html |title=GNU General Public License, version 3 |publisher=Free Software Foundation |date=2007-06-29 |access-date=2026-06-02 |archive-url=https://web.archive.org/web/20260602103622/https://www.gnu.org/licenses/gpl-3.0.html |archive-date=2026-06-02 |url-status=live}} Section 6 defines the Installation Information a distributor must provide with a User Product and defines a User Product to include a consumer product.</ref>
<ref name="agpl3">{{Cite web |url=https://www.gnu.org/licenses/agpl-3.0.html |title=GNU Affero General Public License, version 3 |publisher=Free Software Foundation |date=2007-11-19 |access-date=2026-06-02 |archive-url=https://web.archive.org/web/20260602064947/https://www.gnu.org/licenses/agpl-3.0.html |archive-date=2026-06-02 |url-status=live}} Section 13 requires a modified version that supports remote network interaction to offer interacting users an opportunity to receive the Corresponding Source.</ref>
<ref name="prusaslicer-lic">{{Cite web |url=https://github.com/prusa3d/PrusaSlicer/blob/master/LICENSE |title=PrusaSlicer LICENSE file |publisher=Prusa Research (GitHub) |access-date=2026-06-02}} Identifies PrusaSlicer as licensed under the GNU Affero General Public License v3.0.</ref>
<ref name="bambustudio-lic">{{Cite web |url=https://github.com/bambulab/BambuStudio/blob/master/LICENSE |title=BambuStudio LICENSE file |publisher=Bambu Lab (GitHub) |access-date=2026-06-02}} Identifies bambulab/BambuStudio as licensed under the GNU Affero General Public License v3.0.</ref>
<ref name="marlin-lic">{{Cite web |url=https://github.com/MarlinFirmware/Marlin/blob/2.1.x/LICENSE |title=Marlin LICENSE file |publisher=MarlinFirmware (GitHub) |access-date=2026-06-02}} Reproduces the GNU General Public License Version 3.</ref>
<ref name="klipper-lic">{{Cite web |url=https://github.com/Klipper3d/klipper/blob/master/COPYING |title=Klipper COPYING file |publisher=Klipper3d (GitHub) |access-date=2026-06-02}} Reproduces the GNU General Public License Version 3.</ref>
<ref name="hackaday-marlin">{{Cite web |url=https://hackaday.com/2018/08/27/gpl-violations-cost-creality-a-us-distributor/ |title=GPL Violations Cost Creality A US Distributor |author=Tom Nardi |publisher=Hackaday |date=2018-08-27 |access-date=2026-06-02}} Reports that US distributor Printed Solid stopped selling Creality printers over unreleased Marlin (GPLv3) corresponding source on the CR-10 line.</ref>
<ref name="sfc-bambu">{{Cite web |url=https://sfconservancy.org/news/2026/may/18/bambu-studio-3d-printer-agpl-violation-response/ |title=Comprehensive Response to Bambu's AGPLv3 Violations |publisher=Software Freedom Conservancy |date=2026-05-18 |access-date=2026-06-02}} States that Bambu does not provide the complete Corresponding Source for Bambu Studio and combines it with a proprietary library.</ref>
<ref name="ca3">{{Cite web |url=https://www2.ca3.uscourts.gov/opinarch/233058p.pdf |title=Defense Distributed v. Attorney General New Jersey, No. 23-3058 |publisher=United States Court of Appeals for the Third Circuit |date=2026-02-12 |access-date=2026-06-02}} Page 30 states "Purely functional code with no expressive purpose, use, or intent is simply not covered by the First Amendment"; the court affirmed dismissal because the plaintiffs failed to plead that their files were expressive.</ref>
<ref name="courthouse">{{Cite web |url=https://www.courthousenews.com/third-circuit-backs-new-jerseys-crackdown-on-3d-printed-gun-code/ |title=Third Circuit backs New Jersey's crackdown on 3D-printed gun code |publisher=Courthouse News Service |date=2026-02-12 |access-date=2026-06-02}}</ref>
<ref name="vanderstok">{{Cite web |url=https://www.supremecourt.gov/opinions/24pdf/23-852_c07d.pdf |title=Bondi v. VanDerStok, No. 23-852 |publisher=Supreme Court of the United States |date=2025-03-26 |access-date=2026-06-02}} Page 7 states that "a frame or receiver is, even when sold separately, subject to the Act's requirements"; the Court upheld the ATF's 2022 frame-or-receiver rule.</ref>
<ref name="testimony">{{Cite web |url=https://www.nysenate.gov/sites/default/files/admin/structure/media/manage/filefile/a/2026-03/everytown-for-gun-safety.pdf |title=Testimony of Everytown for Gun Safety to the Senate Finance Committee and Assembly Ways and Means Committee in Support of PPGG Part C |author=Elisabeth Ryan |publisher=Everytown for Gun Safety |date=2026-02-12 |access-date=2026-06-02}} Policy counsel Elisabeth Ryan's written testimony on behalf of Everytown for Gun Safety supporting New York's 3D printer blocking mandate.</ref>
<ref name="pipeline">{{Cite web |url=https://www.everytown.org/press/new-york-shuts-down-the-plastic-pipeline-governor-hochul-and-lawmakers-pass-nation-leading-measures-to-stop-the-spread-of-diy-machine-guns-and-3d-printed-firearms-in-fy27-budget/ |title=New York Shuts Down the 'Plastic Pipeline': Governor Hochul and Lawmakers Pass Nation-Leading Measures to Stop the Spread of DIY Machine Guns and 3D-Printed Firearms in FY27 Budget |publisher=Everytown for Gun Safety |date=2026-05-21 |access-date=2026-06-02}}</ref>
<ref name="everytown-ca">{{Cite web |url=https://www.everytown.org/press/california-assembly-passes-landmark-bill-to-stop-the-rise-of-3d-printed-ghost-guns/ |title=California Assembly Passes Landmark Bill to Stop the Rise of 3D-Printed Ghost Guns |publisher=Everytown for Gun Safety |date=2026-05-27 |access-date=2026-06-02}} States that AB 2047 "would require that consumer 3D printers sold in California include existing technology capable of blocking attempts to print firearms and illegal gun parts."</ref>
<ref name="wa-hb2321">{{Cite web |url=https://app.leg.wa.gov/billsummary?BillNumber=2321&Year=2025 |title=HB 2321 - Requiring three-dimensional printers be equipped with certain blocking technologies |publisher=Washington State Legislature |access-date=2026-06-02}}</ref>
<ref name="everytown-wa">{{Cite web |url=https://www.everytown.org/press/washington-legislature-passes-critical-bill-to-address-threat-of-3d-printed-ghost-guns/ |title=Washington Legislature Passes Critical Bill to Address Threat of 3D-Printed Ghost Guns |publisher=Everytown for Gun Safety |date=2026-03-11 |access-date=2026-06-02}}</ref>
<ref name="everytown-co">{{Cite web |url=https://www.everytown.org/press/governor-polis-signs-hb-1144-into-law-marking-step-forward-on-tackling-the-spread-of-3d-printed-guns-as-advocates-push-for-stronger-action/ |title=Governor Polis Signs HB 1144 Into Law, Marking Step Forward on Tackling the Spread of 3D-Printed Guns as Advocates Push for Stronger Action |publisher=Everytown for Gun Safety |date=2026-05-04 |access-date=2026-06-02}}</ref>
<ref name="everytown-ct">{{Cite web |url=https://www.everytown.org/press/connecticut-chapters-of-moms-demand-action-students-demand-action-applaud-governor-ned-lamonts-bold-move-to-stop-the-spread-of-diy-machine-guns/ |title=Connecticut Chapters of Moms Demand Action, Students Demand Action Applaud Governor Ned Lamont's Bold Move to Stop the Spread of DIY Machine Guns |publisher=Everytown for Gun Safety |date=2026 |access-date=2026-06-02}}</ref>
<ref name="everytown-vt">{{Cite web |url=https://www.everytown.org/press/victory-for-gun-safety-vermont-governor-phil-scott-allows-bill-to-prohibit-unserialized-ghost-guns-to-become-law-moms-demand-action-and-students-demand-action-respond/ |title=Victory for Gun Safety: Vermont Governor Phil Scott Allows Bill to Prohibit Unserialized Ghost Guns to Become Law |publisher=Everytown for Gun Safety |date=2024-05-28 |access-date=2026-06-02}}</ref>
</references>

[[Category:Anti-consumer practices]]
[[Category:Right to Repair]]
[[Category:Legislation]]
[[Category:Digital rights management]]

Flashforge

2026-06-07T01:30:43Z

Wownyc: /* Flashforge threatens to report customers for printing firearms or weapon components */

{{CompanyCargo
|Description=Forces Adventurer 5M/AD5X owners onto proprietary Flash Studio slicer with banner ads; class action filed over heating & extruder defects
|Founded=2011
|Industry=3D printing,Consumer electronics
|Logo=FlashForge.png
|ParentCompany=
|CompanyAlias=Zhejiang Flashforge 3D Technology Co. Ltd.,Flashforge
|Type=Private
|Website=https://www.flashforge.com/
}}

'''FlashForge''' (legal name: '''Zhejiang Flashforge 3D Technology Co., Ltd.''') is a Chinese desktop & industrial 3D printer manufacturer founded in 2011.<ref name="ff-about">{{Cite web |url=https://www.flashforge.com/pages/about-us |title=About Us - Flashforge |website=Flashforge |access-date=May 22, 2026}}</ref> Between February 2025 & May 2026 FlashForge progressively closed the network architecture of its Adventurer 5M & AD5X consumer 3D printers, pushing owners towards a proprietary slicer carrying a banner advertisement for a $1 Meshy.ai membership offer, and which broke third-party slicer compatibility documented in OrcaSlicer GitHub issues #5154, #10112, #10260, & #11658.<ref name="ff-service-notice">{{Cite web |url=https://www.flashforge.com/blogs/news/service-upgrade-notification |title=Service Upgrade Notification |website=Flashforge |access-date=May 22, 2026}}</ref><ref name="ff-meshy">{{Cite web |url=https://www.flashforge.com/blogs/news/flashforge-meshy-ai |title=Flashforge × Meshy AI: From AI Ideas to Real Prints |date=2026-05-20 |website=Flashforge |access-date=May 22, 2026}}</ref> The same printers are the subject of a February 2026 class-action investigation by the Washington, D.C. consumer-protection firm Migliaccio & Rathod LLP over recurring heating, extruder, and auto-leveling failures.<ref name="classlaw-ff">{{Cite web |url=https://classlawdc.com/2026/02/25/flashforge-3d-printer-investigation/ |title=Flashforge 3D Printer Investigation |date=2026-02-25 |website=Migliaccio & Rathod LLP |access-date=May 22, 2026}}</ref>

== Consumer-impact summary ==

* '''Vendor lock-in via firmware update.''' The March 25, 2025 ''"Service Upgrade Notification"'' set hard version floors that retired the open networking pathways previously used by mainline OrcaSlicer and third-party tooling.<ref name="ff-service-notice" />
* '''In-app advertising.''' Flash Studio Desktop (the rebranded Orca-Flashforge) carries a banner promoting a $1 Meshy.ai membership offer inside its printer-management view.<ref name="ff-meshy" />
* '''Open-source license dispute.''' OrcaSlicer issue #5154 alleges FlashForge bundled the GPLv3-licensed OrcaSlicer fork with a restrictive commercial EULA prohibiting redistribution, modification, and reverse engineering.<ref name="orca-5154">{{Cite web |url=https://github.com/SoftFever/OrcaSlicer/issues/5154 |title=Flashforge is violating OrcaSlicer's GPLv3 license (Issue #5154) |date=2024-04-26 |website=GitHub: SoftFever/OrcaSlicer |access-date=May 22, 2026}}</ref>
* '''Class-action investigation.''' Migliaccio & Rathod LLP solicits Adventurer 5M & AD5X owners reporting nozzle heating failures, premature extruder breakage, and auto-leveling crashes that gouge the build plate.<ref name="classlaw-ff" />
* '''Telemetry without disclosed source.''' Orca-Flashforge issue #26 documents the desktop slicer making outbound connections to roughly twenty hostnames (including a competitor API and the NetEase IM library) that do not appear in the company's published source repository.<ref name="orca-ff-26">{{Cite web |url=https://github.com/FlashForge/Orca-Flashforge/issues/26 |title=Provide actual codebase which exposes all connections (Issue #26) |date=2025-11-15 |website=GitHub: FlashForge/Orca-Flashforge |access-date=May 22, 2026}}</ref>

== Background ==

FlashForge was incorporated in 2011 as Zhejiang Flashforge 3D Technology Co., Ltd.<ref name="ff-about" /> The company manufactures desktop FDM 3D printers (the Adventurer, Creator, Guider, and Inventor lines), resin and DLP printers (the Foto and Hunter lines), and industrial wax 3D printers (the WaxJet series).<ref name="ff-about" /> Its budget sub-brand '''Voxelab''' targets entry-level consumers, and a U.S. distribution arm operates under the name Flashforge USA.<ref name="ff-usa">{{Cite web |url=https://www.flashforge-usa.com/ |title=Flashforge USA |website=Flashforge USA |access-date=May 22, 2026}}</ref>

FlashForge originally shipped open network protocols on its FDM printers. An August 15, 2024 FlashForge blog post described Orca-Flashforge (a fork of SoftFever's open-source OrcaSlicer) as the recommended slicer for the Adventurer 5M series & Guider 3 Ultra,<ref name="ff-orca-guide" /> & Adventurer 5M firmware 2.6.5 (April 11, 2024) added ''"Support Orca-Flashforge connection"'' & a LAN mode.<ref name="ff-orca-guide">{{Cite web |url=https://www.flashforge.com/blogs/news/orca-and-orca-flashforge-a-comprehensive-guide |title=Orca and Orca-Flashforge: A Comprehensive Guide |date=2024-08-15 |website=Flashforge |access-date=May 22, 2026}}</ref><ref name="ff-5m-changelog">{{Cite web |url=https://www.flashforge.com/a/docs/adventurer-5m-series/adventurer-5m-series-firmware-update-log |title=Adventurer 5M Series Firmware Update Log |website=Flashforge |access-date=May 22, 2026}}</ref> The 2025 service migration replaced that posture with a closed, cloud-mediated architecture.

== Incidents ==

=== Flash Studio mandatory slicer advertising and third-party slicer lockout ===

{{Main|FlashForge Flash Studio mandatory slicer advertising and third-party slicer lockout}}

In early 2025 FlashForge published a ''"Service Upgrade Notification"'' announcing the retirement of its legacy server services on March 26, 2025 & requiring Adventurer 5M, Adventurer 5M Pro, & Guider 3 Ultra owners to update firmware to v3.1.0 or later & the Orca-Flashforge desktop slicer to v1.3.0 or later.<ref name="ff-service-notice" /> Orca-Flashforge was subsequently rebranded to Flash Studio Desktop, & on May 20, 2026 the company announced a Meshy.ai partnership that embedded a banner promoting a $1 Meshy membership offer inside the slicer's printer-management view.<ref name="ff-meshy" /> Owners running mainline OrcaSlicer 2.3.0 against post-migration firmware report ''"ERR_CONNECTION_REFUSED"'' errors on the device tab (OrcaSlicer issue #10260, July 28, 2025).<ref name="orca-10260">{{Cite web |url=https://github.com/OrcaSlicer/OrcaSlicer/issues/10260 |title=Device Section of Orca Slicer not working with Flashforge AD5M (Issue #10260) |date=2025-07-28 |website=GitHub: OrcaSlicer/OrcaSlicer |access-date=May 22, 2026}}</ref> Two community Klipper-based firmware mods (''xblax/flashforge_ad5m_klipper_mod'' & ''DrA1ex/ff5m'') restore open networking at the cost of voiding the manufacturer warranty.<ref name="klipper-xblax">{{Cite web |url=https://github.com/xblax/flashforge_ad5m_klipper_mod |title=Unofficial mod for Flashforge Adventurer 5M (Pro) 3D printers to run Moonraker, custom Klipper, Mainsail and Fluidd |website=GitHub: xblax/flashforge_ad5m_klipper_mod |access-date=May 22, 2026}}</ref>

=== Flashforge threatens to report customers for printing firearms or weapon components ===

In late 2025, Flashforge posted an infographic titled '''NO to weaponized 3D printing''' on Facebook, threatening to report customers printing firearms or weapon components to "authorities"<ref>https://www.reddit.com/r/3Dprinting/comments/1owqkqs/flashforge_telling_and_threatening_their_users/</ref><ref>https://www.reddit.com/r/Firearms/comments/1oxtrni/3d_printer_manufacturer_flashforge_openly/</ref>, implying that it has the capability to view users prints, or to mitigate liability.

The Facebook post has been reproduced below:
<div style="width: 30vw; color: gray;">
We build tools for creation--never for harm. 
Flashforge stands for safe, responsible 3D printing.
</div>
<div style="width: 30vw; color: gray; text-align: center">
NO to weaponized 3D printing

Flashforge does not support or condone the 3D printing of firearms or weapon components. (Subject to the Flashforge user agreement.)

Flashforge prohibits using our products and services to create firearms or weapon components. Violations may lead to account termination and refer- ral to authorities.
</div>

Privately made firearms are legal in the United States, at least federally.<ref>https://www.atf.gov/firearms/privately-made-firearms</ref>

The Facebook post was later retracted.{{Citation needed}}

=== Adventurer 5M & AD5X hardware-defect class-action investigation ===

On February 25, 2026 the Washington, D.C. consumer-protection law firm Migliaccio & Rathod LLP opened a class-action investigation soliciting Adventurer 5M & AD5X owners whose printers exhibit recurring failures.<ref name="classlaw-ff" /> The firm's intake page lists specific defect patterns: nozzles that fail to heat or hold temperature, printers that stop working within days or months of purchase, premature extruder & filament-feeder breakage, repeated jams & feeding errors, & auto-leveling failures resulting in nozzle scraping & poor first-layer adhesion.<ref name="classlaw-ff" /> The firm solicits affected owners through an online intake form.<ref name="classlaw-ff" /> Tom's Hardware reviewer Denise Bertacchi, in a published October 12, 2025 AD5X review, separately reported that the bundled Orca-Flashforge slicer ''"is perhaps the least stable version"'' of OrcaSlicer she had used, crashing about every third print.<ref name="tomshardware-ad5x">{{Cite web |url=https://www.tomshardware.com/3d-printing/flashforge-ad5x-review |title=Flashforge AD5X review: An affordable option for fast color 3D printing |last=Bertacchi |first=Denise |date=2025-10-12 |website=Tom's Hardware |access-date=May 22, 2026}}</ref> The investigation is open as of May 2026; no class certification or settlement has been announced.<ref name="classlaw-ff" />

== Products ==

FlashForge sells three families of additive-manufacturing hardware plus the proprietary Flash Studio software suite.

* '''Adventurer 5M series.''' CoreXY FDM printers including the Adventurer 5M (open frame) & Adventurer 5M Pro (enclosed with HEPA filtration). Affected by the March 2025 service migration & the Migliaccio & Rathod class-action investigation.<ref name="ff-service-notice" /><ref name="classlaw-ff" />
* '''Adventurer 5X (AD5X).''' Multi-color CoreXY FDM printer with an Intelligent Filament System. Affected by the same firmware lockout & class-action investigation, & the subject of the October 2025 Tom's Hardware stability review.<ref name="tomshardware-ad5x" /><ref name="classlaw-ff" />
* '''Creator 5 / Creator 5 Pro.''' Four-toolhead changing systems heavily promoted in the Meshy.ai partnership materials.<ref name="ff-meshy" /><ref name="prnewswire-meshy">{{Cite web |url=https://www.prnewswire.com/news-releases/flashforge-and-meshy-partner-to-bring-ai-image-to-3d-directly-into-consumer-multi-color-printing-302778460.html |title=FlashForge and Meshy Partner to Bring AI Image-to-3D Directly Into Consumer Multi-Color Printing |date=2026-05-21 |website=PR Newswire |access-date=May 22, 2026}}</ref>
* '''Guider 3 Ultra.''' Enterprise-tier FDM printer also covered by the March 2025 service migration's mandatory firmware floor.<ref name="ff-service-notice" />
* '''Software.''' Flash Studio Desktop (formerly Orca-Flashforge; a GPLv3 fork of SoftFever's OrcaSlicer), Flash Studio Mobile (formerly Flash Maker), & the legacy FlashPrint slicer.<ref name="ff-meshy" /><ref name="orca-5154" />
* '''Legacy & adjacent lines.''' Creator (2011-), Creator Pro, Creator 3, Dreamer, Finder, Adventurer 3 & 4, Inventor, Guider II, Foto 8.9 LCD resin, Hunter S DLP, & the industrial WaxJet 400/510/530 wax-pattern printers.<ref name="ff-about" />

The budget sub-brand Voxelab markets entry-level FDM & resin printers separately from the main FlashForge catalogue.<ref name="ff-about" />

== See also ==

* [[FlashForge Flash Studio mandatory slicer advertising and third-party slicer lockout]]
* [[Bambu Lab Authorization Control System]]

== References ==

<references />

[[Category:Companies]]
[[Category:FlashForge]]
[[Category:3D printing]]
[[Category:Chinese companies]]

Flashforge

2026-06-07T01:29:23Z

Wownyc: /* Flashforge threatens to report customers for printing firearms or weapon components */ oop draft

{{CompanyCargo
|Description=Forces Adventurer 5M/AD5X owners onto proprietary Flash Studio slicer with banner ads; class action filed over heating & extruder defects
|Founded=2011
|Industry=3D printing,Consumer electronics
|Logo=FlashForge.png
|ParentCompany=
|CompanyAlias=Zhejiang Flashforge 3D Technology Co. Ltd.,Flashforge
|Type=Private
|Website=https://www.flashforge.com/
}}

'''FlashForge''' (legal name: '''Zhejiang Flashforge 3D Technology Co., Ltd.''') is a Chinese desktop & industrial 3D printer manufacturer founded in 2011.<ref name="ff-about">{{Cite web |url=https://www.flashforge.com/pages/about-us |title=About Us - Flashforge |website=Flashforge |access-date=May 22, 2026}}</ref> Between February 2025 & May 2026 FlashForge progressively closed the network architecture of its Adventurer 5M & AD5X consumer 3D printers, pushing owners towards a proprietary slicer carrying a banner advertisement for a $1 Meshy.ai membership offer, and which broke third-party slicer compatibility documented in OrcaSlicer GitHub issues #5154, #10112, #10260, & #11658.<ref name="ff-service-notice">{{Cite web |url=https://www.flashforge.com/blogs/news/service-upgrade-notification |title=Service Upgrade Notification |website=Flashforge |access-date=May 22, 2026}}</ref><ref name="ff-meshy">{{Cite web |url=https://www.flashforge.com/blogs/news/flashforge-meshy-ai |title=Flashforge × Meshy AI: From AI Ideas to Real Prints |date=2026-05-20 |website=Flashforge |access-date=May 22, 2026}}</ref> The same printers are the subject of a February 2026 class-action investigation by the Washington, D.C. consumer-protection firm Migliaccio & Rathod LLP over recurring heating, extruder, and auto-leveling failures.<ref name="classlaw-ff">{{Cite web |url=https://classlawdc.com/2026/02/25/flashforge-3d-printer-investigation/ |title=Flashforge 3D Printer Investigation |date=2026-02-25 |website=Migliaccio & Rathod LLP |access-date=May 22, 2026}}</ref>

== Consumer-impact summary ==

* '''Vendor lock-in via firmware update.''' The March 25, 2025 ''"Service Upgrade Notification"'' set hard version floors that retired the open networking pathways previously used by mainline OrcaSlicer and third-party tooling.<ref name="ff-service-notice" />
* '''In-app advertising.''' Flash Studio Desktop (the rebranded Orca-Flashforge) carries a banner promoting a $1 Meshy.ai membership offer inside its printer-management view.<ref name="ff-meshy" />
* '''Open-source license dispute.''' OrcaSlicer issue #5154 alleges FlashForge bundled the GPLv3-licensed OrcaSlicer fork with a restrictive commercial EULA prohibiting redistribution, modification, and reverse engineering.<ref name="orca-5154">{{Cite web |url=https://github.com/SoftFever/OrcaSlicer/issues/5154 |title=Flashforge is violating OrcaSlicer's GPLv3 license (Issue #5154) |date=2024-04-26 |website=GitHub: SoftFever/OrcaSlicer |access-date=May 22, 2026}}</ref>
* '''Class-action investigation.''' Migliaccio & Rathod LLP solicits Adventurer 5M & AD5X owners reporting nozzle heating failures, premature extruder breakage, and auto-leveling crashes that gouge the build plate.<ref name="classlaw-ff" />
* '''Telemetry without disclosed source.''' Orca-Flashforge issue #26 documents the desktop slicer making outbound connections to roughly twenty hostnames (including a competitor API and the NetEase IM library) that do not appear in the company's published source repository.<ref name="orca-ff-26">{{Cite web |url=https://github.com/FlashForge/Orca-Flashforge/issues/26 |title=Provide actual codebase which exposes all connections (Issue #26) |date=2025-11-15 |website=GitHub: FlashForge/Orca-Flashforge |access-date=May 22, 2026}}</ref>

== Background ==

FlashForge was incorporated in 2011 as Zhejiang Flashforge 3D Technology Co., Ltd.<ref name="ff-about" /> The company manufactures desktop FDM 3D printers (the Adventurer, Creator, Guider, and Inventor lines), resin and DLP printers (the Foto and Hunter lines), and industrial wax 3D printers (the WaxJet series).<ref name="ff-about" /> Its budget sub-brand '''Voxelab''' targets entry-level consumers, and a U.S. distribution arm operates under the name Flashforge USA.<ref name="ff-usa">{{Cite web |url=https://www.flashforge-usa.com/ |title=Flashforge USA |website=Flashforge USA |access-date=May 22, 2026}}</ref>

FlashForge originally shipped open network protocols on its FDM printers. An August 15, 2024 FlashForge blog post described Orca-Flashforge (a fork of SoftFever's open-source OrcaSlicer) as the recommended slicer for the Adventurer 5M series & Guider 3 Ultra,<ref name="ff-orca-guide" /> & Adventurer 5M firmware 2.6.5 (April 11, 2024) added ''"Support Orca-Flashforge connection"'' & a LAN mode.<ref name="ff-orca-guide">{{Cite web |url=https://www.flashforge.com/blogs/news/orca-and-orca-flashforge-a-comprehensive-guide |title=Orca and Orca-Flashforge: A Comprehensive Guide |date=2024-08-15 |website=Flashforge |access-date=May 22, 2026}}</ref><ref name="ff-5m-changelog">{{Cite web |url=https://www.flashforge.com/a/docs/adventurer-5m-series/adventurer-5m-series-firmware-update-log |title=Adventurer 5M Series Firmware Update Log |website=Flashforge |access-date=May 22, 2026}}</ref> The 2025 service migration replaced that posture with a closed, cloud-mediated architecture.

== Incidents ==

=== Flash Studio mandatory slicer advertising and third-party slicer lockout ===

{{Main|FlashForge Flash Studio mandatory slicer advertising and third-party slicer lockout}}

In early 2025 FlashForge published a ''"Service Upgrade Notification"'' announcing the retirement of its legacy server services on March 26, 2025 & requiring Adventurer 5M, Adventurer 5M Pro, & Guider 3 Ultra owners to update firmware to v3.1.0 or later & the Orca-Flashforge desktop slicer to v1.3.0 or later.<ref name="ff-service-notice" /> Orca-Flashforge was subsequently rebranded to Flash Studio Desktop, & on May 20, 2026 the company announced a Meshy.ai partnership that embedded a banner promoting a $1 Meshy membership offer inside the slicer's printer-management view.<ref name="ff-meshy" /> Owners running mainline OrcaSlicer 2.3.0 against post-migration firmware report ''"ERR_CONNECTION_REFUSED"'' errors on the device tab (OrcaSlicer issue #10260, July 28, 2025).<ref name="orca-10260">{{Cite web |url=https://github.com/OrcaSlicer/OrcaSlicer/issues/10260 |title=Device Section of Orca Slicer not working with Flashforge AD5M (Issue #10260) |date=2025-07-28 |website=GitHub: OrcaSlicer/OrcaSlicer |access-date=May 22, 2026}}</ref> Two community Klipper-based firmware mods (''xblax/flashforge_ad5m_klipper_mod'' & ''DrA1ex/ff5m'') restore open networking at the cost of voiding the manufacturer warranty.<ref name="klipper-xblax">{{Cite web |url=https://github.com/xblax/flashforge_ad5m_klipper_mod |title=Unofficial mod for Flashforge Adventurer 5M (Pro) 3D printers to run Moonraker, custom Klipper, Mainsail and Fluidd |website=GitHub: xblax/flashforge_ad5m_klipper_mod |access-date=May 22, 2026}}</ref>

=== Flashforge threatens to report customers for printing firearms or weapon components ===

In late 2025, Flashforge posted an infographic titled '''NO to weaponized 3D printing''' on Facebook, threatening to report customers printing firearms or weapon components to "authorities"<ref>https://www.reddit.com/r/3Dprinting/comments/1owqkqs/flashforge_telling_and_threatening_their_users/</ref><ref>https://www.reddit.com/r/Firearms/comments/1oxtrni/3d_printer_manufacturer_flashforge_openly/</ref>, implying that it has the capability to view users prints, or to mitigate liability.

The Facebook post has been reproduced below:
<div style="width: 30vw; color: gray; text-align: center">
We build tools for creation--never for harm. 
Flashforge stands for safe, responsible 3D printing.

NO to weaponized 3D printing

Flashforge does not support or condone the 3D printing of firearms or weapon components. (Subject to the Flashforge user agreement.)

Flashforge prohibits using our products and services to create firearms or weapon components. Violations may lead to account termination and refer- ral to authorities.
</div>

Privately made firearms are legal in the United States, at least federally.<ref>https://www.atf.gov/firearms/privately-made-firearms</ref>

The Facebook post was later retracted.{{Citation needed}}

=== Adventurer 5M & AD5X hardware-defect class-action investigation ===

On February 25, 2026 the Washington, D.C. consumer-protection law firm Migliaccio & Rathod LLP opened a class-action investigation soliciting Adventurer 5M & AD5X owners whose printers exhibit recurring failures.<ref name="classlaw-ff" /> The firm's intake page lists specific defect patterns: nozzles that fail to heat or hold temperature, printers that stop working within days or months of purchase, premature extruder & filament-feeder breakage, repeated jams & feeding errors, & auto-leveling failures resulting in nozzle scraping & poor first-layer adhesion.<ref name="classlaw-ff" /> The firm solicits affected owners through an online intake form.<ref name="classlaw-ff" /> Tom's Hardware reviewer Denise Bertacchi, in a published October 12, 2025 AD5X review, separately reported that the bundled Orca-Flashforge slicer ''"is perhaps the least stable version"'' of OrcaSlicer she had used, crashing about every third print.<ref name="tomshardware-ad5x">{{Cite web |url=https://www.tomshardware.com/3d-printing/flashforge-ad5x-review |title=Flashforge AD5X review: An affordable option for fast color 3D printing |last=Bertacchi |first=Denise |date=2025-10-12 |website=Tom's Hardware |access-date=May 22, 2026}}</ref> The investigation is open as of May 2026; no class certification or settlement has been announced.<ref name="classlaw-ff" />

== Products ==

FlashForge sells three families of additive-manufacturing hardware plus the proprietary Flash Studio software suite.

* '''Adventurer 5M series.''' CoreXY FDM printers including the Adventurer 5M (open frame) & Adventurer 5M Pro (enclosed with HEPA filtration). Affected by the March 2025 service migration & the Migliaccio & Rathod class-action investigation.<ref name="ff-service-notice" /><ref name="classlaw-ff" />
* '''Adventurer 5X (AD5X).''' Multi-color CoreXY FDM printer with an Intelligent Filament System. Affected by the same firmware lockout & class-action investigation, & the subject of the October 2025 Tom's Hardware stability review.<ref name="tomshardware-ad5x" /><ref name="classlaw-ff" />
* '''Creator 5 / Creator 5 Pro.''' Four-toolhead changing systems heavily promoted in the Meshy.ai partnership materials.<ref name="ff-meshy" /><ref name="prnewswire-meshy">{{Cite web |url=https://www.prnewswire.com/news-releases/flashforge-and-meshy-partner-to-bring-ai-image-to-3d-directly-into-consumer-multi-color-printing-302778460.html |title=FlashForge and Meshy Partner to Bring AI Image-to-3D Directly Into Consumer Multi-Color Printing |date=2026-05-21 |website=PR Newswire |access-date=May 22, 2026}}</ref>
* '''Guider 3 Ultra.''' Enterprise-tier FDM printer also covered by the March 2025 service migration's mandatory firmware floor.<ref name="ff-service-notice" />
* '''Software.''' Flash Studio Desktop (formerly Orca-Flashforge; a GPLv3 fork of SoftFever's OrcaSlicer), Flash Studio Mobile (formerly Flash Maker), & the legacy FlashPrint slicer.<ref name="ff-meshy" /><ref name="orca-5154" />
* '''Legacy & adjacent lines.''' Creator (2011-), Creator Pro, Creator 3, Dreamer, Finder, Adventurer 3 & 4, Inventor, Guider II, Foto 8.9 LCD resin, Hunter S DLP, & the industrial WaxJet 400/510/530 wax-pattern printers.<ref name="ff-about" />

The budget sub-brand Voxelab markets entry-level FDM & resin printers separately from the main FlashForge catalogue.<ref name="ff-about" />

== See also ==

* [[FlashForge Flash Studio mandatory slicer advertising and third-party slicer lockout]]
* [[Bambu Lab Authorization Control System]]

== References ==

<references />

[[Category:Companies]]
[[Category:FlashForge]]
[[Category:3D printing]]
[[Category:Chinese companies]]

Flashforge

2026-06-07T01:24:44Z

Wownyc: /* Incidents */ flashforge bad

{{CompanyCargo
|Description=Forces Adventurer 5M/AD5X owners onto proprietary Flash Studio slicer with banner ads; class action filed over heating & extruder defects
|Founded=2011
|Industry=3D printing,Consumer electronics
|Logo=FlashForge.png
|ParentCompany=
|CompanyAlias=Zhejiang Flashforge 3D Technology Co. Ltd.,Flashforge
|Type=Private
|Website=https://www.flashforge.com/
}}

'''FlashForge''' (legal name: '''Zhejiang Flashforge 3D Technology Co., Ltd.''') is a Chinese desktop & industrial 3D printer manufacturer founded in 2011.<ref name="ff-about">{{Cite web |url=https://www.flashforge.com/pages/about-us |title=About Us - Flashforge |website=Flashforge |access-date=May 22, 2026}}</ref> Between February 2025 & May 2026 FlashForge progressively closed the network architecture of its Adventurer 5M & AD5X consumer 3D printers, pushing owners towards a proprietary slicer carrying a banner advertisement for a $1 Meshy.ai membership offer, and which broke third-party slicer compatibility documented in OrcaSlicer GitHub issues #5154, #10112, #10260, & #11658.<ref name="ff-service-notice">{{Cite web |url=https://www.flashforge.com/blogs/news/service-upgrade-notification |title=Service Upgrade Notification |website=Flashforge |access-date=May 22, 2026}}</ref><ref name="ff-meshy">{{Cite web |url=https://www.flashforge.com/blogs/news/flashforge-meshy-ai |title=Flashforge × Meshy AI: From AI Ideas to Real Prints |date=2026-05-20 |website=Flashforge |access-date=May 22, 2026}}</ref> The same printers are the subject of a February 2026 class-action investigation by the Washington, D.C. consumer-protection firm Migliaccio & Rathod LLP over recurring heating, extruder, and auto-leveling failures.<ref name="classlaw-ff">{{Cite web |url=https://classlawdc.com/2026/02/25/flashforge-3d-printer-investigation/ |title=Flashforge 3D Printer Investigation |date=2026-02-25 |website=Migliaccio & Rathod LLP |access-date=May 22, 2026}}</ref>

== Consumer-impact summary ==

* '''Vendor lock-in via firmware update.''' The March 25, 2025 ''"Service Upgrade Notification"'' set hard version floors that retired the open networking pathways previously used by mainline OrcaSlicer and third-party tooling.<ref name="ff-service-notice" />
* '''In-app advertising.''' Flash Studio Desktop (the rebranded Orca-Flashforge) carries a banner promoting a $1 Meshy.ai membership offer inside its printer-management view.<ref name="ff-meshy" />
* '''Open-source license dispute.''' OrcaSlicer issue #5154 alleges FlashForge bundled the GPLv3-licensed OrcaSlicer fork with a restrictive commercial EULA prohibiting redistribution, modification, and reverse engineering.<ref name="orca-5154">{{Cite web |url=https://github.com/SoftFever/OrcaSlicer/issues/5154 |title=Flashforge is violating OrcaSlicer's GPLv3 license (Issue #5154) |date=2024-04-26 |website=GitHub: SoftFever/OrcaSlicer |access-date=May 22, 2026}}</ref>
* '''Class-action investigation.''' Migliaccio & Rathod LLP solicits Adventurer 5M & AD5X owners reporting nozzle heating failures, premature extruder breakage, and auto-leveling crashes that gouge the build plate.<ref name="classlaw-ff" />
* '''Telemetry without disclosed source.''' Orca-Flashforge issue #26 documents the desktop slicer making outbound connections to roughly twenty hostnames (including a competitor API and the NetEase IM library) that do not appear in the company's published source repository.<ref name="orca-ff-26">{{Cite web |url=https://github.com/FlashForge/Orca-Flashforge/issues/26 |title=Provide actual codebase which exposes all connections (Issue #26) |date=2025-11-15 |website=GitHub: FlashForge/Orca-Flashforge |access-date=May 22, 2026}}</ref>

== Background ==

FlashForge was incorporated in 2011 as Zhejiang Flashforge 3D Technology Co., Ltd.<ref name="ff-about" /> The company manufactures desktop FDM 3D printers (the Adventurer, Creator, Guider, and Inventor lines), resin and DLP printers (the Foto and Hunter lines), and industrial wax 3D printers (the WaxJet series).<ref name="ff-about" /> Its budget sub-brand '''Voxelab''' targets entry-level consumers, and a U.S. distribution arm operates under the name Flashforge USA.<ref name="ff-usa">{{Cite web |url=https://www.flashforge-usa.com/ |title=Flashforge USA |website=Flashforge USA |access-date=May 22, 2026}}</ref>

FlashForge originally shipped open network protocols on its FDM printers. An August 15, 2024 FlashForge blog post described Orca-Flashforge (a fork of SoftFever's open-source OrcaSlicer) as the recommended slicer for the Adventurer 5M series & Guider 3 Ultra,<ref name="ff-orca-guide" /> & Adventurer 5M firmware 2.6.5 (April 11, 2024) added ''"Support Orca-Flashforge connection"'' & a LAN mode.<ref name="ff-orca-guide">{{Cite web |url=https://www.flashforge.com/blogs/news/orca-and-orca-flashforge-a-comprehensive-guide |title=Orca and Orca-Flashforge: A Comprehensive Guide |date=2024-08-15 |website=Flashforge |access-date=May 22, 2026}}</ref><ref name="ff-5m-changelog">{{Cite web |url=https://www.flashforge.com/a/docs/adventurer-5m-series/adventurer-5m-series-firmware-update-log |title=Adventurer 5M Series Firmware Update Log |website=Flashforge |access-date=May 22, 2026}}</ref> The 2025 service migration replaced that posture with a closed, cloud-mediated architecture.

== Incidents ==

=== Flash Studio mandatory slicer advertising and third-party slicer lockout ===

{{Main|FlashForge Flash Studio mandatory slicer advertising and third-party slicer lockout}}

In early 2025 FlashForge published a ''"Service Upgrade Notification"'' announcing the retirement of its legacy server services on March 26, 2025 & requiring Adventurer 5M, Adventurer 5M Pro, & Guider 3 Ultra owners to update firmware to v3.1.0 or later & the Orca-Flashforge desktop slicer to v1.3.0 or later.<ref name="ff-service-notice" /> Orca-Flashforge was subsequently rebranded to Flash Studio Desktop, & on May 20, 2026 the company announced a Meshy.ai partnership that embedded a banner promoting a $1 Meshy membership offer inside the slicer's printer-management view.<ref name="ff-meshy" /> Owners running mainline OrcaSlicer 2.3.0 against post-migration firmware report ''"ERR_CONNECTION_REFUSED"'' errors on the device tab (OrcaSlicer issue #10260, July 28, 2025).<ref name="orca-10260">{{Cite web |url=https://github.com/OrcaSlicer/OrcaSlicer/issues/10260 |title=Device Section of Orca Slicer not working with Flashforge AD5M (Issue #10260) |date=2025-07-28 |website=GitHub: OrcaSlicer/OrcaSlicer |access-date=May 22, 2026}}</ref> Two community Klipper-based firmware mods (''xblax/flashforge_ad5m_klipper_mod'' & ''DrA1ex/ff5m'') restore open networking at the cost of voiding the manufacturer warranty.<ref name="klipper-xblax">{{Cite web |url=https://github.com/xblax/flashforge_ad5m_klipper_mod |title=Unofficial mod for Flashforge Adventurer 5M (Pro) 3D printers to run Moonraker, custom Klipper, Mainsail and Fluidd |website=GitHub: xblax/flashforge_ad5m_klipper_mod |access-date=May 22, 2026}}</ref>

=== Flashforge threatens to report customers for printing firearms or weapon components ===

In late 2025, Flashforge posted an infographic titled '''NO to weaponized 3D printing''' on Facebook, threatening to report customers printing firearms or weapon components to "authorities"<ref>https://www.reddit.com/r/3Dprinting/comments/1owqkqs/flashforge_telling_and_threatening_their_users/</ref><ref>https://www.reddit.com/r/Firearms/comments/1oxtrni/3d_printer_manufacturer_flashforge_openly/</ref>, implying that it has the capability to view users prints, or just to cover their ass.

<div style="width: 30vw; color: gray; text-align: center">
We build tools for creation--never for harm. 
Flashforge stands for safe, responsible 3D printing.

NO to weaponized 3D printing

Flashforge does not support or condone the 3D printing of firearms or weapon components. (Subject to the Flashforge user agreement.)

Flashforge prohibits using our products and services to create firearms or weapon components. Violations may lead to account termination and refer- ral to authorities.
</div>

Privately made firearms are legal in the United States, at least federally.<ref>https://www.atf.gov/firearms/privately-made-firearms</ref>

The Facebook post was later retracted.{{Citation needed}}

=== Adventurer 5M & AD5X hardware-defect class-action investigation ===

On February 25, 2026 the Washington, D.C. consumer-protection law firm Migliaccio & Rathod LLP opened a class-action investigation soliciting Adventurer 5M & AD5X owners whose printers exhibit recurring failures.<ref name="classlaw-ff" /> The firm's intake page lists specific defect patterns: nozzles that fail to heat or hold temperature, printers that stop working within days or months of purchase, premature extruder & filament-feeder breakage, repeated jams & feeding errors, & auto-leveling failures resulting in nozzle scraping & poor first-layer adhesion.<ref name="classlaw-ff" /> The firm solicits affected owners through an online intake form.<ref name="classlaw-ff" /> Tom's Hardware reviewer Denise Bertacchi, in a published October 12, 2025 AD5X review, separately reported that the bundled Orca-Flashforge slicer ''"is perhaps the least stable version"'' of OrcaSlicer she had used, crashing about every third print.<ref name="tomshardware-ad5x">{{Cite web |url=https://www.tomshardware.com/3d-printing/flashforge-ad5x-review |title=Flashforge AD5X review: An affordable option for fast color 3D printing |last=Bertacchi |first=Denise |date=2025-10-12 |website=Tom's Hardware |access-date=May 22, 2026}}</ref> The investigation is open as of May 2026; no class certification or settlement has been announced.<ref name="classlaw-ff" />

== Products ==

FlashForge sells three families of additive-manufacturing hardware plus the proprietary Flash Studio software suite.

* '''Adventurer 5M series.''' CoreXY FDM printers including the Adventurer 5M (open frame) & Adventurer 5M Pro (enclosed with HEPA filtration). Affected by the March 2025 service migration & the Migliaccio & Rathod class-action investigation.<ref name="ff-service-notice" /><ref name="classlaw-ff" />
* '''Adventurer 5X (AD5X).''' Multi-color CoreXY FDM printer with an Intelligent Filament System. Affected by the same firmware lockout & class-action investigation, & the subject of the October 2025 Tom's Hardware stability review.<ref name="tomshardware-ad5x" /><ref name="classlaw-ff" />
* '''Creator 5 / Creator 5 Pro.''' Four-toolhead changing systems heavily promoted in the Meshy.ai partnership materials.<ref name="ff-meshy" /><ref name="prnewswire-meshy">{{Cite web |url=https://www.prnewswire.com/news-releases/flashforge-and-meshy-partner-to-bring-ai-image-to-3d-directly-into-consumer-multi-color-printing-302778460.html |title=FlashForge and Meshy Partner to Bring AI Image-to-3D Directly Into Consumer Multi-Color Printing |date=2026-05-21 |website=PR Newswire |access-date=May 22, 2026}}</ref>
* '''Guider 3 Ultra.''' Enterprise-tier FDM printer also covered by the March 2025 service migration's mandatory firmware floor.<ref name="ff-service-notice" />
* '''Software.''' Flash Studio Desktop (formerly Orca-Flashforge; a GPLv3 fork of SoftFever's OrcaSlicer), Flash Studio Mobile (formerly Flash Maker), & the legacy FlashPrint slicer.<ref name="ff-meshy" /><ref name="orca-5154" />
* '''Legacy & adjacent lines.''' Creator (2011-), Creator Pro, Creator 3, Dreamer, Finder, Adventurer 3 & 4, Inventor, Guider II, Foto 8.9 LCD resin, Hunter S DLP, & the industrial WaxJet 400/510/530 wax-pattern printers.<ref name="ff-about" />

The budget sub-brand Voxelab markets entry-level FDM & resin printers separately from the main FlashForge catalogue.<ref name="ff-about" />

== See also ==

* [[FlashForge Flash Studio mandatory slicer advertising and third-party slicer lockout]]
* [[Bambu Lab Authorization Control System]]

== References ==

<references />

[[Category:Companies]]
[[Category:FlashForge]]
[[Category:3D printing]]
[[Category:Chinese companies]]

Cisco Systems, Inc.

2026-06-07T01:02:41Z

Wownyc: /* Cisco Meraki */

{{Cleanup}}
{{CompanyCargo
|Description=American tech company known for manufacturing networking software and hardware.
|Founded=December 10, 1984
|Industry=Computing, Information Technology
|Logo=Cisco logo blue 2016.png
|ParentCompany=
|Type=Public
|Website=https://www.cisco.com/
}}
'''[[wikipedia:Cisco|Cisco Systems, Inc.]]''' is an American multinational corporation that develops, manufactures, and sells networking hardware, software, telecommunications equipment and other high-technology services and products.<ref>{{Cite web |date=2012 |title=FORM 10-K |url=https://pdf.secdatabase.com/419/0001193125-12-388590.pdf |url-status=live |access-date=9 Apr 2025 |archive-url=http://web.archive.org/web/20250708182452/http://pdf.secdatabase.com/419/0001193125-12-388590.pdf |archive-date=8 Jul 2025}}</ref>

Cisco's founders were crucial to many of modern day implementations and protocols of Local Area Network systems we have today.

==Consumer impact summary==

===Company Issues===

====Business model====

=====Cisco Meraki=====
{{Main|Cisco Meraki}}

Meraki is a cloud managed IT infrastructure division of Cisco acquired in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points and security cameras all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

All Cisco Meraki devices require paid licensing to work and are very strict if this becomes out of compliance. Failure to obtain proper licensing will not only remove equipment configuration access in the portal, it will cease all internet traffic from otherwise operational devices.

===== "What happens when I reach my co-termination date? =====

Immediately after reaching your co-termination date, you will receive a 30-day grace period ... If you chose not to renew before the end of the 30-day grace period, the organization will be "shut down"(License Problem - Out of Compliance). You will no longer be able to manage your devices via the Meraki cloud and your Meraki network devices will cease to function. This means that you will no longer be able to configure or make changes to your Meraki network equipment, and your Meraki network products will no longer allow traffic to pass to the Internet."<ref>{{Cite web |date=16 Jan 2025 |title=Meraki Licensing FAQs |url=https://documentation.meraki.com/General_Administration/Licensing/Meraki_Licensing_FAQs |url-status=live |access-date=9 Apr 2025 |website=Meraki |archive-url=http://web.archive.org/web/20250823014551/https://documentation.meraki.com/General_Administration/Licensing/Meraki_Licensing_FAQs |archive-date=23 Aug 2025}}</ref>

====Complicit in implementing state-operated internet censorship in the People's Republic of China====
According to internal PowerPoint presentations from 2002 that surfaced online, Cisco systems knowingly supplied hardware used in China's ''Golden Shield'' project, informally known as The Great Firewall of China. This is the infrastructure used by the CCP to heavily censor the internet in China for its citizens and to block access to independent information.<ref>{{Cite web |last=Bort |first=Julie |date=2011-05-23 |title=Cisco sued over its alleged part in Great Chinese Firewall scandal |url=https://www.networkworld.com/article/753194/cisco-subnet-cisco-sued-over-its-alleged-part-in-great-chinese-firewall-scandal.html |access-date=2025-06-06 |website=Networkworld |url-status=live |archive-url=http://web.archive.org/web/20250820125115/https://www.networkworld.com/article/753194/cisco-subnet-cisco-sued-over-its-alleged-part-in-great-chinese-firewall-scandal.html |archive-date=20 Aug 2025}}</ref><ref>{{Cite web |last=Broache |first=Anne |date=2008-05-20 |title=Senators weigh new laws over China online censorship |url=https://news.cnet.com/8301-10784_3-9948331-7.html |url-status=dead |archive-url=https://web.archive.org/web/20080907214313/https://news.cnet.com/8301-10784_3-9948331-7.html |archive-date=2008-09-07}}</ref>

====Removing access to critical downloads for products that are end-of-support====
[[File:Cisco Security removes everything for discontinued products.png|thumb|Cisco's Retired Products page with a note explaining that they purposely remove documentation, downloads and product pages from the Cisco.com website "for security purposes"]]
Cisco removes all downloads for products that are past their end-of-support date, making it impossible to obtain software or firmware from official sources for your Cisco product. Cisco claims "'''Note:''' For security purposes, upon retirement of a product, Cisco Systems purposely removes documentation, downloads, and product pages from the Cisco.com website, though you may be able to obtain peer support in the Cisco Community."<ref>{{Cite web |date=2026-02-25 |title=Retired Products |url=https://www.cisco.com/c/en/us/support/security/retired.html |url-status=live |archive-url=https://web.archive.org/web/20260222210213/https://www.cisco.com/c/en/us/support/security/retired.html |archive-date=2026-02-22 |access-date=2026-02-25 |website=Cisco Product Support}}</ref> This is considered to be [[security through obscurity]]. If you, a consumer, have obtained obsolete Cisco hardware and wish to utilize it in a working environment, Cisco has deliberately made it harder to update your device to shield against security issues, or add features.

====Requiring a service contract to download firmware for products that are in-support====
[[File:Cisco forcing service contract for file access.png|thumb|A Cisco download page showing the text "'''Log In and Service Contract Required".''']]
Some Cisco products such as the [https://www.cisco.com/c/en/us/support/routers/1000-series-integrated-services-routers-isr/series.html Cisco ISR 1000 series] require an active service contract from Cisco to download any files such as firmware, software, patches, etc. This makes updating devices to their latest respective versions increasingly harder, as you are [[Forced account|required to sign in]] to an account and pay a subscription fee just to update components of the device that you already own. "To Download this software, you must have a valid service contract associated to your Cisco.com profile"<ref>{{Cite web |date=2026-02-25 |title=Cisco 1000 Series Integrated Services Routers download page showing "Service Contract Required" |url=https://www.cisco.com/c/en/us/support/routers/1000-series-integrated-services-routers-isr/series.html#~tab-downloads |url-status=live |archive-url=https://web.archive.org/web/20250831232702/https://www.cisco.com/c/en/us/support/routers/1000-series-integrated-services-routers-isr/series.html#~tab-downloads |archive-date=2025-08-31 |access-date=2026-02-25 |website=Cisco Product Support}}</ref>

====Withholding bug details from customers without a service contract====
Cisco hides bug details, most importantly the resolution/workaround of a bug from non-paying customers. You are required to log into a Cisco account to view bug details, and even then you are only permitted to view 200 bugs a month without paying for a service contract.<ref>{{Cite web |date=2026-02-25 |title=Cisco Bug Search Tool |url=https://bst.cisco.com/quickview/bug/CSCvu61065 |url-status=live |archive-url=https://web.archive.org/web/20260225021043/https://bst.cisco.com/quickview/bug/CSCvu61065 |archive-date=2026-02-25 |access-date=2026-02-25}}</ref>

"Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract."

====Requires employees to sign perpetual forced arbitration agreements when hired, preventing current or former employees from ever suing the company.{{Citation needed}}====

==References==
<references />
[[Category:{{PAGENAME}}]]
[[Category:Articles in need of additional work]]

Device bricking

2026-06-07T00:59:43Z

Wownyc:

{{StubNotice}}

A "[https://foundershield.com/insurance-terms/definition/bricking/#:~:text=Bricking%20is%20a%20term%20that,which%20renders%20the%20device%20useless. Bricked]" device is a device which has had its main functions rendered unusable, such a device is commonly refereed to as a brick. Companies reserve the right to remotely brick a consumers device if they attempt to do anything that [https://www.ign.com/articles/nintendo-revises-user-agreement-and-if-you-break-it-nintendo-reserves-the-right-to-brick-your-switch#:~:text=You%20acknowledge%20that%20if%20you%20fail%20to%20comply%20with%20the%20foregoing%20restrictions%20Nintendo%20may%20render%20the%20Nintendo%20Account%20Services%20and/or%20the%20applicable%20Nintendo%20device%20permanently%20unusable%20in%20whole%20or%20in%20part.%22 goes against the terms of service the company sets] for their devices. A recent example of this can be seen from the release of the Switch 2 from [[Nintendo]].

A company may justify "bricking" a consumer's device for "safety concerns". With intent to discourage "[https://www.techopedia.com/definition/10649/homebrew Homebrewed]" devices (devices with unofficial, third-party or user-created modifications) from being created and to try preventing piracy and hacking. Usually with financial incentives.

Device bricking occurs commonly as a result of [[Planned obsolescence]], where a company's goal is to force the consumer to buy new and replace the old product, now rendered unusable.

==Recent cases of Device bricking==
{| class="wikitable"
|+
!Time of incident
!Company name
!Reason
!Effects
!Details
|-
|June 2025 - Ongoing
|Nintendo
|EULA violation
|All games not fully downloaded prior rendered unplayable<ref>{{Cite web |last= |first= |date=2025-07-27 |title=What does a banned Switch 2 ACTUALLY mean? |url=https://youtu.be/MqFY3rICDWs?si=T3lLrbrbUH7CUT39 |url-status=live |access-date=2025-08-20 |website=YouTube |archive-url=https://preservetube.com/watch?v=MqFY3rICDWs |archive-date=16 Feb 2026}}</ref>, online features disabled
|In a May 2025 policy update, Nintendo stated they may ''"render the Nintendo Account Services and/or the applicable Nintendo device permanently unusable in whole or in part."''<ref>{{Cite web |date=2025-08-20 |title=Nintendo Account User Agreement |url=https://accounts.nintendo.com/term/eula/US?lang=en-US |url-status=live |archive-url=https://web.archive.org/web/20250513142857/https://accounts.nintendo.com/term/eula/US?lang=en-US |archive-date=2025-05-13 |access-date=2025-08-20 |website=Nintendo Official Site}}</ref>
|-
|
|
|
|
|
|-
|
|
|
|
|
|}
<references />

Cisco Meraki

2026-06-07T00:54:44Z

Wownyc: parent company in infobox pls thx

{{StubNotice}}
{{Incomplete}}

{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by [[Cisco Systems, Inc.|Cisco]] in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==

Since ~2018, hardware has been locked down with SecureBoot. <ref>https://forum.openwrt.org/t/cisco-meraki-mx68w/134895</ref><ref>https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881</ref> Hardware before 2018, or with SecureBoot exploits may be reflashable to OpenWRT.<ref name="watchmysys" /><ref>https://openwrt.org/toh/meraki/start</ref>

The company was previously friendly to open-source.<ref name="watchmysys">https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/</ref><ref name="only_took_four_months">https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4</ref><ref>https://forum.archive.openwrt.org/viewtopic.php?id=63838</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5</ref><ref name="mr46">https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64</ref> and/or releases source code that doesn't build.<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60</ref><ref name="mr46" />

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>https://github.com/riptidewave93/LEDE-MR33/issues/13</ref>

===User freedom===

===User privacy===

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx60
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx64
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/support-for-meraki-mx85/207538
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr52
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr18
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |https://openwrt.org/toh/meraki/mr34
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr42
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 https://github.com/halmartin/meraki-builder/issues/11
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |https://github.com/halmartin/meraki-builder/issues/23
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other Products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{reflist}}

[[Category:{{PAGENAME}}]]

Cisco Meraki

2026-06-07T00:51:44Z

Wownyc: replace excerpt

{{StubNotice}}
{{Incomplete}}

{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a cloud managed IT infrastructure company. It was acquired by Cisco in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points, and security cameras, all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

==Consumer impact summary==

Since ~2018, hardware has been locked down with SecureBoot. <ref>https://forum.openwrt.org/t/cisco-meraki-mx68w/134895</ref><ref>https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881</ref> Hardware before 2018, or with SecureBoot exploits may be reflashable to OpenWRT.<ref name="watchmysys" /><ref>https://openwrt.org/toh/meraki/start</ref>

The company was previously friendly to open-source.<ref name="watchmysys">https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/</ref><ref name="only_took_four_months">https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4</ref><ref>https://forum.archive.openwrt.org/viewtopic.php?id=63838</ref>

Its software stack contains open source (GPL) code, but the company delays releasing source code,<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5</ref><ref name="mr46">https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64</ref> and/or releases source code that doesn't build.<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60</ref><ref name="mr46" />

Devices without active licensing, or devices that do not support third party firmware, become e-waste.

Some models may brick if tampered with.<ref>https://github.com/riptidewave93/LEDE-MR33/issues/13</ref>

===User freedom===

===User privacy===

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx60
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx64
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/support-for-meraki-mx85/207538
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr52
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr18
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |https://openwrt.org/toh/meraki/mr34
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr42
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 https://github.com/halmartin/meraki-builder/issues/11
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |https://github.com/halmartin/meraki-builder/issues/23
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other Products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{reflist}}

[[Category:{{PAGENAME}}]]

Cisco Meraki

2026-06-06T18:40:14Z

Wownyc: /* MS Series */ add ms390

{{StubNotice}}
{{Incomplete}}

{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=Cisco meraki.webp
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

{{Excerpt|Cisco_Systems,_Inc.#Cisco_Meraki}}

Company was previously friendly to open-source.<ref name="watchmysys">https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/</ref><ref name="only_took_four_months">https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4</ref><ref>https://forum.archive.openwrt.org/viewtopic.php?id=63838</ref>

==Consumer impact summary==
Locked down hardware (SecureBoot) since ~2018.<ref>https://forum.openwrt.org/t/cisco-meraki-mx68w/134895</ref><ref>https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881</ref> Hardware before 2018, or with SecureBoot exploits may be reflashable to OpenWRT.<ref name="watchmysys" /><ref>https://openwrt.org/toh/meraki/start</ref>

Built on open source, but delays releasing source code,<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5</ref><ref name="mr46">https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64</ref> and/or releases source code that doesn't build.<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60</ref><ref name="mr46" />

Creates tons of e-waste (e.g, on [[eBay]]).

Some models may brick if tampered with.<ref>https://github.com/riptidewave93/LEDE-MR33/issues/13</ref>

===User freedom===

===User privacy===

===Business model===
Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx60
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx64
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/support-for-meraki-mx85/207538
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr52
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr18
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |https://openwrt.org/toh/meraki/mr34
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr42
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 https://github.com/halmartin/meraki-builder/issues/11
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |https://github.com/halmartin/meraki-builder/issues/23
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |[[Meraki MS390|MS390]]
| align="left" |
| align="right" |
| align="left" |
| align="left" |
| align="left" |
|}

===Other Products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{reflist}}

[[Category:{{PAGENAME}}]]

Cisco Meraki

2026-06-05T18:55:54Z

Wownyc: use excerpt from cisco page. or should it be the other way around?

{{StubNotice}}
{{Incomplete}}

{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

{{Excerpt|Cisco_Systems,_Inc.#Cisco_Meraki}}

Company was previously friendly to open-source.<ref name="watchmysys">https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/</ref><ref name="only_took_four_months">https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4</ref><ref>https://forum.archive.openwrt.org/viewtopic.php?id=63838</ref>

==Consumer-impact summary==

Locked down hardware (SecureBoot) since ~2018.<ref>https://forum.openwrt.org/t/cisco-meraki-mx68w/134895</ref><ref>https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881</ref> Hardware before 2018, or with SecureBoot exploits may be reflashable to OpenWRT.<ref name="watchmysys" /><ref>https://openwrt.org/toh/meraki/start</ref>

Built on open source, but delays releasing source code<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5</ref><ref name="mr46">https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64</ref>, and/or releases source code that doesn't build<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60</ref><ref name="mr46" />.

Creates tons of e-waste (e.g, on eBay).

Some models may brick if tampered with.<ref>https://github.com/riptidewave93/LEDE-MR33/issues/13</ref>

===User freedom===

===User privacy===

===Business model===

Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx60
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx64
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/support-for-meraki-mx85/207538
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr52
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr18
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |https://openwrt.org/toh/meraki/mr34
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr42
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 https://github.com/halmartin/meraki-builder/issues/11
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |https://github.com/halmartin/meraki-builder/issues/23
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|}

===Other Products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{reflist}}

[[Category:{{PAGENAME}}]]

Cisco Systems, Inc.

2026-06-05T18:53:44Z

Wownyc: /* Cisco Meraki */ link

{{Cleanup}}
{{CompanyCargo
|Description=American tech company known for manufacturing networking software and hardware.
|Founded=December 10, 1984
|Industry=Computing, Information Technology
|Logo=Cisco logo blue 2016.png
|ParentCompany=
|Type=Public
|Website=https://www.cisco.com/
}}
'''[[wikipedia:Cisco|Cisco Systems, Inc.]]''' is an American multinational corporation that develops, manufactures, and sells networking hardware, software, telecommunications equipment and other high-technology services and products.<ref>{{Cite web |date=2012 |title=FORM 10-K |url=https://pdf.secdatabase.com/419/0001193125-12-388590.pdf |url-status=live |access-date=9 Apr 2025 |archive-url=http://web.archive.org/web/20250708182452/http://pdf.secdatabase.com/419/0001193125-12-388590.pdf |archive-date=8 Jul 2025}}</ref>

Cisco's founders were crucial to many of modern day implementations and protocols of Local Area Network systems we have today.

==Consumer impact summary==

===Company Issues===

====Business model====

=====Cisco Meraki=====
{{Main|Cisco Meraki}}

Meraki is a cloud managed IT infrastructure division of Cisco acquired in 2012. Cisco Meraki devices include network firewalls, switching, wireless access points and security cameras all managed from their online web portal.<ref>{{Cite web |last=Constine |first=Josh |date=18 Nov 2012 |title=Cisco Acquires Enterprise Wi-Fi Startup Meraki For $1.2 Billion In Cash |url=https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |url-status=live |access-date=9 Apr 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20250709084717/https://techcrunch.com/2012/11/18/cisco-acquires-enterprise-wi-fi-startup-meraki-for-1-2-billion-in-cash/ |archive-date=9 Jul 2025}}</ref>

All Cisco Meraki devices require paid licensing to work and are very strict if this becomes out of compliance. Failure to obtain proper licensing will not only remove your access from configuring your equipment in the portal, it will cease all internet traffic from moving on previously working devices.

"What happens when I reach my co-termination date?

Immediately after reaching your co-termination date, you will receive a 30-day grace period ... If you chose not to renew before the end of the 30-day grace period, the organization will be "shut down"(License Problem - Out of Compliance). You will no longer be able to manage your devices via the Meraki cloud and your Meraki network devices will cease to function. This means that you will no longer be able to configure or make changes to your Meraki network equipment, and your Meraki network products will no longer allow traffic to pass to the Internet."<ref>{{Cite web |date=16 Jan 2025 |title=Meraki Licensing FAQs |url=https://documentation.meraki.com/General_Administration/Licensing/Meraki_Licensing_FAQs |url-status=live |access-date=9 Apr 2025 |website=Meraki |archive-url=http://web.archive.org/web/20250823014551/https://documentation.meraki.com/General_Administration/Licensing/Meraki_Licensing_FAQs |archive-date=23 Aug 2025}}</ref>

====Complicit in implementing state-operated internet censorship in the People's Republic of China====
According to internal PowerPoint presentations from 2002 that surfaced online, Cisco systems knowingly supplied hardware used in China's ''Golden Shield'' project, informally known as The Great Firewall of China. This is the infrastructure used by the CCP to heavily censor the internet in China for its citizens and to block access to independent information.<ref>{{Cite web |last=Bort |first=Julie |date=2011-05-23 |title=Cisco sued over its alleged part in Great Chinese Firewall scandal |url=https://www.networkworld.com/article/753194/cisco-subnet-cisco-sued-over-its-alleged-part-in-great-chinese-firewall-scandal.html |access-date=2025-06-06 |website=Networkworld |url-status=live |archive-url=http://web.archive.org/web/20250820125115/https://www.networkworld.com/article/753194/cisco-subnet-cisco-sued-over-its-alleged-part-in-great-chinese-firewall-scandal.html |archive-date=20 Aug 2025}}</ref><ref>{{Cite web |last=Broache |first=Anne |date=2008-05-20 |title=Senators weigh new laws over China online censorship |url=https://news.cnet.com/8301-10784_3-9948331-7.html |url-status=dead |archive-url=https://web.archive.org/web/20080907214313/https://news.cnet.com/8301-10784_3-9948331-7.html |archive-date=2008-09-07}}</ref>

====Removing access to critical downloads for products that are end-of-support====
[[File:Cisco Security removes everything for discontinued products.png|thumb|Cisco's Retired Products page with a note explaining that they purposely remove documentation, downloads and product pages from the Cisco.com website "for security purposes"]]
Cisco removes all downloads for products that are past their end-of-support date, making it impossible to obtain software or firmware from official sources for your Cisco product. Cisco claims "'''Note:''' For security purposes, upon retirement of a product, Cisco Systems purposely removes documentation, downloads, and product pages from the Cisco.com website, though you may be able to obtain peer support in the Cisco Community."<ref>{{Cite web |date=2026-02-25 |title=Retired Products |url=https://www.cisco.com/c/en/us/support/security/retired.html |url-status=live |archive-url=https://web.archive.org/web/20260222210213/https://www.cisco.com/c/en/us/support/security/retired.html |archive-date=2026-02-22 |access-date=2026-02-25 |website=Cisco Product Support}}</ref> This is considered to be [[security through obscurity]]. If you, a consumer, have obtained obsolete Cisco hardware and wish to utilize it in a working environment, Cisco has deliberately made it harder to update your device to shield against security issues, or add features.

====Requiring a service contract to download firmware for products that are in-support====
[[File:Cisco forcing service contract for file access.png|thumb|A Cisco download page showing the text "'''Log In and Service Contract Required".''']]
Some Cisco products such as the [https://www.cisco.com/c/en/us/support/routers/1000-series-integrated-services-routers-isr/series.html Cisco ISR 1000 series] require an active service contract from Cisco to download any files such as firmware, software, patches, etc. This makes updating devices to their latest respective versions increasingly harder, as you are [[Forced account|required to sign in]] to an account and pay a subscription fee just to update components of the device that you already own. "To Download this software, you must have a valid service contract associated to your Cisco.com profile"<ref>{{Cite web |date=2026-02-25 |title=Cisco 1000 Series Integrated Services Routers download page showing "Service Contract Required" |url=https://www.cisco.com/c/en/us/support/routers/1000-series-integrated-services-routers-isr/series.html#~tab-downloads |url-status=live |archive-url=https://web.archive.org/web/20250831232702/https://www.cisco.com/c/en/us/support/routers/1000-series-integrated-services-routers-isr/series.html#~tab-downloads |archive-date=2025-08-31 |access-date=2026-02-25 |website=Cisco Product Support}}</ref>

====Withholding bug details from customers without a service contract====
Cisco hides bug details, most importantly the resolution/workaround of a bug from non-paying customers. You are required to log into a Cisco account to view bug details, and even then you are only permitted to view 200 bugs a month without paying for a service contract.<ref>{{Cite web |date=2026-02-25 |title=Cisco Bug Search Tool |url=https://bst.cisco.com/quickview/bug/CSCvu61065 |url-status=live |archive-url=https://web.archive.org/web/20260225021043/https://bst.cisco.com/quickview/bug/CSCvu61065 |archive-date=2026-02-25 |access-date=2026-02-25}}</ref>

"Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract."

====Requires employees to sign perpetual forced arbitration agreements when hired, preventing current or former employees from ever suing the company.{{Citation needed}}====

==References==
<references />
[[Category:{{PAGENAME}}]]
[[Category:Articles in need of additional work]]

Cisco Meraki

2026-06-05T18:47:42Z

Wownyc:

{{StubNotice}}
{{Incomplete}}

{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a company providing subscription-based cloud-managed networking hardware. Company was previously friendly to open-source.<ref name="watchmysys">https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/</ref><ref name="only_took_four_months">https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4</ref><ref>https://forum.archive.openwrt.org/viewtopic.php?id=63838</ref>

==Consumer-impact summary==

Locked down hardware (SecureBoot) since ~2018.<ref>https://forum.openwrt.org/t/cisco-meraki-mx68w/134895</ref><ref>https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881</ref> Hardware before 2018, or with SecureBoot exploits may be reflashable to OpenWRT.<ref name="watchmysys" /><ref>https://openwrt.org/toh/meraki/start</ref>

Built on open source, but delays releasing source code<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5</ref><ref name="mr46">https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64</ref>, and/or releases source code that doesn't build<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60</ref><ref name="mr46" />.

Creates tons of e-waste (e.g, on eBay).

Some models may brick if tampered with.<ref>https://github.com/riptidewave93/LEDE-MR33/issues/13</ref>

===User freedom===

===User privacy===

===Business model===

Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx60
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx64
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/support-for-meraki-mx85/207538
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr52
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr18
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |https://openwrt.org/toh/meraki/mr34
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr42
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 https://github.com/halmartin/meraki-builder/issues/11
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |https://github.com/halmartin/meraki-builder/issues/23
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|}

===Other Products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{reflist}}

[[Category:{{PAGENAME}}]]

Cisco Meraki

2026-06-05T18:45:32Z

Wownyc: add stub notice

{{StubNotice}}

{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a company providing subscription-based cloud-managed networking hardware. Company was previously friendly to open-source.<ref name="watchmysys">https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/</ref><ref name="only_took_four_months">https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4</ref><ref>https://forum.archive.openwrt.org/viewtopic.php?id=63838</ref>

==Consumer-impact summary==

Locked down hardware (SecureBoot) since ~2018.<ref>https://forum.openwrt.org/t/cisco-meraki-mx68w/134895</ref><ref>https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881</ref> Hardware before 2018, or with SecureBoot exploits may be reflashable to OpenWRT.<ref name="watchmysys" /><ref>https://openwrt.org/toh/meraki/start</ref>

Built on open source, but delays releasing source code<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5</ref><ref name="mr46">https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64</ref>, and/or releases source code that doesn't build<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60</ref><ref name="mr46" />.

Creates tons of e-waste (e.g, on eBay).

Some models may brick if tampered with.<ref>https://github.com/riptidewave93/LEDE-MR33/issues/13</ref>

===User freedom===

===User privacy===

===Business model===

Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx60
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx64
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/support-for-meraki-mx85/207538
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr52
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr18
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |https://openwrt.org/toh/meraki/mr34
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr42
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 https://github.com/halmartin/meraki-builder/issues/11
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |https://github.com/halmartin/meraki-builder/issues/23
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|}

===Other Products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{reflist}}

[[Category:{{PAGENAME}}]]

Cisco Meraki

2026-06-05T18:44:56Z

Wownyc: change type

{{CompanyCargo
|Description=Subscription-based cloud-managed IT hardware
|Founded=2006
|Industry=
|Logo=
|ParentCompany=Cisco Systems, Inc.
|CompanyAlias=
|Type=
|Website=http://meraki.cisco.com/
}}

Cisco Meraki is a company providing subscription-based cloud-managed networking hardware. Company was previously friendly to open-source.<ref name="watchmysys">https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/</ref><ref name="only_took_four_months">https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/4</ref><ref>https://forum.archive.openwrt.org/viewtopic.php?id=63838</ref>

==Consumer-impact summary==

Locked down hardware (SecureBoot) since ~2018.<ref>https://forum.openwrt.org/t/cisco-meraki-mx68w/134895</ref><ref>https://github.com/halmartin/meraki-builder/issues/11#issuecomment-751338881</ref> Hardware before 2018, or with SecureBoot exploits may be reflashable to OpenWRT.<ref name="watchmysys" /><ref>https://openwrt.org/toh/meraki/start</ref>

Built on open source, but delays releasing source code<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409/5</ref><ref name="mr46">https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/64</ref>, and/or releases source code that doesn't build<ref>https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/60</ref><ref name="mr46" />.

Creates tons of e-waste (e.g, on eBay).

Some models may brick if tampered with.<ref>https://github.com/riptidewave93/LEDE-MR33/issues/13</ref>

===User freedom===

===User privacy===

===Business model===

Subscription-based cloud-managed networking hardware. Primarily for businesses.

===Market control===

==Incidents==
{{Ph-C-Inc}}
This is a list of all consumer-protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===Example incident one (''date'')===
{{Main|link to the main CR Wiki article}}
Short summary of the incident (could be the same as the summary preceding the article).
===Example incident two (''date'')===
...

==Products==
{{Ph-C-P}}

For the latest on OpenWrt device support, see OpenWrt's site.

===MX Series===
{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''Description'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MX60
| align="left" |
| align="right" |2011-07-13
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx60
|-
| align="left" |MX400
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX600
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX80
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |Sort of
| align="left" |Missing APM86290 support in mainline Linux
| align="left" |https://forum.openwrt.org/t/support-for-cisco-meraki-mx80/16572/32
|-
| align="left" |MX90
| align="left" |
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX60W
| align="left" |
| align="right" |2012-10-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX64
| align="left" |MX64 MX64W
| align="right" |2015-02-05
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mx64
|-
| align="left" |MX84
| align="left" |
| align="right" |2015-11-10
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX65
| align="left" |MX65 MX65W
| align="right" |2016-02-12
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX250
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX450
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX67
| align="left" |MX67 MX67W MX67C
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |
|-
| align="left" |MX68
| align="left" |MX68 MX68 MX68CW
| align="right" |2018-08-28
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895
|-
| align="left" |MX100
| align="left" |
| align="left" |Pre-2014
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MX105
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/meraki-mx105-lets-see-if-we-can-figure-this-out/170841/3
|-
| align="left" |MX75
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MX85
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/support-for-meraki-mx85/207538
|-
| align="left" |MX95
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|}

===MR Series===

Wireless access point devices

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Description'''
! align="left" |'''Launch/Announce'''
! align="left" |'''Secure Boot?'''
! align="left" |'''OpenWrt Support'''
! align="left" |'''Notes'''
! align="left" |'''Link'''
|-
| align="left" |MR62
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR66
| align="left" |
| align="right" |2011-08-23
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR72
| align="left" |
| align="right" |2014-12-09
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-05-25
| align="left" |No
| align="left" |No
| align="left" |missing QSGMII support in dwmac-ipq806x driver
| align="left" |https://forum.openwrt.org/t/adding-openwrt-support-for-meraki-mr53/67505/26
|-
| align="left" |MR52
| align="left" |dual-band enterprise class 802.11ac Wave 2 cloud-managed access point.
| align="right" |2016-06-24
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr52
|-
| align="left" |MR84
| align="left" |
| align="right" |2016-09-13
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR30H
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |Yes, dropped?
| align="left" |
| align="left" |
|-
| align="left" |MR32
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes but no wifi. Broadcom reference fw works tho
| align="left" |
| align="left" |https://forum.openwrt.org/t/flash-meraki-mr32-new-method/108365/11
|-
| align="left" |MR33
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |Yes™
| align="left" |Bootloader may brick itself if tampered
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13
|-
| align="left" |MR74
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2017-03-08
| align="left" |Yes
| align="left" |Soon™
| align="left" |
| align="left" |https://github.com/riptidewave93/LEDE-MR33/issues/13#issuecomment-3267672239
|-
| align="left" |MR20 Go GR10
| align="left" |dual-band enterprise class 802.11ac cloud-managed access point.
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR70 Go GR60
| align="left" |
| align="right" |2018-01-29
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |https://watchmysys.com/blog/2026/02/openwrt-for-meraki-mr20-mr70-go-gr10-and-go-gr60/
|-
| align="left" |MR42E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR53E
| align="left" |
| align="right" |2018-02-01
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR12
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR16
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR18
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr18
|-
| align="left" |MR24
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR26
| align="left" |
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MR28
| align="left" |dual-band enterprise Wi-Fi 6 cloud-managed access point.
| align="left" |
| align="left" |
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MR34
| align="left" |
| align="left" |
| align="left" |No
| align="left" |No
| align="left" |Unsupported broadcom wireless
| align="left" |https://openwrt.org/toh/meraki/mr34
|-
| align="left" |MR42
| align="left" |
| align="left" |
| align="left" |No
| align="left" |Yes
| align="left" |
| align="left" |https://openwrt.org/toh/meraki/mr42
|-
| align="left" |MR44
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr44/117409
|-
| align="left" |MR46
| align="left" |
| align="left" |
| align="left" |Yes
| align="left" |No
| align="left" |
| align="left" |https://forum.openwrt.org/t/openwrt-support-for-meraki-mr46/143499/21
|-
| align="left" |MR36
| align="left" |
| align="left" |
| align="left" |
| align="left" |No
| align="left" |u-boot source is available
| align="left" |https://forum.openwrt.org/t/mr36-bootloader-uboot-source-code/204097
|}

===MS Series===

Network switches

{| class="wikitable sortable"
! align="left" |'''Product Series'''
! align="left" |'''Products'''
! align="left" |'''Launch'''
! align="left" |'''SecureBoot'''
! align="left" |
! align="left" |
|-
| align="left" |MS120
| align="left" |MS-120-8
| align="right" |2017-09-12
| align="left" |Yes
| align="left" |
| align="left" |
|-
| align="left" |MS210
| align="left" |
| align="right" |2017-09-12
| align="left" |
| align="left" |“MS120 series is not supported. Won't be supported unless a workaround to boot unsigned code is found.”
| align="left" |https://forum.openwrt.org/t/cisco-meraki-mx68w/134895/13 https://forum.openwrt.org/t/support-for-meraki-ms120-8lp/59212 https://github.com/halmartin/meraki-builder/issues/11
|-
| align="left" |MS22
| align="left" |MS22 MS22P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS220
| align="left" |MS220-8P MS220-24 MS220-24P MS220-48 MS220-48LP MS220-48FP
| align="left" |2013-06 2013-11-05 ? ? ? ?
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS225
| align="left" |
| align="right" |2016-12-06
| align="left" |No
| align="left" |“there is a beta firmware available for the MS225. Email me if you'd like to participate in testing.”
| align="left" |https://github.com/halmartin/meraki-builder/issues/23
|-
| align="left" |MS250
| align="left" |
| align="right" |2016-12-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS320
| align="left" |MS320-24 MS320-24P MS320-48 MS320-48LP MS320-48FP
| align="right" |? ? ? ? 2013-11-05
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS42
| align="left" |MS42 MS42P
| align="right" |2012-01-18
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS420
| align="left" |MS420-24 MS420-48
| align="left" |? 2013-06
| align="left" |
| align="left" |
| align="left" |
|-
| align="left" |MS350-24X
| align="left" |
| align="right" |2016-05-25
| align="left" |
| align="left" |
| align="left" |
|}

===Other Products===

{| class="wikitable sortable"
! align="left" |'''Product'''
! align="left" |'''Launch'''
! align="left" |'''Product Description'''
! align="left" |'''Link'''
|-
| align="left" |Z1
| align="right" |2012-10-09
| align="left" |
| align="left" |
|-
| align="left" |Z3
| align="right" |2017-09-12
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Go GX20
| align="left" |
| align="left" |"remote work gateway"
| align="left" |https://watchmysys.com/blog/2024/04/breaking-secure-boot-on-the-meraki-z3-and-meraki-go-gx20/
|-
| align="left" |Z3C
| align="right" |2018-08-28
| align="left" |
| align="left" |
|-
| align="left" |MC74
| align="right" |2016-05-25
| align="left" |VoIP phone
| align="left" |
|}

==See also==
{{Ph-C-SA}}

==References==
{{reflist}}

[[Category:{{PAGENAME}}]]

Wemo discontinuation of service

2026-06-05T18:38:27Z

Wownyc: oops

{{IncidentCargo
|Company=Belkin
|StartDate=10 July 2025
|EndDate=
|Status=
|ProductLine=Wemo
|Product=
|ArticleType=
|Type=
|Description=
}}{{OngoingEvent}}

[[Belkin]] [[Wemo]] smart home devices require cloud connectivity to work. On 10 July 2025, Belkin announced the shutdown of cloud services supporting most Wemo devices, effective 31 January 2026.<ref name=":2">{{Cite web |title=Belkin Official Support - Wemo Support Ending – What You Need to Know |url=https://www.belkin.com/support-article/?articleNum=335419 |url-status=live |archive-url=https://web.archive.org/web/20250711172157/https://www.belkin.com/support-article/?articleNum=335419 |date=2025-07-10 |access-date=2025-07-13 |archive-date=11 Jul 2025 |website=Belkin Official Support}}</ref> These devices remain for sale on Belkin's Amazon WeMo store<ref>{{Cite web |title=Amazon.com: Wemo Smart Plug with Thread - Smart Outlet for Apple HomeKit - Smart Home Products, Smart Home Lighting, Smart Home Gadgets - Homekit Smart Plug - Tech Gifts - Works W/ Apple iPhone, Easy NFC Set Up : Tools & Home Improvement |url=https://www.amazon.com/Wemo-Smart-Plug-Thread-Products/dp/B09T4S3QKC |url-status=live |archive-url=http://web.archive.org/web/20260220201917/https://www.amazon.com/Wemo-Smart-Plug-Thread-Products/dp/B09T4S3QKC |archive-date=20 Feb 2026 |access-date=2025-07-13 |website=[[Amazon]]}}</ref> and advertising them as working with Google, Alexa, & more.<ref name=":02">{{Cite web |title=Amazon.com: Wemo |url=https://www.amazon.com/stores/Wemo/page/E33F6EA2-93FC-48CD-8BF6-EE10D5398795 |url-status=live |archive-url=https://web.archive.org/web/20260227172544/https://www.amazon.com/stores/Wemo/page/E33F6EA2-93FC-48CD-8BF6-EE10D5398795 |archive-date=2026-02-27 |access-date=2025-07-13 |website=Amazon.com: Wemo}}</ref><ref>{{Cite web |last=Preston |first=Dominic |date=2025-07-11 |title=Belkin is ending support for nearly all its Wemo smart home devices |url=https://www.theverge.com/news/705136/belkin-wemo-smart-home-support-ending-homekit-thread |url-status=live |archive-url=https://web.archive.org/web/20250711204531/https://www.theverge.com/news/705136/belkin-wemo-smart-home-support-ending-homekit-thread |archive-date=11 Jul 2025 |access-date=2025-07-14 |website=The Verge |language=en-US}}</ref>

This shutdown will disable remote access and automation functionality for 27+ device models sold between August 2015 and November 2023, affecting thousands of customers who purchased these devices as permanent smart home solutions. The incident is one example of a broader trend of IoT device abandonment and {{Wplink|Tethering|software tethering}} practices that enable manufacturers to remotely disable purchased products.

==Background==
First launched in 2011, Wemo is a smart home product line developed by Belkin. The product line includes smart plugs, light switches, motion sensors, dimmers, and connected appliances like coffee makers and humidifiers. These devices were marketed as one-time purchases with cloud features, app control, and integration with voice assistants including Amazon Alexa, Google Home, and Apple HomeKit.

Wemo gained popularity for its convenience, ease of use, and broad compatibility with voice assistants and cloud automation programs. Devices were sold with '''no disclosed end-of-life timeline for cloud functionality'''.

==2025 shutdown announcement==
[[File:Belkin email Wemo shutdown.jpg|alt=Email from Belkin about Wemo shutdown|thumb|right|Email notification sent to Wemo customers about the January 2026 shutdown]]

On 10 July 2025, Belkin created a support page and began e-mailing customers informing them that most Wemo devices would stop working on 31 January 2026.<ref name=":2" /> The company described this as a ''"difficult decision"'' to shut down cloud services for Wemo products, stating they needed to ''"focus our resources on different parts of the Belkin business."''

The shutdown affects any feature requiring cloud connectivity, including:
*Wemo app functionality
*Amazon Alexa integration
*Google Home integration
*Remote access capabilities
*Automation and scheduling features
*Technical support

===Devices affected===
This shutdown impacts 24 different device models spanning smart plugs, switches, specialty appliances, and sensors sold between August 2015 and November 2023, including:
*Wemo Smart Plug (multiple generations)
*Wemo Smart Light Switches
*Wemo In-Wall Dimmers and Switches
*Wemo connected appliances (smart crockpots, air purifiers, coffee makers, humidifiers)
*Wemo Motion Sensors and LED lighting kits
*Wemo Outdoor Smart Plug
*Wemo Mini Smart Plug
*Various specialty devices and older models

Only four Thread-based models will continue functioning after the shutdown date. If using Apple HomeKit, they must have been configured prior to 31 January 2026.<ref name=":2"/>

{| class="wikitable sortable"
! align="left" |'''SKU'''
! align="left" |'''Description'''
! align="left" |Last Sold Units Date
! align="left" |'''Warranty'''
|-
| align="left" |F7C031
| align="left" |Wemo Link
| align="left" |2015-08
| align="left" |2-Year
|-
| align="left" |F7C046
| align="left" |Wemo Humidifier
| align="left" |2015-12
| align="left" |3-Year
|-
| align="left" |F7C045
| align="left" |Wemo CrockPot
| align="left" |2016-04
| align="left" |1-Year
|-
| align="left" |F7C048
| align="left" |Wemo Heater B
| align="left" |2016-06
| align="left" |3-Year
|-
| align="left" |F7C049
| align="left" |Wemo Air Purifier
| align="left" |2016-07
| align="left" |3-Year
|-
| align="left" |F7C047
| align="left" |Wemo Heater A
| align="left" |2016-09
| align="left" |3-Year
|-
| align="left" |F7C050
| align="left" |Wemo Coffee Maker (Mr. Coffee)
| align="left" |2016-12
| align="left" |1-Year
|-
| align="left" |F8J007
| align="left" |Wi-Fi Baby Monitor
| align="left" |2017-06
| align="left" |1-Year
|-
| align="left" |F5Z0489
| align="left" |Wemo LED Lighting Bundle
| align="left" |2017-09
| align="left" |2-Year
|-
| align="left" |F7C028
| align="left" |Wemo Motion Sensor
| align="left" |2017-09
| align="left" |2-Year
|-
| align="left" |F5Z0340
| align="left" |Wemo Switch + Motion Sensor
| align="left" |2017-10
| align="left" |2-Year
|-
| align="left" |F7C043
| align="left" |Wemo Maker Module
| align="left" |2017-11
| align="left" |2-Year
|-
| align="left" |F7C033
| align="left" |Wemo Zigbee Bulb, E27
| align="left" |2018-03
| align="left" |2-Year
|-
| align="left" |F7C061
| align="left" |Wemo Insight v2
| align="left" |2018-07
| align="left" |1-Year
|-
| align="left" |F7C027
| align="left" |Wemo Switch
| align="left" |2019-01
| align="left" |2-Year
|-
| align="left" |F7C062
| align="left" |Wemo Light Switch v2
| align="left" |2019-11
| align="left" |1-Year
|-
| align="left" |F7C029
| align="left" |Wemo Insight
| align="left" |2020-06
| align="left" |2-Year
|-
| align="left" |WLS0403
| align="left" |Wemo Smart Light Switch 3-Way
| align="left" |2021-09
| align="left" |3-Year
|-
| align="left" |WSP070
| align="left" |Wemo Mini Smart Plug
| align="left" |2022-07
| align="left" |3-Year
|-
| align="left" |WDS060
| align="left" |Wemo Wi-Fi Smart Light Switch w/ Dimmer
| align="left" |2022-09
| align="left" |3-Year
|-
| align="left" |WLS040
| align="left" |Wemo Smart Light Switch
| align="left" |2022-09
| align="left" |3-Year
|-
| align="left" |F7C064
| align="left" |Wemo HomeKit
| align="left" |2022-09
| align="left" |1-Year
|-
| align="left" |F7C059
| align="left" |Wemo Dimmer Light Switch
| align="left" |2022-11
| align="left" |1-Year
|-
| align="left" |F7C063
| align="left" |Wemo Mini Plugin Switch
| align="left" |2022-12
| align="left" |3-Year
|-
| align="left" |F7C030
| align="left" |Wemo Light Switch
| align="left" |2022-12
| align="left" |2-Year
|-
| align="left" |WSP090
| align="left" |Wemo Outdoor Plug
| align="left" |2023-05
| align="left" |3-Year
|-
| align="left" |WSP080
| align="left" |Wemo Mini Smart Plug
| align="left" |2023-11
| align="left" |3-Year
|}

===Timing and warranty issues===
Devices with three-year warranties sold as recently as November 2023 will lose core functionality before warranty expiration. Belkin offers only partial refunds for devices still under warranty after the shutdown date, requiring consumers to wait until their devices are non-functional before seeking compensation.

==Belkin suggests disposing of the devices==
Belkin's official response recommends that customers dispose of out-of-warranty devices at authorized e-waste recycling centers, despite the devices remaining physically functional:<ref name=":2" />
<blockquote>''"For any Wemo devices you have that are out of warranty, will not work with HomeKit or if you are unable to use HomeKit, we recommend disposing of these devices at an authorized e-waste recycling center."''</blockquote>

This recommendation is particularly controversial for in-wall switches and dimmers that are permanently installed in customers' homes. One Ars Technica forum user suggested ''"boxing them up and shipping them directly to Belkin corporate headquarters."''<ref>{{Cite web |author=ReaderBot |title=Belkin shows tech firms getting too comfortable with bricking customers' stuff |url=https://arstechnica.com/civis/threads/belkin-shows-tech-firms-getting-too-comfortable-with-bricking-customers%E2%80%99-stuff.1508302/post-43842885 |website=Ars Technica |date=11 Jul 2025 |access-date=17 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260222233540/https://arstechnica.com/civis/threads/belkin-shows-tech-firms-getting-too-comfortable-with-bricking-customers%E2%80%99-stuff.1508302/#post-43842885 |archive-date=22 Feb 2026}}</ref>

==Continued sales of soon-to-be-dead products==
Despite announcing the shutdown, Belkin continues selling affected Wemo devices through [[Amazon]] and other retailers without disclosing the impending service termination.<ref name=":0" /> As of July 2025, the Wemo Amazon store prominently displays compatibility claims with Amazon Alexa, Google Assistant, and other platforms that will stop functioning in six months.

<gallery mode="slideshow">
File:Belkin still selling Wemo dimmer.jpg|Belkin light switch still for sale despite announced functionality loss.<ref name=":7">{{Cite web |title=WeMo Smart Light Switch 2ND Gen |url=https://www.amazon.com/WeMo-Smart-Light-Switch-2ND/dp/B07RT8H9WH |archive-url=http://web.archive.org/web/20250904072417/https://www.amazon.com/WeMo-Smart-Light-Switch-2ND/dp/B07RT8H9WH |archive-date=4 Sep 2025|access-date=13 Jul 2025 |website=[[Amazon]]}}</ref>
File:Amazon store Belkin Wemo works.jpg|Belkin's Amazon store advertising platform compatibility despite planned termination.<ref name=":0" />
</gallery>

==Consumer response and criticism==
===Immediate reaction===
Customer response was swift and negative, with users expressing feelings of abandonment and frustration over recent purchases becoming obsolete.<ref>{{Cite web |author= |title=Wemo - Apps on Google Play |url=https://play.google.com/store/apps/details?id=com.belkin.wemoandroid |website=[[Google]] |date= |access-date=17 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260109061920/https://play.google.com/store/apps/details?id=com.belkin.wemoandroid |archive-date=9 Jan 2026}}</ref> The company provided only six months of notice for a shutdown affecting fourteen years of product sales.

===Technology community backlash===

Ars Technica's coverage criticized Belkin's move as reflecting an industry that ''"has grown too comfortable with bricking customers' stuff"'' without offering adequate recourse or transparency.<ref>{{Cite web |last=Harding |first=Scharon |title=Belkin shows tech firms getting too comfortable with bricking customers' stuff |url=https://arstechnica.com/gadgets/2025/07/belkin-shows-tech-firms-getting-too-comfortable-with-bricking-customers-stuff/ |website=Ars Technica |date=12 Jul 2025 |access-date=17 Feb 2026 |url-status=live |archive-url=http://web.archive.org/web/20251119165125/https://arstechnica.com/gadgets/2025/07/belkin-shows-tech-firms-getting-too-comfortable-with-bricking-customers-stuff/ |archive-date=19 Nov 2025}}</ref>

[[Reddit]] discussions in r/WeMo revealed widespread customer anger:
<blockquote>''"They just guaranteed I'll never buy Belkin again. Half the light switches in my house are going to need replacing."<ref>{{Cite web |author=whitebean |title=It’s officially ending. I just got this email. Glad I started switching to Zigbee last week. |url=https://old.reddit.com/r/WeMo/comments/1lwilvc/its_officially_ending_i_just_got_this_email_glad/n2esknt/ |website=[[Reddit]] |date=10 Jul 2025 |access-date=17 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260222233607/https://old.reddit.com/r/WeMo/comments/1lwilvc/its_officially_ending_i_just_got_this_email_glad/n2esknt/ |archive-date=22 Feb 2026}}</ref>''</blockquote>

<blockquote>''"I figured it's made by a trusted brand so it would be better than using no name Amazon junk. What a joke. [...] Belkin is never getting a dollar from me again."<ref>{{Cite web
|author=ho_merjpimpson |title=It’s officially ending. I just got this email. Glad I started switching to Zigbee last week. |url=https://old.reddit.com/r/WeMo/comments/1lwilvc/its_officially_ending_i_just_got_this_email_glad/n2et52a/ |website=[[Reddit]] |date=10 Jul 2025 |access-date=17 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260222233628/https://old.reddit.com/r/WeMo/comments/1lwilvc/its_officially_ending_i_just_got_this_email_glad/n2et52a/ |archive-date=22 Feb 2026}}</ref>''</blockquote>

Users called for firmware updates enabling local control and drew parallels to digital game preservation campaigns such as the [[Stop Killing Games]] campaign.

==Technical workarounds==
While technical solutions exist for maintaining some device functionality, they require a good amount of technical expertise that most consumers lack:

*'''Apple HomeKit:''' Devices configured with HomeKit before the shutdown will continue working through Apple's ecosystem.
*'''Home Assistant:''' Open-source platform offering local control through {{Wplink|universal plug-and-play}} device discovery.
*'''Third-party firmware:''' Projects such as [https://ota.tasmota.com/tasmota/ Tasmota] enable complete device replacement, though requiring technical modification
*'''Pywemo:''' Supports joining and changing Wi-Fi settings, and local control via Wemo's local API (which is not documented by Belkin). [https://github.com/pywemo/pywemo GitHub project link]

The existence of these workarounds demonstrates that the shutdown represents a business decision rather than out of technical necessity, as devices can continue functioning locally without cloud services.

==Industry context==
The Wemo shutdown represents part of a broader pattern of IoT device abandonment affecting millions of devices globally. Similar shutdowns include:
*Google Cloud IoT Core termination (2023)
*Amazon Web Services IoT service discontinuations (2024—2026)
*Complete collapse of {{Wplink|Insteon}}'s smart home system (2022), affecting 1.3 million customers<ref>{{Cite web |last=Amadeo |first=Ron |title=Shameful: Insteon looks dead—just like its users’ smart homes |url=https://arstechnica.com/gadgets/2022/04/shameful-insteon-looks-dead-just-like-its-users-smart-homes/ |website=Ars Technica |date=18 Apr 2022 |access-date=13 Jul 2025 |url-status=live |archive-url=http://web.archive.org/web/20251213064809/https://arstechnica.com/gadgets/2022/04/shameful-insteon-looks-dead-just-like-its-users-smart-homes/ |archive-date=13 Dec 2025}}</ref>

Academic research has identified this phenomenon as ''"regulation by bricking"''<ref>{{Cite journal |last=Tusikov |first=Natasha |date=18 Jun 2019 |title=Regulation through “bricking”: private ordering in the “Internet of Things” |url=https://policyreview.info/articles/analysis/regulation-through-bricking-private-ordering-internet-things |url-status=live |journal=Internet Policy Review |volume=8 |issue=2 |doi=10.14763/2019.2.1405 |archive-url=https://web.archive.org/web/20190807232444/https://policyreview.info/articles/analysis/regulation-through-bricking-private-ordering-internet-things |archive-date=7 Aug 2019 |access-date=13 Jul 2025}}</ref>'','' a form of corporate control where manufacturers retain the ability to remotely disable devices after purchase through licensing agreements and cloud service dependencies.

==Consumer protection and regulatory response==
The incident shows the gaps in consumer protection frameworks for software-dependent devices. Current warranty laws assume hardware failure rather than service termination, creating uncertainty about whether cloud service shutdowns count as defective products.

Consumer advocacy organizations, led by Consumer Reports, have mobilized against IoT device abandonment practices, coining the term ''"software tethering"'' to describe manufacturer control over post-purchase device functionality.<ref>{{Cite web |last1=Brookman |first1=Justin |last2=Higginbotham |first2=Stacey |last3=Gutterman |first3=Lucas |display-authors=2 |title=Consumer Reports, U.S. PIRG, and 15 other groups call on FTC to create clear guidance for ‘software tethering’ |url=https://advocacy.consumerreports.org/research/group-letter-ftc-software-tethering/ |website=Consumer Reports |date=13 Jul 2025 |access-date=13 Jul 2025 |url-status=live |archive-url=http://web.archive.org/web/20251119040431/https://advocacy.consumerreports.org/research/group-letter-ftc-software-tethering/ |archive-date=19 Nov 2025}}</ref> The coalition has petitioned the [[Federal Trade Commission|FTC]] to address these practices and establish mandatory disclosure requirements for device support timelines.

===Legal action===
On 28 January 2026, ClassAction.org issued a website form for people affected by the Wemo cloud shutdown to contact them regarding a potential mass arbitration event.<ref>{{Cite web |author=
|title=Belkin Wemo End of Life Arbitration: Affected by Discontinued Belkin Wemo Support? |url=https://www.classaction.org/belkin-wemo-bricking-arbitration-lawsuit-info |website=ClassAction.org |date=28 Jan 2026 |access-date=29 Jan 2026 |url-status=live |archive-url=https://web.archive.org/web/20260129143210/https://www.classaction.org/belkin-wemo-bricking-arbitration-lawsuit-info |archive-date=29 Jan 2026}}</ref> In addition, the Sauder Schelkopf law firm launched their own investigation into the Wemo cloud shutdown.<ref>{{Cite web |author= |title=Belkin Ends Support for Wemo Smart Home Products Class Action Lawsuit Investigation |url=https://sauderschelkopf.com/investigations/belkin-ends-support-for-wemo-smart-home-products-class-action-lawsuit-investigation/ |website=Sauder Schelkopf Attorneys At Law |date=2025 |access-date=17 Feb 2026 |url-status=live |archive-url=http://web.archive.org/web/20260129144014/https://sauderschelkopf.com/investigations/belkin-ends-support-for-wemo-smart-home-products-class-action-lawsuit-investigation/ |archive-date=29 Jan 2026}}</ref>
<gallery>
File:Fettig et al. v. Belkin International, Inc. Wemo Case No. 326cv01590 Filed Feb 24 2026.pdf|Belkin (Wemo) Class Action Filing US Federal Court.
</gallery>

==See also==
*[[Planned obsolescence]]
*[[Right to repair]]

==References==
{{Reflist}}

[[Category:Belkin]]
[[Category:Wemo]]
[[Category:Internet of Things]]
[[Category:Planned obsolescence]]
[[Category:Smart home devices]]
[[Category:Ongoing events]]

Wemo discontinuation of service

2026-06-05T18:37:55Z

Wownyc:

{{IncidentCargo
|Company=Belkin
|StartDate=10 July 2025
|EndDate=
|Status=
|ProductLine=Wemo
|Product=
|ArticleType=
|Type=
|Description=
}}{{OngoingEvent}}

[[Belkin]] [[Wemo]] smart home devices require cloud connectivity to work. On 10 July 2025, Belkin announced the shutdown of cloud services supporting most Wemo devices, effective 31 January 2026.<ref name=":2">{{Cite web |title=Belkin Official Support - Wemo Support Ending – What You Need to Know |url=https://www.belkin.com/support-article/?articleNum=335419 |url-status=live |archive-url=https://web.archive.org/web/20250711172157/https://www.belkin.com/support-article/?articleNum=335419 |date=2025-07-10 |access-date=2025-07-13 |archive-date=11 Jul 2025 |website=Belkin Official Support}}</ref> These devices remain for sale on Belkin's Amazon WeMo store<ref>{{Cite web |title=Amazon.com: Wemo Smart Plug with Thread - Smart Outlet for Apple HomeKit - Smart Home Products, Smart Home Lighting, Smart Home Gadgets - Homekit Smart Plug - Tech Gifts - Works W/ Apple iPhone, Easy NFC Set Up : Tools & Home Improvement |url=https://www.amazon.com/Wemo-Smart-Plug-Thread-Products/dp/B09T4S3QKC |url-status=live |archive-url=http://web.archive.org/web/20260220201917/https://www.amazon.com/Wemo-Smart-Plug-Thread-Products/dp/B09T4S3QKC |archive-date=20 Feb 2026 |access-date=2025-07-13 |website=[[Amazon]]}}</ref> and advertising them as working with Google, Alexa, & more.<ref name=":02">{{Cite web |title=Amazon.com: Wemo |url=https://www.amazon.com/stores/Wemo/page/E33F6EA2-93FC-48CD-8BF6-EE10D5398795 |url-status=live |archive-url=https://web.archive.org/web/20260227172544/https://www.amazon.com/stores/Wemo/page/E33F6EA2-93FC-48CD-8BF6-EE10D5398795 |archive-date=2026-02-27 |access-date=2025-07-13 |website=Amazon.com: Wemo}}</ref><ref>{{Cite web |last=Preston |first=Dominic |date=2025-07-11 |title=Belkin is ending support for nearly all its Wemo smart home devices |url=https://www.theverge.com/news/705136/belkin-wemo-smart-home-support-ending-homekit-thread |url-status=live |archive-url=https://web.archive.org/web/20250711204531/https://www.theverge.com/news/705136/belkin-wemo-smart-home-support-ending-homekit-thread |archive-date=11 Jul 2025 |access-date=2025-07-14 |website=The Verge |language=en-US}}</ref>

This shutdown will disable remote access and automation functionality for 27+ device models sold between August 2015 and November 2023, affecting thousands of customers who purchased these devices as permanent smart home solutions. The incident is one example of a broader trend of IoT device abandonment and {{Wplink|Tethering|software tethering}} practices that enable manufacturers to remotely disable purchased products.

==Background==
First launched in 2011, Wemo is a smart home product line developed by Belkin. The product line includes smart plugs, light switches, motion sensors, dimmers, and connected appliances like coffee makers and humidifiers. These devices were marketed as one-time purchases with cloud features, app control, and integration with voice assistants including Amazon Alexa, Google Home, and Apple HomeKit.

Wemo gained popularity for its convenience, ease of use, and broad compatibility with voice assistants and cloud automation programs. Devices were sold with '''no disclosed end-of-life timeline for cloud functionality'''.

==2025 shutdown announcement==
[[File:Belkin email Wemo shutdown.jpg|alt=Email from Belkin about Wemo shutdown|thumb|right|Email notification sent to Wemo customers about the January 2026 shutdown]]

On 10 July 2025, Belkin created a support page and began e-mailing customers informing them that most Wemo devices would stop working on 31 January 2026.<ref name=":2" /> The company described this as a ''"difficult decision"'' to shut down cloud services for Wemo products, stating they needed to ''"focus our resources on different parts of the Belkin business."''

The shutdown affects any feature requiring cloud connectivity, including:
*Wemo app functionality
*Amazon Alexa integration
*Google Home integration
*Remote access capabilities
*Automation and scheduling features
*Technical support

===Devices affected===
This shutdown impacts 24 different device models spanning smart plugs, switches, specialty appliances, and sensors sold between August 2015 and November 2023, including:
*Wemo Smart Plug (multiple generations)
*Wemo Smart Light Switches
*Wemo In-Wall Dimmers and Switches
*Wemo connected appliances (smart crockpots, air purifiers, coffee makers, humidifiers)
*Wemo Motion Sensors and LED lighting kits
*Wemo Outdoor Smart Plug
*Wemo Mini Smart Plug
*Various specialty devices and older models

Only four Thread-based models will continue functioning after the shutdown date. If using Apple HomeKit, they must have been configured prior to 31 January 2026.<ref name=":2">

{| class="wikitable sortable"
! align="left" |'''SKU'''
! align="left" |'''Description'''
! align="left" |Last Sold Units Date
! align="left" |'''Warranty'''
|-
| align="left" |F7C031
| align="left" |Wemo Link
| align="left" |2015-08
| align="left" |2-Year
|-
| align="left" |F7C046
| align="left" |Wemo Humidifier
| align="left" |2015-12
| align="left" |3-Year
|-
| align="left" |F7C045
| align="left" |Wemo CrockPot
| align="left" |2016-04
| align="left" |1-Year
|-
| align="left" |F7C048
| align="left" |Wemo Heater B
| align="left" |2016-06
| align="left" |3-Year
|-
| align="left" |F7C049
| align="left" |Wemo Air Purifier
| align="left" |2016-07
| align="left" |3-Year
|-
| align="left" |F7C047
| align="left" |Wemo Heater A
| align="left" |2016-09
| align="left" |3-Year
|-
| align="left" |F7C050
| align="left" |Wemo Coffee Maker (Mr. Coffee)
| align="left" |2016-12
| align="left" |1-Year
|-
| align="left" |F8J007
| align="left" |Wi-Fi Baby Monitor
| align="left" |2017-06
| align="left" |1-Year
|-
| align="left" |F5Z0489
| align="left" |Wemo LED Lighting Bundle
| align="left" |2017-09
| align="left" |2-Year
|-
| align="left" |F7C028
| align="left" |Wemo Motion Sensor
| align="left" |2017-09
| align="left" |2-Year
|-
| align="left" |F5Z0340
| align="left" |Wemo Switch + Motion Sensor
| align="left" |2017-10
| align="left" |2-Year
|-
| align="left" |F7C043
| align="left" |Wemo Maker Module
| align="left" |2017-11
| align="left" |2-Year
|-
| align="left" |F7C033
| align="left" |Wemo Zigbee Bulb, E27
| align="left" |2018-03
| align="left" |2-Year
|-
| align="left" |F7C061
| align="left" |Wemo Insight v2
| align="left" |2018-07
| align="left" |1-Year
|-
| align="left" |F7C027
| align="left" |Wemo Switch
| align="left" |2019-01
| align="left" |2-Year
|-
| align="left" |F7C062
| align="left" |Wemo Light Switch v2
| align="left" |2019-11
| align="left" |1-Year
|-
| align="left" |F7C029
| align="left" |Wemo Insight
| align="left" |2020-06
| align="left" |2-Year
|-
| align="left" |WLS0403
| align="left" |Wemo Smart Light Switch 3-Way
| align="left" |2021-09
| align="left" |3-Year
|-
| align="left" |WSP070
| align="left" |Wemo Mini Smart Plug
| align="left" |2022-07
| align="left" |3-Year
|-
| align="left" |WDS060
| align="left" |Wemo Wi-Fi Smart Light Switch w/ Dimmer
| align="left" |2022-09
| align="left" |3-Year
|-
| align="left" |WLS040
| align="left" |Wemo Smart Light Switch
| align="left" |2022-09
| align="left" |3-Year
|-
| align="left" |F7C064
| align="left" |Wemo HomeKit
| align="left" |2022-09
| align="left" |1-Year
|-
| align="left" |F7C059
| align="left" |Wemo Dimmer Light Switch
| align="left" |2022-11
| align="left" |1-Year
|-
| align="left" |F7C063
| align="left" |Wemo Mini Plugin Switch
| align="left" |2022-12
| align="left" |3-Year
|-
| align="left" |F7C030
| align="left" |Wemo Light Switch
| align="left" |2022-12
| align="left" |2-Year
|-
| align="left" |WSP090
| align="left" |Wemo Outdoor Plug
| align="left" |2023-05
| align="left" |3-Year
|-
| align="left" |WSP080
| align="left" |Wemo Mini Smart Plug
| align="left" |2023-11
| align="left" |3-Year
|}

===Timing and warranty issues===
Devices with three-year warranties sold as recently as November 2023 will lose core functionality before warranty expiration. Belkin offers only partial refunds for devices still under warranty after the shutdown date, requiring consumers to wait until their devices are non-functional before seeking compensation.

==Belkin suggests disposing of the devices==
Belkin's official response recommends that customers dispose of out-of-warranty devices at authorized e-waste recycling centers, despite the devices remaining physically functional:<ref name=":2" />
<blockquote>''"For any Wemo devices you have that are out of warranty, will not work with HomeKit or if you are unable to use HomeKit, we recommend disposing of these devices at an authorized e-waste recycling center."''</blockquote>

This recommendation is particularly controversial for in-wall switches and dimmers that are permanently installed in customers' homes. One Ars Technica forum user suggested ''"boxing them up and shipping them directly to Belkin corporate headquarters."''<ref>{{Cite web |author=ReaderBot |title=Belkin shows tech firms getting too comfortable with bricking customers' stuff |url=https://arstechnica.com/civis/threads/belkin-shows-tech-firms-getting-too-comfortable-with-bricking-customers%E2%80%99-stuff.1508302/post-43842885 |website=Ars Technica |date=11 Jul 2025 |access-date=17 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260222233540/https://arstechnica.com/civis/threads/belkin-shows-tech-firms-getting-too-comfortable-with-bricking-customers%E2%80%99-stuff.1508302/#post-43842885 |archive-date=22 Feb 2026}}</ref>

==Continued sales of soon-to-be-dead products==
Despite announcing the shutdown, Belkin continues selling affected Wemo devices through [[Amazon]] and other retailers without disclosing the impending service termination.<ref name=":0" /> As of July 2025, the Wemo Amazon store prominently displays compatibility claims with Amazon Alexa, Google Assistant, and other platforms that will stop functioning in six months.

<gallery mode="slideshow">
File:Belkin still selling Wemo dimmer.jpg|Belkin light switch still for sale despite announced functionality loss.<ref name=":7">{{Cite web |title=WeMo Smart Light Switch 2ND Gen |url=https://www.amazon.com/WeMo-Smart-Light-Switch-2ND/dp/B07RT8H9WH |archive-url=http://web.archive.org/web/20250904072417/https://www.amazon.com/WeMo-Smart-Light-Switch-2ND/dp/B07RT8H9WH |archive-date=4 Sep 2025|access-date=13 Jul 2025 |website=[[Amazon]]}}</ref>
File:Amazon store Belkin Wemo works.jpg|Belkin's Amazon store advertising platform compatibility despite planned termination.<ref name=":0" />
</gallery>

==Consumer response and criticism==
===Immediate reaction===
Customer response was swift and negative, with users expressing feelings of abandonment and frustration over recent purchases becoming obsolete.<ref>{{Cite web |author= |title=Wemo - Apps on Google Play |url=https://play.google.com/store/apps/details?id=com.belkin.wemoandroid |website=[[Google]] |date= |access-date=17 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260109061920/https://play.google.com/store/apps/details?id=com.belkin.wemoandroid |archive-date=9 Jan 2026}}</ref> The company provided only six months of notice for a shutdown affecting fourteen years of product sales.

===Technology community backlash===

Ars Technica's coverage criticized Belkin's move as reflecting an industry that ''"has grown too comfortable with bricking customers' stuff"'' without offering adequate recourse or transparency.<ref>{{Cite web |last=Harding |first=Scharon |title=Belkin shows tech firms getting too comfortable with bricking customers' stuff |url=https://arstechnica.com/gadgets/2025/07/belkin-shows-tech-firms-getting-too-comfortable-with-bricking-customers-stuff/ |website=Ars Technica |date=12 Jul 2025 |access-date=17 Feb 2026 |url-status=live |archive-url=http://web.archive.org/web/20251119165125/https://arstechnica.com/gadgets/2025/07/belkin-shows-tech-firms-getting-too-comfortable-with-bricking-customers-stuff/ |archive-date=19 Nov 2025}}</ref>

[[Reddit]] discussions in r/WeMo revealed widespread customer anger:
<blockquote>''"They just guaranteed I'll never buy Belkin again. Half the light switches in my house are going to need replacing."<ref>{{Cite web |author=whitebean |title=It’s officially ending. I just got this email. Glad I started switching to Zigbee last week. |url=https://old.reddit.com/r/WeMo/comments/1lwilvc/its_officially_ending_i_just_got_this_email_glad/n2esknt/ |website=[[Reddit]] |date=10 Jul 2025 |access-date=17 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260222233607/https://old.reddit.com/r/WeMo/comments/1lwilvc/its_officially_ending_i_just_got_this_email_glad/n2esknt/ |archive-date=22 Feb 2026}}</ref>''</blockquote>

<blockquote>''"I figured it's made by a trusted brand so it would be better than using no name Amazon junk. What a joke. [...] Belkin is never getting a dollar from me again."<ref>{{Cite web
|author=ho_merjpimpson |title=It’s officially ending. I just got this email. Glad I started switching to Zigbee last week. |url=https://old.reddit.com/r/WeMo/comments/1lwilvc/its_officially_ending_i_just_got_this_email_glad/n2et52a/ |website=[[Reddit]] |date=10 Jul 2025 |access-date=17 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260222233628/https://old.reddit.com/r/WeMo/comments/1lwilvc/its_officially_ending_i_just_got_this_email_glad/n2et52a/ |archive-date=22 Feb 2026}}</ref>''</blockquote>

Users called for firmware updates enabling local control and drew parallels to digital game preservation campaigns such as the [[Stop Killing Games]] campaign.

==Technical workarounds==
While technical solutions exist for maintaining some device functionality, they require a good amount of technical expertise that most consumers lack:

*'''Apple HomeKit:''' Devices configured with HomeKit before the shutdown will continue working through Apple's ecosystem.
*'''Home Assistant:''' Open-source platform offering local control through {{Wplink|universal plug-and-play}} device discovery.
*'''Third-party firmware:''' Projects such as [https://ota.tasmota.com/tasmota/ Tasmota] enable complete device replacement, though requiring technical modification
*'''Pywemo:''' Supports joining and changing Wi-Fi settings, and local control via Wemo's local API (which is not documented by Belkin). [https://github.com/pywemo/pywemo GitHub project link]

The existence of these workarounds demonstrates that the shutdown represents a business decision rather than out of technical necessity, as devices can continue functioning locally without cloud services.

==Industry context==
The Wemo shutdown represents part of a broader pattern of IoT device abandonment affecting millions of devices globally. Similar shutdowns include:
*Google Cloud IoT Core termination (2023)
*Amazon Web Services IoT service discontinuations (2024—2026)
*Complete collapse of {{Wplink|Insteon}}'s smart home system (2022), affecting 1.3 million customers<ref>{{Cite web |last=Amadeo |first=Ron |title=Shameful: Insteon looks dead—just like its users’ smart homes |url=https://arstechnica.com/gadgets/2022/04/shameful-insteon-looks-dead-just-like-its-users-smart-homes/ |website=Ars Technica |date=18 Apr 2022 |access-date=13 Jul 2025 |url-status=live |archive-url=http://web.archive.org/web/20251213064809/https://arstechnica.com/gadgets/2022/04/shameful-insteon-looks-dead-just-like-its-users-smart-homes/ |archive-date=13 Dec 2025}}</ref>

Academic research has identified this phenomenon as ''"regulation by bricking"''<ref>{{Cite journal |last=Tusikov |first=Natasha |date=18 Jun 2019 |title=Regulation through “bricking”: private ordering in the “Internet of Things” |url=https://policyreview.info/articles/analysis/regulation-through-bricking-private-ordering-internet-things |url-status=live |journal=Internet Policy Review |volume=8 |issue=2 |doi=10.14763/2019.2.1405 |archive-url=https://web.archive.org/web/20190807232444/https://policyreview.info/articles/analysis/regulation-through-bricking-private-ordering-internet-things |archive-date=7 Aug 2019 |access-date=13 Jul 2025}}</ref>'','' a form of corporate control where manufacturers retain the ability to remotely disable devices after purchase through licensing agreements and cloud service dependencies.

==Consumer protection and regulatory response==
The incident shows the gaps in consumer protection frameworks for software-dependent devices. Current warranty laws assume hardware failure rather than service termination, creating uncertainty about whether cloud service shutdowns count as defective products.

Consumer advocacy organizations, led by Consumer Reports, have mobilized against IoT device abandonment practices, coining the term ''"software tethering"'' to describe manufacturer control over post-purchase device functionality.<ref>{{Cite web |last1=Brookman |first1=Justin |last2=Higginbotham |first2=Stacey |last3=Gutterman |first3=Lucas |display-authors=2 |title=Consumer Reports, U.S. PIRG, and 15 other groups call on FTC to create clear guidance for ‘software tethering’ |url=https://advocacy.consumerreports.org/research/group-letter-ftc-software-tethering/ |website=Consumer Reports |date=13 Jul 2025 |access-date=13 Jul 2025 |url-status=live |archive-url=http://web.archive.org/web/20251119040431/https://advocacy.consumerreports.org/research/group-letter-ftc-software-tethering/ |archive-date=19 Nov 2025}}</ref> The coalition has petitioned the [[Federal Trade Commission|FTC]] to address these practices and establish mandatory disclosure requirements for device support timelines.

===Legal action===
On 28 January 2026, ClassAction.org issued a website form for people affected by the Wemo cloud shutdown to contact them regarding a potential mass arbitration event.<ref>{{Cite web |author=
|title=Belkin Wemo End of Life Arbitration: Affected by Discontinued Belkin Wemo Support? |url=https://www.classaction.org/belkin-wemo-bricking-arbitration-lawsuit-info |website=ClassAction.org |date=28 Jan 2026 |access-date=29 Jan 2026 |url-status=live |archive-url=https://web.archive.org/web/20260129143210/https://www.classaction.org/belkin-wemo-bricking-arbitration-lawsuit-info |archive-date=29 Jan 2026}}</ref> In addition, the Sauder Schelkopf law firm launched their own investigation into the Wemo cloud shutdown.<ref>{{Cite web |author= |title=Belkin Ends Support for Wemo Smart Home Products Class Action Lawsuit Investigation |url=https://sauderschelkopf.com/investigations/belkin-ends-support-for-wemo-smart-home-products-class-action-lawsuit-investigation/ |website=Sauder Schelkopf Attorneys At Law |date=2025 |access-date=17 Feb 2026 |url-status=live |archive-url=http://web.archive.org/web/20260129144014/https://sauderschelkopf.com/investigations/belkin-ends-support-for-wemo-smart-home-products-class-action-lawsuit-investigation/ |archive-date=29 Jan 2026}}</ref>
<gallery>
File:Fettig et al. v. Belkin International, Inc. Wemo Case No. 326cv01590 Filed Feb 24 2026.pdf|Belkin (Wemo) Class Action Filing US Federal Court.
</gallery>

==See also==
*[[Planned obsolescence]]
*[[Right to repair]]

==References==
{{Reflist}}

[[Category:Belkin]]
[[Category:Wemo]]
[[Category:Internet of Things]]
[[Category:Planned obsolescence]]
[[Category:Smart home devices]]
[[Category:Ongoing events]]

Wemo

2026-06-05T18:32:00Z

Wownyc: image of a table smh

{{CompanyCargo
|Founded=2011
|Industry=Home automation
|Logo=Wemo logo.svg
|ParentCompany=Belkin
|Type=Subsidiary
|Website=https://www.belkin.com/products/wemo-smart-home/
|Description=American smart home and accessory manufacturer. In 2025, announced non-Homekit devices will cease to function.
}}

'''{{Wplink|WEMO|Wemo}}''' is a subsidiary of [[Belkin]] founded in 2011. They are known for smart home devices such as plugs and light switches that use the Apple HomeKit and Thread protocols.

==Consumer impact summary==
====User freedom====
[[File:WEMO account closure.png|thumb|right|Screenshot of account closure screen.]]
Users have to delete their account through the mobile app. This prompts a warning that Wemos cannot be controlled through the app once account data is deleted. Devices can also work using the Apple Home app, which does not require a Wemo account to set up.{{Citation needed|date=June 2026}}

====User privacy====
Since late 2023, the [https://www.belkin.com/legal/privacy-policy/ privacy policy] of Belkin and Wemo have merged, sharing the same terms with each other. The data collected on users includes account information such as email and password, device information, first and third-party [[Web cookie|cookies]], age, location, and IP address.<ref>{{Cite web |author= |title=WeMO PRIVACY POLICY |url=https://www.wemo.com/privacy-policy/ |website=Wemo |date= |access-date=29 Mar 2025 |url-status=dead |archive-url=https://web.archive.org/web/20230107062703/https://www.wemo.com/privacy-policy/#typesofinformation |archive-date=7 Jan 2023}}</ref> Belkin shares this info with marketing partners unless the user opts-out.<ref>{{Cite web |author= |title=Marketing |url=https://www.belkin.com/legal/privacy-policy/#marketing-anchor |website=[[Belkin]] |date=Jan 2024 |access-date=19 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260123140413/https://www.belkin.com/legal/privacy-policy/#marketing-anchor |archive-date=23 Jan 2026}}</ref> Users are allowed to make requests to access, withdraw consent, object, and delete most of the information Belkin has collected on them.<ref>{{Cite web |author= |title=Your Rights in relation to your Personal Information |url=https://www.belkin.com/legal/privacy-policy/#your-rights-in-relation |website=[[Belkin]] |date=Jan 2024 |access-date=29 Mar 2025 |url-status=live |archive-url=https://web.archive.org/web/20260123140413/https://www.belkin.com/legal/privacy-policy/#your-rights-in-relation |archive-date=23 Jan 2026}}</ref> Belkin states they may need to hold onto information for "Defending Belkin against legal claims" or "Needing to respond to customer complaints and queries."<ref>{{Cite web |author= |title=Retention of Personal Information |url=https://www.belkin.com/legal/privacy-policy/#retention-of |website=[[Belkin]] |date=Jan 2024 |access-date=29 Mar 2025 |url-status=live |archive-url=https://web.archive.org/web/20260123140413/https://www.belkin.com/legal/privacy-policy/#retention-of |archive-date=23 Jan 2026}}</ref>

====Business model====
The business model of Wemo is to sell smart home devices without the user paying for a subscription service. Although this may seem like a pro-consumer move, the Wemo experience has been diminished due to the lack of income streams. According to the App Store, the app once had a 3-year window without updates, which lasted between 23 February 2021 and 28 May 2024 (the current version as of 24 February 2025).<ref name="AAS">{{Cite web |author= |title=Wemo on the App Store |url=https://apps.apple.com/us/app/wemo/id511376996 |website=[[Apple]] |date=28 May 2024 |access-date=19 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20250313120121/https://apps.apple.com/us/app/wemo/id511376996 |archive-date=13 Mar 2025}}</ref>

====Market control====
Market control of Wemo has been decreasing over the years, as Wemo is only selling three devices,<ref>{{Cite web |author= |title=Wemo Smart Home |url=https://www.belkin.com/products/wemo-smart-home/ |website=[[Belkin]] |date= |access-date=29 Mar 2025 |url-status=deviated |archive-url=https://web.archive.org/web/20240225173134/https://www.belkin.com/products/wemo-smart-home/ |archive-date=25 Feb 2024}}</ref> down from nine the year prior.<ref>{{Cite web |title=Wemo Smart Home |url=https://www.belkin.com/products/wemo-smart-home/ |url-status=deviated |archive-url=https://web.archive.org/web/20230201232551/https://www.belkin.com/products/wemo-smart-home/ |archive-date=1 Feb 2023 |access-date=29 Mar 2025 |website=Belkin}}</ref>

==Incidents==

===Discontinuation of cloud service (''2026'')===
{{Excerpt|Wemo discontinuation of service}}

===DNS activity (''2024'')===
Some users of Wemo have noticed their switches connect to multiple unrelated domains, such as to CNN and [[wikipedia:Fastly|Fastly]].<ref>{{Cite web |author=sd_042 |title=Fun fact: Wemo switches act as a DNS server |url=https://old.reddit.com/r/WeMo/comments/1auslst/fun_fact_wemo_switches_act_as_a_dns_server/ |website=[[Reddit]] |date=19 Feb 2024 |access-date=29 Mar 2025 |url-status=live |archive-url=http://web.archive.org/web/20240307040322/https://old.reddit.com/r/WeMo/comments/1auslst/fun_fact_wemo_switches_act_as_a_dns_server/ |archive-date=7 Mar 2024}}</ref> Other reports mention each Wemo device making 160,000+ [[wikipedia:Domain_Name_System|DNS]] requests in a 24-hour timeframe.<ref>{{Cite web |author=D3-Doom |title=Fun fact: Wemo switches act as a DNS server |url=https://old.reddit.com/r/WeMo/comments/1auslst/fun_fact_wemo_switches_act_as_a_dns_server/ktxkqx8/ |website=[[Reddit]] |date=8 Mar 2024 |access-date=19 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260222233252/https://old.reddit.com/r/WeMo/comments/1auslst/fun_fact_wemo_switches_act_as_a_dns_server/ktxkqx8/ |archive-date=22 Feb 2026}}</ref>

===Connection issues (''2018—Present'')===
Since 2018, there have been reports of Wemo devices having some kinds of connection problem. These reports include:

* Dimmers,<ref>{{Cite web |author=boggsrays |date=28 Dec 2022 |title=The End of WeMo? |url=https://old.reddit.com/r/WeMo/comments/zwb7wr/comment/j1xqs3h/ |url-status=live |archive-url=https://web.archive.org/web/20260222233029/https://old.reddit.com/r/WeMo/comments/zwb7wr/the_end_of_wemo/j1xqs3h/ |archive-date=22 Feb 2026 |access-date=29 Mar 2025 |website=[[Reddit]]}}</ref> plugs,<ref>{{Cite web |author=Specul8 |date=14 Nov 2023 |title=WeMo in 2023. Is it dead? Probably. |url=https://old.reddit.com/r/WeMo/comments/17ur9b2/comment/k97i0dp/ |url-status=live |archive-url=https://web.archive.org/web/20260222233050/https://old.reddit.com/r/WeMo/comments/17ur9b2/wemo_in_2023_is_it_dead_probably/k97i0dp/ |archive-date=22 Feb 2026 |access-date=19 Feb 2025 |website=[[Reddit]]}}</ref> and switches,<ref>{{Cite web |author=rickatk |date=13 Jan 2023 |title=Thoughts on WEMO going into 2024? |url=https://old.reddit.com/r/WeMo/comments/18iidjr/thoughts_on_wemo_going_into_2024/m6utdkq/ |url-status=live |archive-url=https://web.archive.org/web/20260222233112/https://old.reddit.com/r/WeMo/comments/18iidjr/thoughts_on_wemo_going_into_2024/m6utdkq/ |archive-date=22 Feb 2026 |access-date=19 Feb 2026 |website=[[Reddit]]}}</ref> losing connection to networks frequently.<ref>{{Cite web |author=luisfpinto |date=21 Jun 2018 |title=The most common problems and issues with Wemo devices |url=https://old.reddit.com/r/WeMo/comments/8sv90i/the_most_common_problems_and_issues_with_wemo/ |url-status=live |archive-url=http://web.archive.org/web/20230610122822/https://old.reddit.com/r/WeMo/comments/8sv90i/the_most_common_problems_and_issues_with_wemo/ |archive-date=10 Jun 2023 |access-date=19 Feb 2026 |website=[[Reddit]]}}</ref>

* Device rules created through the Wemo app being unreliable.<ref>{{Cite web |author=-JEFF007- |date=17 Dec 2023 |title=Thoughts on WEMO going into 2024? |url=https://old.reddit.com/r/WeMo/comments/18iidjr/thoughts_on_wemo_going_into_2024/kdr6n38/ |url-status=live |archive-url=https://web.archive.org/web/20260222233136/https://old.reddit.com/r/WeMo/comments/18iidjr/thoughts_on_wemo_going_into_2024/kdr6n38/ |archive-date=22 Feb 2026 |access-date=19 Feb 2026 |website=[[Reddit]]}}</ref>

* Wemo cloud going offline offline, with users being led to 404 pages.<ref>{{Cite web |author= |date=12 Dec 2022 |title=Belkin Wemo is the worst! The App is full of bugs, the cloud is "drifted away" every other day, and even their link to the "more info" is dead! |url=https://old.reddit.com/r/WeMo/comments/zkd9xc/belkin_wemo_is_the_worst_the_app_is_full_of_bugs/ |url-status=live |archive-url=http://web.archive.org/web/20221213062324/https://old.reddit.com/r/WeMo/comments/zkd9xc/belkin_wemo_is_the_worst_the_app_is_full_of_bugs/ |archive-date=13 Dec 2022 |access-date=19 Feb 2026 |website=[[Reddit]]}}</ref>

* Amazon Alexa and [[Google]] home integrations not working for periods of time are also common.<ref>{{Cite web |author=JonSnowWho |date=17 Jun 2025 |title=Google is trying... |url=https://old.reddit.com/r/WeMo/comments/1le3til/google_is_trying/ |url-status=live |archive-url=https://web.archive.org/web/20260222233206/https://old.reddit.com/r/WeMo/comments/1le3til/google_is_trying/ |archive-date=22 Feb 2026 |access-date=19 Feb 2026 |website=[[Reddit]]}}</ref>
* Suddenly devices restricted to only work with Apple Homekit.<ref>{{Cite web |author=XYZZY_1002 |date=26 Nov 2024 |title=Wemo Plugs and some Switches/Dimmers suddenly no longer detected |url=https://old.reddit.com/r/WeMo/comments/1h0ec6v/wemo_plugs_and_some_switchesdimmers_suddenly_no/ |url-status=live |archive-url=https://web.archive.org/web/20260222233228/https://old.reddit.com/r/WeMo/comments/1h0ec6v/wemo_plugs_and_some_switchesdimmers_suddenly_no/ |archive-date=22 Feb 2026 |access-date=19 Feb 2026 |website=[[Reddit]]}}</ref>

===Security vulnerabilities (''2013—2023'')===
On 5 November 2013, Wemo updated its API to prevent XML injection attacks published by a CERT advisory.<ref>{{Cite web |author= |date= |title=Wemo® and Security |url=https://www.belkin.com/support-article/?articleNum=80322 |url-status=live |archive-url=https://web.archive.org/web/20230926192207/https://www.belkin.com/support-article/?articleNum=80322 |archive-date=26 Sep 2023 |access-date=19 Feb 2026 |website=[[Belkin]]}}</ref>

On 16 May 2023, multiple websites{{Clarify|which}} reported a Sternum study regarding a buffer overflow vulnerability in the Wemo Mini Smart Plug V2.<ref>{{Cite web |last1=Serper |first1=Amit |last2=Yakar |first2=Reuven |date=16 May 2023 |title=‘FriendlyName’ Buffer Overflow Vulnerability in Wemo Smart Plug V2 |url=https://sternumiot.com/iot-blog/mini-smart-plug-v2-vulnerability-buffer-overflow/ |url-status=live |archive-url=https://web.archive.org/web/20230516160431/https://sternumiot.com/iot-blog/mini-smart-plug-v2-vulnerability-buffer-overflow/ |archive-date=16 May 2023 |access-date=19 Feb 2026 |website=Sternum}}</ref> The study mentions the device could be exploited through a program called pyWemo<ref>{{Cite web |last=Lakshmanan |first=Ravie |date=17 May 2023 |title=Serious Unpatched Vulnerability Uncovered in Popular Belkin Wemo Smart Plugs |url=https://thehackernews.com/2023/05/serious-unpatched-vulnerability.html |url-status=live |archive-url=https://web.archive.org/web/20230517155641/https://thehackernews.com/2023/05/serious-unpatched-vulnerability.html |archive-date=17 May 2023 |access-date=19 Feb 2026 |website=The Hacker News}}</ref> and potentially through cloud controls.<ref>{{Cite web |last=Davis |first=Wes |date=16 May 2023 |title=PSA: time to recycle your old Wemo smart plugs (if you haven’t already) |url=https://www.theverge.com/2023/5/16/23725290/wemo-smart-plug-v2-smart-home-security-vulnerability |url-status=live |archive-url=https://web.archive.org/web/20230517021155/https://www.theverge.com/2023/5/16/23725290/wemo-smart-plug-v2-smart-home-security-vulnerability |archive-date=17 May 2023 |access-date=29 Mar 2025 |website=The Verge}}</ref> In their official response, Wemo stated "we believe that bad actors cannot exploit this vulnerability unless they have access to the user's local network",<ref>{{Cite web |author=WEMOcares |date=17 May 2023 |title=WEMOcares on X |url=https://nitter.catsarch.com/WEMOcares/status/1658963426230562819 |url-status=live |archive-url=https://web.archive.org/web/20260324184234/https://nitter.catsarch.com/WEMOcares/status/1658963426230562819 |archive-date=24 Mar 2026 |access-date=19 Mar 2025 |website=[[X]]}}</ref> and "We discontinued the Wemo Mini Smart Plug V2 (F7C063) in 2020"<ref>{{Cite web |author=WEMOcares |date=17 May 2023 |title=WEMOcares on X |url=https://nitter.catsarch.com/WEMOcares/status/1658963635882938374 |url-status=live |archive-url=https://web.archive.org/web/20260324184237/https://nitter.catsarch.com/WEMOcares/status/1658963635882938374 |archive-date=24 Mar 2026 |access-date=19 Feb 2026 |website=[[X]]}}</ref> despite not making this information publicly available prior. During this report, the Wemo app hadn't been updated in two years, with the most recent update being on February 23, 2021, as previously mentioned.<ref name="AAS" />

==Products==
;Dimmers
*Wemo Smart Dimmer<ref>{{Cite web |author= |title=Wemo Smart Dimmer (WDS070) |url=https://www.belkin.com/smart-dimmer/P-WDS070.html |website=[[Belkin]] |date= |access-date= |url-status=dead |archive-url=https://web.archive.org/web/20221130043724/https://www.belkin.com/smart-dimmer/P-WDS070.html |archive-date=30 Nov 2022}}</ref>
*Wemo WiFi Smart Dimmer<ref>{{Cite web |author= |title=Wemo WiFi Smart Dimmer 2-Pack (WDS060-BD2) |url=https://www.belkin.com/wifi-smart-dimmer/P-WDS060.html |website=[[Belkin]] |date= |access-date= |url-status=dead |archive-url=https://web.archive.org/web/20221129001529/https://www.belkin.com/wifi-smart-dimmer/P-WDS060.html |archive-date=29 Nov 2022}}</ref>

;Doorbells
*Wemo Smart Video Doorbell<ref>{{Cite web |author= |title=Wemo Smart Video Doorbell (WDC010) |url=https://www.belkin.com/p/smart-video-doorbell/WDC010.html |website=[[Belkin]] |date= |access-date= |url-status=dead |archive-url=https://web.archive.org/web/20250219094510/https://www.belkin.com/p/smart-video-doorbell/WDC010.html |archive-date=19 Feb 2025
}}</ref>

;Light switches
*Wemo Smart Light Switch with Thread<ref>{{Cite web |author= |title=Wemo Smart Light Switch with Thread (WLS0503) |url=https://www.belkin.com/p/smart-light-switch-with-thread/WLS0503.html |website=[[Belkin]] |date= |access-date=17 Mar 2025 |url-status=deviated |archive-url=https://web.archive.org/web/20250121215711/https://www.belkin.com/p/smart-light-switch-with-thread/WLS0503.html |archive-date=21 Jan 2025}}</ref>
*Wemo WiFi Smart Light Switch<ref>{{Cite web |author= |title=Wemo WiFi Smart Light Switch (WLS040-CA) |url=https://www.belkin.com/wifi-smart-light-switch/WLS040-CA.html |website=[[Belkin]] |date= |access-date= |url-status=deviated |archive-url=https://web.archive.org/web/20221130045654/https://www.belkin.com/wifi-smart-light-switch/WLS040-CA.html |archive-date=30 Nov 2022}}</ref>
*Wemo Smart Light Switch 3-Way<ref>{{Cite web |author= |title=Wemo Smart Light Switch 3-Way 2-Pack (WLS0403-BDL) |url=https://www.belkin.com/smart-light-switch-3-way/P-WLS0403.html |website=[[Belkin]] |date= |access-date= |url-status=deviated |archive-url=https://web.archive.org/web/20221129145512/https://www.belkin.com/smart-light-switch-3-way/P-WLS0403.html |archive-date=29 Nov 2022}}</ref>

;Plugs
*Wemo Smart Plug with Thread<ref>{{Cite web |author= |title=Wemo Smart Plug with Thread (WSP100) |url=https://www.belkin.com/smart-plug-with-thread/WSP100.html |website=[[Belkin]] |date= |access-date= |url-status=dead |archive-url=https://web.archive.org/web/20231002205640/https://www.belkin.com/smart-plug-with-thread/WSP100.html |archive-date=2 Oct 2023}}</ref>
*Wemo WiFi Smart Outdoor Plug<ref>{{Cite web |author= |title=Wemo WiFi Smart Outdoor Plug (WSP090) |url=https://www.belkin.com/wifi-smart-outdoor-plug/WSP090.html |website=[[Belkin]] |date= |access-date= |url-status=deviated |archive-url=https://web.archive.org/web/20221201141200/https://www.belkin.com/wifi-smart-outdoor-plug/WSP090.html |archive-date=1 Dec 2022}}</ref>

;Scene controller
*Wemo Scene Controller with Thread<ref>{{Cite web |author= |title=Wemo Scene Controller with Thread (WSC010) |url=https://www.belkin.com/p/scene-controller-with-thread/WSC010.html |website=[[Belkin]] |date= |access-date=19 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20250304111821/https://www.belkin.com/p/scene-controller-with-thread/WSC010.html |archive-date=4 Mar 2025}}</ref>

==References==
{{Reflist}}

[[Category:Wemo]]
[[Category:Belkin]]

Wemo discontinuation of service

2026-06-05T18:31:29Z

Wownyc: /* Devices affected */ add table of affected devices

{{IncidentCargo
|Company=Belkin
|StartDate=10 July 2025
|EndDate=
|Status=
|ProductLine=Wemo
|Product=
|ArticleType=
|Type=
|Description=
}}{{OngoingEvent}}

[[Belkin]] [[Wemo]] smart home devices require cloud connectivity to work. On 10 July 2025, Belkin announced the shutdown of cloud services supporting most Wemo devices, effective 31 January 2026.<ref name=":2">{{Cite web |title=Belkin Official Support - Wemo Support Ending – What You Need to Know |url=https://www.belkin.com/support-article/?articleNum=335419 |url-status=live |archive-url=https://web.archive.org/web/20250711172157/https://www.belkin.com/support-article/?articleNum=335419 |date=2025-07-10 |access-date=2025-07-13 |archive-date=11 Jul 2025 |website=Belkin Official Support}}</ref> These devices remain for sale on Belkin's Amazon WeMo store<ref>{{Cite web |title=Amazon.com: Wemo Smart Plug with Thread - Smart Outlet for Apple HomeKit - Smart Home Products, Smart Home Lighting, Smart Home Gadgets - Homekit Smart Plug - Tech Gifts - Works W/ Apple iPhone, Easy NFC Set Up : Tools & Home Improvement |url=https://www.amazon.com/Wemo-Smart-Plug-Thread-Products/dp/B09T4S3QKC |url-status=live |archive-url=http://web.archive.org/web/20260220201917/https://www.amazon.com/Wemo-Smart-Plug-Thread-Products/dp/B09T4S3QKC |archive-date=20 Feb 2026 |access-date=2025-07-13 |website=[[Amazon]]}}</ref> and advertising them as working with Google, Alexa, & more.<ref name=":02">{{Cite web |title=Amazon.com: Wemo |url=https://www.amazon.com/stores/Wemo/page/E33F6EA2-93FC-48CD-8BF6-EE10D5398795 |url-status=live |archive-url=https://web.archive.org/web/20260227172544/https://www.amazon.com/stores/Wemo/page/E33F6EA2-93FC-48CD-8BF6-EE10D5398795 |archive-date=2026-02-27 |access-date=2025-07-13 |website=Amazon.com: Wemo}}</ref><ref>{{Cite web |last=Preston |first=Dominic |date=2025-07-11 |title=Belkin is ending support for nearly all its Wemo smart home devices |url=https://www.theverge.com/news/705136/belkin-wemo-smart-home-support-ending-homekit-thread |url-status=live |archive-url=https://web.archive.org/web/20250711204531/https://www.theverge.com/news/705136/belkin-wemo-smart-home-support-ending-homekit-thread |archive-date=11 Jul 2025 |access-date=2025-07-14 |website=The Verge |language=en-US}}</ref>

This shutdown will disable remote access and automation functionality for 27+ device models sold between August 2015 and November 2023, affecting thousands of customers who purchased these devices as permanent smart home solutions. The incident is one example of a broader trend of IoT device abandonment and {{Wplink|Tethering|software tethering}} practices that enable manufacturers to remotely disable purchased products.

==Background==
First launched in 2011, Wemo is a smart home product line developed by Belkin. The product line includes smart plugs, light switches, motion sensors, dimmers, and connected appliances like coffee makers and humidifiers. These devices were marketed as one-time purchases with cloud features, app control, and integration with voice assistants including Amazon Alexa, Google Home, and Apple HomeKit.

Wemo gained popularity for its convenience, ease of use, and broad compatibility with voice assistants and cloud automation programs. Devices were sold with '''no disclosed end-of-life timeline for cloud functionality'''.

==2025 shutdown announcement==
[[File:Belkin email Wemo shutdown.jpg|alt=Email from Belkin about Wemo shutdown|thumb|right|Email notification sent to Wemo customers about the January 2026 shutdown]]

On 10 July 2025, Belkin created a support page and began e-mailing customers informing them that most Wemo devices would stop working on 31 January 2026.<ref name=":2" /> The company described this as a ''"difficult decision"'' to shut down cloud services for Wemo products, stating they needed to ''"focus our resources on different parts of the Belkin business."''

The shutdown affects any feature requiring cloud connectivity, including:
*Wemo app functionality
*Amazon Alexa integration
*Google Home integration
*Remote access capabilities
*Automation and scheduling features
*Technical support

===Devices affected===
This shutdown impacts 24 different device models spanning smart plugs, switches, specialty appliances, and sensors sold between August 2015 and November 2023, including:
*Wemo Smart Plug (multiple generations)
*Wemo Smart Light Switches
*Wemo In-Wall Dimmers and Switches
*Wemo connected appliances (smart crockpots, air purifiers, coffee makers, humidifiers)
*Wemo Motion Sensors and LED lighting kits
*Wemo Outdoor Smart Plug
*Wemo Mini Smart Plug
*Various specialty devices and older models

Only four Thread-based[''Clarify''] models will continue functioning through Apple HomeKit after the shutdown date, and only if configured prior to 31 January 2026.
{| class="wikitable sortable"
! align="left" |'''SKU'''
! align="left" |'''Description'''
! align="left" |Last Sold Units Date
! align="left" |'''Warranty'''
|-
| align="left" |F7C031
| align="left" |Wemo Link
| align="left" |2015-08
| align="left" |2-Year
|-
| align="left" |F7C046
| align="left" |Wemo Humidifier
| align="left" |2015-12
| align="left" |3-Year
|-
| align="left" |F7C045
| align="left" |Wemo CrockPot
| align="left" |2016-04
| align="left" |1-Year
|-
| align="left" |F7C048
| align="left" |Wemo Heater B
| align="left" |2016-06
| align="left" |3-Year
|-
| align="left" |F7C049
| align="left" |Wemo Air Purifier
| align="left" |2016-07
| align="left" |3-Year
|-
| align="left" |F7C047
| align="left" |Wemo Heater A
| align="left" |2016-09
| align="left" |3-Year
|-
| align="left" |F7C050
| align="left" |Wemo Coffee Maker (Mr. Coffee)
| align="left" |2016-12
| align="left" |1-Year
|-
| align="left" |F8J007
| align="left" |Wi-Fi Baby Monitor
| align="left" |2017-06
| align="left" |1-Year
|-
| align="left" |F5Z0489
| align="left" |Wemo LED Lighting Bundle
| align="left" |2017-09
| align="left" |2-Year
|-
| align="left" |F7C028
| align="left" |Wemo Motion Sensor
| align="left" |2017-09
| align="left" |2-Year
|-
| align="left" |F5Z0340
| align="left" |Wemo Switch + Motion Sensor
| align="left" |2017-10
| align="left" |2-Year
|-
| align="left" |F7C043
| align="left" |Wemo Maker Module
| align="left" |2017-11
| align="left" |2-Year
|-
| align="left" |F7C033
| align="left" |Wemo Zigbee Bulb, E27
| align="left" |2018-03
| align="left" |2-Year
|-
| align="left" |F7C061
| align="left" |Wemo Insight v2
| align="left" |2018-07
| align="left" |1-Year
|-
| align="left" |F7C027
| align="left" |Wemo Switch
| align="left" |2019-01
| align="left" |2-Year
|-
| align="left" |F7C062
| align="left" |Wemo Light Switch v2
| align="left" |2019-11
| align="left" |1-Year
|-
| align="left" |F7C029
| align="left" |Wemo Insight
| align="left" |2020-06
| align="left" |2-Year
|-
| align="left" |WLS0403
| align="left" |Wemo Smart Light Switch 3-Way
| align="left" |2021-09
| align="left" |3-Year
|-
| align="left" |WSP070
| align="left" |Wemo Mini Smart Plug
| align="left" |2022-07
| align="left" |3-Year
|-
| align="left" |WDS060
| align="left" |Wemo Wi-Fi Smart Light Switch w/ Dimmer
| align="left" |2022-09
| align="left" |3-Year
|-
| align="left" |WLS040
| align="left" |Wemo Smart Light Switch
| align="left" |2022-09
| align="left" |3-Year
|-
| align="left" |F7C064
| align="left" |Wemo HomeKit
| align="left" |2022-09
| align="left" |1-Year
|-
| align="left" |F7C059
| align="left" |Wemo Dimmer Light Switch
| align="left" |2022-11
| align="left" |1-Year
|-
| align="left" |F7C063
| align="left" |Wemo Mini Plugin Switch
| align="left" |2022-12
| align="left" |3-Year
|-
| align="left" |F7C030
| align="left" |Wemo Light Switch
| align="left" |2022-12
| align="left" |2-Year
|-
| align="left" |WSP090
| align="left" |Wemo Outdoor Plug
| align="left" |2023-05
| align="left" |3-Year
|-
| align="left" |WSP080
| align="left" |Wemo Mini Smart Plug
| align="left" |2023-11
| align="left" |3-Year
|}

===Timing and warranty issues===
Devices with three-year warranties sold as recently as November 2023 will lose core functionality before warranty expiration. Belkin offers only partial refunds for devices still under warranty after the shutdown date, requiring consumers to wait until their devices are non-functional before seeking compensation.

==Belkin suggests disposing of the devices==
Belkin's official response recommends that customers dispose of out-of-warranty devices at authorized e-waste recycling centers, despite the devices remaining physically functional:<ref name=":2" />
<blockquote>''"For any Wemo devices you have that are out of warranty, will not work with HomeKit or if you are unable to use HomeKit, we recommend disposing of these devices at an authorized e-waste recycling center."''</blockquote>

This recommendation is particularly controversial for in-wall switches and dimmers that are permanently installed in customers' homes. One Ars Technica forum user suggested ''"boxing them up and shipping them directly to Belkin corporate headquarters."''<ref>{{Cite web |author=ReaderBot |title=Belkin shows tech firms getting too comfortable with bricking customers' stuff |url=https://arstechnica.com/civis/threads/belkin-shows-tech-firms-getting-too-comfortable-with-bricking-customers%E2%80%99-stuff.1508302/post-43842885 |website=Ars Technica |date=11 Jul 2025 |access-date=17 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260222233540/https://arstechnica.com/civis/threads/belkin-shows-tech-firms-getting-too-comfortable-with-bricking-customers%E2%80%99-stuff.1508302/#post-43842885 |archive-date=22 Feb 2026}}</ref>

==Continued sales of soon-to-be-dead products==
Despite announcing the shutdown, Belkin continues selling affected Wemo devices through [[Amazon]] and other retailers without disclosing the impending service termination.<ref name=":0" /> As of July 2025, the Wemo Amazon store prominently displays compatibility claims with Amazon Alexa, Google Assistant, and other platforms that will stop functioning in six months.

<gallery mode="slideshow">
File:Belkin still selling Wemo dimmer.jpg|Belkin light switch still for sale despite announced functionality loss.<ref name=":7">{{Cite web |title=WeMo Smart Light Switch 2ND Gen |url=https://www.amazon.com/WeMo-Smart-Light-Switch-2ND/dp/B07RT8H9WH |archive-url=http://web.archive.org/web/20250904072417/https://www.amazon.com/WeMo-Smart-Light-Switch-2ND/dp/B07RT8H9WH |archive-date=4 Sep 2025|access-date=13 Jul 2025 |website=[[Amazon]]}}</ref>
File:Amazon store Belkin Wemo works.jpg|Belkin's Amazon store advertising platform compatibility despite planned termination.<ref name=":0" />
</gallery>

==Consumer response and criticism==
===Immediate reaction===
Customer response was swift and negative, with users expressing feelings of abandonment and frustration over recent purchases becoming obsolete.<ref>{{Cite web |author= |title=Wemo - Apps on Google Play |url=https://play.google.com/store/apps/details?id=com.belkin.wemoandroid |website=[[Google]] |date= |access-date=17 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260109061920/https://play.google.com/store/apps/details?id=com.belkin.wemoandroid |archive-date=9 Jan 2026}}</ref> The company provided only six months of notice for a shutdown affecting fourteen years of product sales.

===Technology community backlash===

Ars Technica's coverage criticized Belkin's move as reflecting an industry that ''"has grown too comfortable with bricking customers' stuff"'' without offering adequate recourse or transparency.<ref>{{Cite web |last=Harding |first=Scharon |title=Belkin shows tech firms getting too comfortable with bricking customers' stuff |url=https://arstechnica.com/gadgets/2025/07/belkin-shows-tech-firms-getting-too-comfortable-with-bricking-customers-stuff/ |website=Ars Technica |date=12 Jul 2025 |access-date=17 Feb 2026 |url-status=live |archive-url=http://web.archive.org/web/20251119165125/https://arstechnica.com/gadgets/2025/07/belkin-shows-tech-firms-getting-too-comfortable-with-bricking-customers-stuff/ |archive-date=19 Nov 2025}}</ref>

[[Reddit]] discussions in r/WeMo revealed widespread customer anger:
<blockquote>''"They just guaranteed I'll never buy Belkin again. Half the light switches in my house are going to need replacing."<ref>{{Cite web |author=whitebean |title=It’s officially ending. I just got this email. Glad I started switching to Zigbee last week. |url=https://old.reddit.com/r/WeMo/comments/1lwilvc/its_officially_ending_i_just_got_this_email_glad/n2esknt/ |website=[[Reddit]] |date=10 Jul 2025 |access-date=17 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260222233607/https://old.reddit.com/r/WeMo/comments/1lwilvc/its_officially_ending_i_just_got_this_email_glad/n2esknt/ |archive-date=22 Feb 2026}}</ref>''</blockquote>

<blockquote>''"I figured it's made by a trusted brand so it would be better than using no name Amazon junk. What a joke. [...] Belkin is never getting a dollar from me again."<ref>{{Cite web
|author=ho_merjpimpson |title=It’s officially ending. I just got this email. Glad I started switching to Zigbee last week. |url=https://old.reddit.com/r/WeMo/comments/1lwilvc/its_officially_ending_i_just_got_this_email_glad/n2et52a/ |website=[[Reddit]] |date=10 Jul 2025 |access-date=17 Feb 2026 |url-status=live |archive-url=https://web.archive.org/web/20260222233628/https://old.reddit.com/r/WeMo/comments/1lwilvc/its_officially_ending_i_just_got_this_email_glad/n2et52a/ |archive-date=22 Feb 2026}}</ref>''</blockquote>

Users called for firmware updates enabling local control and drew parallels to digital game preservation campaigns such as the [[Stop Killing Games]] campaign.

==Technical workarounds==
While technical solutions exist for maintaining some device functionality, they require a good amount of technical expertise that most consumers lack:

*'''Apple HomeKit:''' Devices configured with HomeKit before the shutdown will continue working through Apple's ecosystem.
*'''Home Assistant:''' Open-source platform offering local control through {{Wplink|universal plug-and-play}} device discovery.
*'''Third-party firmware:''' Projects such as [https://ota.tasmota.com/tasmota/ Tasmota] enable complete device replacement, though requiring technical modification
*'''Pywemo:''' Supports joining and changing Wi-Fi settings, and local control via Wemo's local API (which is not documented by Belkin). [https://github.com/pywemo/pywemo GitHub project link]

The existence of these workarounds demonstrates that the shutdown represents a business decision rather than out of technical necessity, as devices can continue functioning locally without cloud services.

==Industry context==
The Wemo shutdown represents part of a broader pattern of IoT device abandonment affecting millions of devices globally. Similar shutdowns include:
*Google Cloud IoT Core termination (2023)
*Amazon Web Services IoT service discontinuations (2024—2026)
*Complete collapse of {{Wplink|Insteon}}'s smart home system (2022), affecting 1.3 million customers<ref>{{Cite web |last=Amadeo |first=Ron |title=Shameful: Insteon looks dead—just like its users’ smart homes |url=https://arstechnica.com/gadgets/2022/04/shameful-insteon-looks-dead-just-like-its-users-smart-homes/ |website=Ars Technica |date=18 Apr 2022 |access-date=13 Jul 2025 |url-status=live |archive-url=http://web.archive.org/web/20251213064809/https://arstechnica.com/gadgets/2022/04/shameful-insteon-looks-dead-just-like-its-users-smart-homes/ |archive-date=13 Dec 2025}}</ref>

Academic research has identified this phenomenon as ''"regulation by bricking"''<ref>{{Cite journal |last=Tusikov |first=Natasha |date=18 Jun 2019 |title=Regulation through “bricking”: private ordering in the “Internet of Things” |url=https://policyreview.info/articles/analysis/regulation-through-bricking-private-ordering-internet-things |url-status=live |journal=Internet Policy Review |volume=8 |issue=2 |doi=10.14763/2019.2.1405 |archive-url=https://web.archive.org/web/20190807232444/https://policyreview.info/articles/analysis/regulation-through-bricking-private-ordering-internet-things |archive-date=7 Aug 2019 |access-date=13 Jul 2025}}</ref>'','' a form of corporate control where manufacturers retain the ability to remotely disable devices after purchase through licensing agreements and cloud service dependencies.

==Consumer protection and regulatory response==
The incident shows the gaps in consumer protection frameworks for software-dependent devices. Current warranty laws assume hardware failure rather than service termination, creating uncertainty about whether cloud service shutdowns count as defective products.

Consumer advocacy organizations, led by Consumer Reports, have mobilized against IoT device abandonment practices, coining the term ''"software tethering"'' to describe manufacturer control over post-purchase device functionality.<ref>{{Cite web |last1=Brookman |first1=Justin |last2=Higginbotham |first2=Stacey |last3=Gutterman |first3=Lucas |display-authors=2 |title=Consumer Reports, U.S. PIRG, and 15 other groups call on FTC to create clear guidance for ‘software tethering’ |url=https://advocacy.consumerreports.org/research/group-letter-ftc-software-tethering/ |website=Consumer Reports |date=13 Jul 2025 |access-date=13 Jul 2025 |url-status=live |archive-url=http://web.archive.org/web/20251119040431/https://advocacy.consumerreports.org/research/group-letter-ftc-software-tethering/ |archive-date=19 Nov 2025}}</ref> The coalition has petitioned the [[Federal Trade Commission|FTC]] to address these practices and establish mandatory disclosure requirements for device support timelines.

===Legal action===
On 28 January 2026, ClassAction.org issued a website form for people affected by the Wemo cloud shutdown to contact them regarding a potential mass arbitration event.<ref>{{Cite web |author=
|title=Belkin Wemo End of Life Arbitration: Affected by Discontinued Belkin Wemo Support? |url=https://www.classaction.org/belkin-wemo-bricking-arbitration-lawsuit-info |website=ClassAction.org |date=28 Jan 2026 |access-date=29 Jan 2026 |url-status=live |archive-url=https://web.archive.org/web/20260129143210/https://www.classaction.org/belkin-wemo-bricking-arbitration-lawsuit-info |archive-date=29 Jan 2026}}</ref> In addition, the Sauder Schelkopf law firm launched their own investigation into the Wemo cloud shutdown.<ref>{{Cite web |author= |title=Belkin Ends Support for Wemo Smart Home Products Class Action Lawsuit Investigation |url=https://sauderschelkopf.com/investigations/belkin-ends-support-for-wemo-smart-home-products-class-action-lawsuit-investigation/ |website=Sauder Schelkopf Attorneys At Law |date=2025 |access-date=17 Feb 2026 |url-status=live |archive-url=http://web.archive.org/web/20260129144014/https://sauderschelkopf.com/investigations/belkin-ends-support-for-wemo-smart-home-products-class-action-lawsuit-investigation/ |archive-date=29 Jan 2026}}</ref>
<gallery>
File:Fettig et al. v. Belkin International, Inc. Wemo Case No. 326cv01590 Filed Feb 24 2026.pdf|Belkin (Wemo) Class Action Filing US Federal Court.
</gallery>

==See also==
*[[Planned obsolescence]]
*[[Right to repair]]

==References==
{{Reflist}}

[[Category:Belkin]]
[[Category:Wemo]]
[[Category:Internet of Things]]
[[Category:Planned obsolescence]]
[[Category:Smart home devices]]
[[Category:Ongoing events]]