Ambitwin · source-available, not open source · © 2026 Nicolò Ghignatti
Every service’s edge surface: HTTP as OpenAPI 3 (rendered by Swagger UI), the Socket.IO feed as AsyncAPI 3. The specs are sources in this repository, at api/*.yaml, and are published alongside this guide — so a spec change ships in the same commit as the handler it describes. They document the edge-facing surface only: internal service-to-service hops and cross-boundary payload shapes are contracts in schemas/, not public APIs.
claims-gateway: Keycloak login and token exchange, the session cookie, /verify for the edge.
gateway.yaml
telemetry: batch ingest, sensors, thresholds, device actions, simulation.
telemetry.yaml
notification: Web Push subscriptions, alert switches, manual alerts.
notification.yaml
socket: the live Socket.IO feed — notifications, telemetry ticks, device dots, building subscriptions.
socket.yaml · AsyncAPI
socket.yaml is AsyncAPI 3, not OpenAPI: Socket.IO pushes events instead of answering requests, so it opens in its own viewer (api/asyncapi.html). registry and provisioner have no edge route, so they have no card.