← Energy board · written 2026-10-15 by claude-opus-5-5 from the pipeline's evidence only

Fabian Neumann (fneum): energy systems, PyPSA maintainer

### What they built His GitHub bio says he is a maintainer in the PyPSA ecosystem, an energy systems researcher at TU Berlin, and managing director of @pypsalabs [source]. PyPSA is an open-source Python framework for optimising and simulating power and energy systems, built for researchers, planners and utilities [source]. It has 2,191 stars and 716 forks [source]. PyPSA-Eur, a sector-coupled optimisation model of the European energy system, has 623 stars and 476 forks [source]. He owns data-science-for-esm, with 135 stars and 101 forks [source]. What @pypsalabs sells, and to whom, is not in the evidence.

### Record Measured signals (n=3; Skoor 35; confidence 0.7) [no source URL in the evidence]:

  • 647 commit contributions in the last year [source].
  • 21 commits in 90 days on PyPSA-Eur, out of 97 total repo commits in that window [source].
  • Commits on both PyPSA and PyPSA-Eur in 90 days [no source URL in the evidence]. His own commit count on PyPSA is not in the evidence. The repo had 99 commits in that window [source].

    • Other facts: the account was created in May 2017 and has 294 followers [source]. His 2017 EV-charging scheduling repo was last pushed in June 2018 [source]. Papers are not in the evidence.

    Inference: the ~22% share of recent PyPSA-Eur commits and the maintainer title point to a core role. Commit counts alone do not show design authority.

    ### Why now Market timing is not in the evidence. Both PyPSA repos were pushed in October 2026 [source] [source].

    Inference: a managing director title at @pypsalabs alongside an academic post suggests commercial work around the open-source tools has already started.

    ### Unknowns

  • What @pypsalabs is, its stage, revenue, customers and funding: not in the evidence.
  • His commit volume and role on PyPSA core: not in the evidence.
  • How his time splits between TU Berlin and @pypsalabs: not in the evidence.
  • Who else maintains PyPSA: not in the evidence. The README notes many contributors [source].

    • ### Questions for the room

  • You are listed as a PyPSA maintainer. Which parts of PyPSA and PyPSA-Eur did you design, and who decides what gets merged?
  • You are managing director of @pypsalabs. What does it sell, who pays, and how much revenue has it booked?
  • You hold a TU Berlin research role. How much of your time goes to @pypsalabs, and do the university and the open-source project have any claims on its work?

    • ### What would move the Skoor It would rise with evidence of paying @pypsalabs customers or a clear lead role in PyPSA core. It would fall if his commits are mostly peripheral or if @pypsalabs has no revenue.