Skip to content

enbility relaunches: the consortium behind the open source EEBUS stack in Go

Thomas Müller4 min read

enbility has relaunched: a new website and a five-member consortium now maintain eebus-go, spine-go and ship-go, the open source EEBUS implementation in Go.

In December 2025 we announced that enbility would not go away, but restart on a broader footing. That restart is now complete. The libraries have a group of owners instead of a single maintainer, the rules by which that group works are published, and the website has been rebuilt to show who is behind the code and how to get involved.

What is enbility?

enbility maintains the open source Go implementations of the EEBUS protocols SHIP and SPINE. They let heat pumps, wallboxes, PV inverters, battery storage and energy managers coordinate on the local network — including the grid-control use cases required under § 14a EnWG and § 9 EEG in Germany.

The stack consists of three MIT-licensed Go modules:

  • ship-go — transport and trust: certificates, mDNS discovery, WebSocket connection, pairing and the SHIP handshake.
  • spine-go — the SPINE data model: entities, features, function types, subscriptions and bindings.
  • eebus-go — the use-case layer, such as limitation of power consumption (LPC) and production (LPP) or EV charging. This is the import most products need.

The libraries were first released publicly in December 2022. Within weeks, evcc picked them up, and they have been running in production devices ever since.

Who is in the enbility consortium?

Five members carry the project: four companies and one individual maintainer. Each brings a different part of what an EEBUS stack needs in practice — code, devices, test capacity and field experience.

  • Coretech Innovations brings eebus-go into manufacturers' products with deployment-ready packages and broad use-case support for Linux and embedded targets. With the EEBUS Hub for simulation and EEBUS Verify 360 for automated pre-qualification, Coretech also contributes tooling for validation and interoperability testing.
  • EnQS from Karlsruhe is an independent development and testing partner for connected energy management. In the EnQS Testlab, use cases are developed and validated against real PV and battery inverters, wallboxes, heat pumps, smart meter gateways and control boxes. EnQS contributes to eebus-go and spine-go with use-case development, test tools, development planning and code reviews.
  • Kontron eSystems from Wendlingen develops and manufactures AC charging solutions and brings ten years of EEBUS experience. The company builds the internal energy management of its wallboxes on eebus-go, with a focus on e-mobility use cases and hardware validation.
  • SPiNE from Munich builds software and hardware for intelligent metering systems and energy assets. Its EnergyLink One gateway speaks EEBUS to heat pumps, PV, storage, wallboxes and control boxes in the meter cabinet and was the first device qualified with the enbility stack. SPiNE contributes to certification and the regulatory use cases, and runs public relations and the website.
  • Kai Takac, a software engineer in the energy sector from Linz, has been a maintainer since 2025.

An individual maintainer as a full member is deliberate: it keeps the project independent of any one employer's priorities, with the same vote as a company.

Who wrote the libraries?

ship-go, spine-go and eebus-go were originally written by Andreas Linde. He released them publicly in December 2022 and carried the project single-handedly for its first two years. Almost everything the consortium maintains and develops today builds on his original work, and we are grateful for it.

Since Andreas is no longer an active member, the consortium took the codebase from there and jointly continued development and maintenance.

How does the consortium make decisions?

The enbility governance sets out roles, policies and member commitments. Its current version 1.4 was approved in July 2026. Four principles apply:

  • Neutrality — technical decisions are made in the open and on merit.
  • Transparency — proposals, decisions and roadmaps are public.
  • Continuity — releases, security and CI do not depend on any single company.
  • Accountability — clear roles, rotation and measurable service levels.

Member companies may build and sell proprietary or open products on top of enbility without disclosing their own source code, subject to the MIT licence of the repositories.

What is new on the website?

  • Consortium — a profile page for every member: what they contribute to the project, and which products and services they offer around it.
  • Code — the three modules with current versions and release dates read directly from GitHub, plus supported use cases and how to contribute.
  • FAQ — how EEBUS works, what the libraries add on top of the specification, whether using enbility makes a device certified, licensing and governance.
  • Governance — the full governance document, readable on the site.
  • Blog — all earlier posts have moved over, and their URLs still work.

How can I get involved?

enbility is open to users, contributors and new members.

  • Use the libraries: start with eebus-go and the Code page.
  • Ask questions: technical questions belong in GitHub Discussions, where the answer helps the next person. Bugs go to the issue tracker.
  • Contribute: contributors can be promoted to committer and then to maintainer of the repositories they work on.
  • Become a member: the Steering Committee admits new members after a commitment declaration and at least one meaningful contribution in code or operations. Get in touch via the contact page.

For project news, follow enbility on LinkedIn.