Mercury, a Stellar ecosystem runtime platform, is shifting to a Light Client deployment model that unbundles data sourcing, execution, and delivery into modular, open-source components. This redesign reduces operational overhead while preserving Mercury's Zephyr and Retroshades runtime technology and enabling third-party infrastructure operators to run Mercury services independently.
Mercury is announcing a strategic pivot to Mercury Light Clients, a new deployment architecture that decouples centralized infrastructure dependencies from the core runtime. After 3-4 years of development and a period of reassessment, the team identified that maintaining a complex, feature-heavy backend was creating operational burden and slowing iteration. The Light Client model unbundles data feeds, execution runtime (Zephyr and Retroshades), and operators into replaceable, pluggable components. All code is open-sourced, enabling redundancy, flexibility, and third-party operators to run Mercury services. Key improvements include faster shipping, safer experimentation, reduced DevOps overhead, and renewed focus on Stellar research. The team is actively seeking infrastructure operators to deploy Mercury Light Clients as services.
