Skip to main content

Member Case Study: Aloxy Leverages Eclipse Foundation Membership to Build its Petro-Chemical Business

At the Eclipse Foundation, we’ve seen companies from all around the world, from different industries, find value in open source software. Aloxy, the subject of our latest member case study, has discovered that adopting open source components helped them focus on the unique aspects of their products, and increase their time to market.

“Our customers like the idea that we’re not reinventing all of the technologies ourselves, and that we’re using and participating in open source projects that are governed by a well-known, independent foundation,” said Glenn Ergeerts, Aloxy’s co-founder and chief technology officer.

Aloxy is an Industrial IoT firm based in Antwerp (Belgium) that primarily works with clients in the petrochemical industry. The company creates infrastructure sensors that monitor the positions of critical valves and send the data back to the Aloxy IIoT Hub for processing and analysis. To build their solutions, Aloxy has adopted two Eclipse IoT projects, Eclipse Hono and Eclipse Ditto.

Aloxy’s open source strategy has proved to be working. “Several large oil and gas multinationals are hosting our software in their private cloud and connecting multiple locations to it,” Ergeerts says. “They feel comfortable enough with our software that they’re willing to connect it to their global architectures. And they’re happy we’re using open source components that can be deployed in a cloud native way without locking them into a specific cloud vendor.”

While there was a learning curve to adopting these technologies, Ergeerts says the decision to leverage stable and secure open source components was a “no-brainer,” and that the company will continue to build on the security, stability, and scalability they have today.

For more insight into Aloxy’s story, read the case study.

To learn more about the benefits of Eclipse Foundation membership, visit our membership page.

Share Your Member Experiences in a Case Study

Our member case studies help companies who are considering membership in the Eclipse Foundation understand the business benefits that can be gained.

If you would like to share insight into your experiences and business evolution as an Eclipse Foundation member, please let us know. All Eclipse Foundation members are welcome to participate in our member case study initiative.

To get involved, email marketing@eclipse.org.

Content You Can Reuse

In the spirit of open source, we’re publishing all of our member case studies under the Creative Commons Attribution 4.0 International (CC BY 4.0) license. As long as you provide attribution according to the terms of the license, you can:
  • Copy and redistribute the case study content in any medium or format.
  • Adapt, transform, and build on the material for any purpose.

Read More Eclipse Foundation Case Studies

If you haven’t read our other case studies, be sure to check them out!

Comments

Popular posts from this blog

Eclipse IDE for Embedded Developers Now Runs on the Raspberry Pi!

The Eclipse IDE is the project that started it all for the Eclipse Foundation . From the beginning, Eclipse IDE was meant to run on multiple platforms; it now supports Linux, Mac OS and Microsoft Windows. Since it is written in Java, it also supports multiple processor architectures. However, support for 32-bit architectures has been dropped in version 2018-12. This meant recent versions of the IDE would not run on the Raspberry Pi anymore. The introduction of the Raspberry Pi 4 in June 2019 gave hope to Eclipse on Pi fans. With its 64-bit quad core ARM Cortex-A72, the Pi 4 was a good hardware platform to work with. It became even more attractive in May 2020, with the introduction of the 8Gb variant. The Eclipse community took notice of those developments. Version 2020-09 of Eclipse IDE now ships with experimental support for 64-bit ARM (aarch64) on Linux.  Those developments mean embedded and IoT developers can now work on the Raspberry Pi 4 by installing the plugins provided by ...

Sparkplug: From Specification to Standard

This week, the Eclipse Foundation announced that the Sparkpug® 3.0 specification has been published as an International Standard. That sounds impressive. But what does it mean, exactly? And how will this impact the evolution of Sparkplug? To answer this question, let’s take a step back and consider what standards are. The technology industry loves standards. For example, USB is a set of standards managed by the USB Implementers Forum, Inc. (USB-IF), a non-profit corporation founded by the companies that developed the USB specification. The Eclipse Foundation describes Jakarta EE as a standard: a set of  specifications for enterprise Java application development. In the IoT and Industrial Automation world, OASIS Open also presents the MQTT protocol as a standard. However, standards play a much more pervasive role in society. There are standards for building homes and others that define how cars should work. Standards permeate our lives. To understand the significance of this ...

A Robotic Dream Team: ROS 2 and Cyclone DDS

The Eclipse Cyclone DDS team has been hard at work recently ; this got them noticed in a big way. Open Robotics recently declared that Eclipse Cyclone DDS will be a tier one middleware in ROS 2 Foxy Fitzroy! Eclipse Cyclone DDS, an implementation of the Data Distribution Service standard under the stewardship of the DDS Foundation and the Object Management Group (OMG), is a project of the Eclipse IoT and OpenADx working groups. Some of the key benefits of Cyclone DDS include: Secure ROS 2 (SROS2) integration & testing contributed by Eclipse IoT member Canonical .  Implementation of DDS Security contributed, tested, optimized and ready for ROS users. The team backported this feature to the ROS 2 Dashing and Eloquent releases! Full coverage of QoS supported by ROS including lifespan and deadline  New high-speed RMW serializer contributed by Rover Robotics Ability to discover a single robot among a swarm of 1,000+ (thanks to iRobot for the use case!) Too many performan...