# Particle Mesh update — a note from the CEO **URL:** \ **Category:** Particle Updates\ **Created:** [January 28, 2020, 7:19pm UTC](https://community.particle.io/t/particle-mesh-update-a-note-from-the-ceo/54394 "2020-01-28T19:19:24Z")\ **Posts on this page:** 1\ **Showing post:** 81
**Author:** ![will](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/will/32/23374_2.png) [@will](https://community.particle.io/u/will)\ **Post date:** [January 29, 2020, 10:15pm UTC](https://community.particle.io/t/particle-mesh-update-a-note-from-the-ceo/54394/81 "2020-01-29T22:15:17Z")
> [@kenmacd](#): > > As a company that creates hardware I think it’s important that people know that hardware will be available when replacements are needed. I appreciate that you’ve open-sourced the design files and am hopeful someone creates a xenon-clone. I’d much rather buy from Particle though. Thanks for your feedback, and I really appreciate that you have been satisfied by the quality of our hardware. Ultimately, though, our goal is to assist customers in building products that connect to the Internet. The Particle development model, which includes key tools like OTA updates, device vitals, and device messaging, relies on a managed connection back to the Particle Cloud. Without a persistent Cloud connection to support these features, much of the value of the Particle platform is eroded for that device. In other words, Xenons without a Particle Mesh backhaul to our Cloud no longer meet the bar that we've set for "first class" Particle devices. We feel there are many companies that can build high quality development kits for bluetooth chips like the nRF52840, and want instead to use our expertise to focus on making the deployment and management of connected products as easy as possible for our customers. --- _[View the full topic](https://community.particle.io/t/particle-mesh-update-a-note-from-the-ceo/54394)._