Sensorics & IoT
MQTT and device telemetry into NGSI-LD, optional connectivity tooling, and automation (e.g. n8n). Heavy ingestion paths use Kubernetes and time-series storage behind the twin.
Ecosystem overview
Esta página aún no está disponible en tu idioma.
The module grid (/modules on this site) is driven by content/modules.json: one entry per product line (core, native services, mobile apps, marketplace modules). Each entry has a status (active, evaluation, etc.). Evaluation items render with an asterisk (*) and a footnote on the marketing pages — use this for roadmap and work-in-progress surfaces without hiding them from the catalog.
Long-form commercial narrative (platform + apps + full marketplace list) remains in the core repo:
NKZ ecosystem — platform, apps & modules
When naming or scope changes, update both files; fix GitHub URLs in modules.json against github.com/nkz-os if a repo was renamed.
Per-domain technical notes can also appear under Modules Catalog in the sidebar (e.g. IoT, LiDAR) when ingested from satellite repos via scripts/fetch-docs.js.
Status field
Section titled “Status field”| Value | On nkz-os.org |
|---|---|
active | No asterisk — treated as a production-grade line in current deployments. |
evaluation | * next to the title + footnote explaining “under evaluation”. |
placeholder | Same as evaluation (legacy). |
Module categories (high level)
Section titled “Module categories (high level)”Same thematic grouping as the public story; aligns with the ecosystem doc’s theme table.
Spatial data (LiDAR & terrain)
Point clouds and elevation products composed in the WebGL client — national layers, custom uploads, and EU-scale terrain where deployed.
Robotics
Cockpit-style experiences and bridges from field robotics into the same NGSI-LD context as parcels and sensors.
Agrivoltaics & energy
Workflows for solar-on-farm and community energy scenarios, often alongside ERP and automation modules.
Maintainers — avoid route conflicts
Section titled “Maintainers — avoid route conflicts”The marketing routes /modules and /es/modules are reserved for the Astro marketing pages. Do not add src/content/docs/modules/index.md here: Starlight would conflict and the doc index would be dropped at build (higher-priority marketing route wins). Use overview.mdx (this page, /modules/overview) for the catalog hub in docs.