Nexgen OS

An open foundation for describing the world — sites, buildings, roofs, meters, participants, devices, sensors — in 3D and over time, so that architecture, energy, operations and compliance tools share one model.

Status: 0.0 — the core schema, the architecture, weather and solar modules, the Home Assistant, geocoding, CityJSON and IFC libraries, the Open-Meteo and PVGIS connectors, external engines in any language with pvlib (Python) as the first, the nexgen-os installer, the fr and be country packs and seven example datasets. Tested; nothing is stable until 0.1.

The pact

The data is yours: it sits in a Postgres database you control, in tables you can read, and leaves only when you say so.
The words are plain: the best of the trades' standards — IFC, CityGML, Brick, SensorThings, QUDT — with names anyone can understand, the standard term written next to each.
The rules are data: what a country, a grid operator or a market decides is a pack of files anyone can read, propose and prove.

What it is, and what it is not

Nexgen OS is the open-source foundation and reference language, under AGPL-3.0 for the core and the modules and MIT for the format libraries, the connectors and the engines. Computations can run outside the database, in any language: a Python engine such as pvlib receives one JSON request and answers one JSON result, and the core keeps the provenance. Nexgen, the commercial platform of WeSmart, is built on it and remains WeSmart's product. The foundation is also made for research: a base that universities and research centres can start from, test a method on and publish a module for.

Read, install, contribute

The repository, the manifesto and the decisions: github.com/nexgen-os/nexgen-os
For an AI agent helping somebody use it: AGENTS.md
What the figures are and are not: DISCLAIMER.md
Where the open foundation stops and the product begins: docs/nexgen-os-and-nexgen.md