Dear IoT WG,
I’d like to share an important milestone for the Eclipse ioFog project.
As some of you may know, the project had been inactive for some time. A couple of months ago, I was appointed as project lead, and since then we’ve consolidated all improvements from theÂ
Datasance codebase into the ioFog repository. With that,
Eclipse ioFog 3.7 is officially released.
Eclipse ioFog is now positioned as a strong
EdgeOps platform ready for enterprise-scale deployments.
You can explore more here:
Many thanks toÂ
@Ignacio Ahedo ,Â
@Frédéric Desbiens for their support during the project handover.
For those attending OCX'2026, please join us for the IoT WG BoF session on 21st Apr 19:00-20:00 CET, where I’ll walk through the release in more detail.Â
What’s new in v3.7?
We focused on making ioFog simpler, more secure, and truly production-ready:
- Distributed Messaging
Legacy messageBus is deprecated, and introduction NATs as a built-in messaging component across distributed edge clusters.
Built-in pub/sub, request-reply, K/V store, and persistent streaming with automatic credential management. Auto attached MessageBus access credentials to the edge workload runtime. No manual overhead with fine grained rbac. - Security & Access Control
Fine-grained user RBAC and NATs decentralize JWT authentication/authorization. Default m-TLS for Router and MessageBus networks, and improved secrets management with external KMS support - Service Interconnection Network
Native and secure service interconnection across edge workloads distributed onto edge nodes, Kubernetes services, and external systems - Operations & Debugging
Remote exec sessions, live logging, and better observability for agents and workloads - Platform Capabilities
Airgap deployment support, offline image distribution, ConfigMaps, Secrets, and flexible volume management - User Experience
ECN Viewer now mirrors almost all CLI capabilities for full browser-based operations - Modernized Stack
Router upgrade to Skupper, improved Kubernetes integration, Keycloak-based auth, and extended edge microservice runtime options
What's next?
We’re continuing with major improvements over the coming months:
- June 2026
New ioFog Agent written in Go
Smaller footprint, single binary, no external container engine, and RISC-V support - Q3 2026
Automatic certificate rotation and mTLS-based user authentication - Q4 2026 - Q1 2027
Introduction of Eclipse Zenoh as an additional message bus option alongside NATs
This release is just the beginning of bringing ioFog back as a modern, enterprise-ready edge platform.
Looking forward to your feedback and to seeing some of you at OCX.
Cheers,
