DEVELOPERS / OPEN ENGINEERING
Understand the
whole connection.
A practical library of integration contracts, implementation notes and architecture proposals. Each guide labels what exists in the current release.
Integration architecture
A small boundary between provider messages and business workflows.
Read guide ↗02 / Implemented in 0.1The normalized uplink contract
The actual output of the Ghost Signal 0.1 adapters.
Read guide ↗03 / Implemented in 0.1ChirpStack uplink adapter
Map ChirpStack v4 JSON application uplinks without coupling your business logic to provider fields.
Read guide ↗04 / Implemented in 0.1The Things Stack uplink adapter
A strict mapping for The Things Stack v3 JSON uplink envelopes.
Read guide ↗05 / Architecture proposalDevice identity & ownership
Bind a physical device to the right customer before its first reading.
Read guide ↗06 / Architecture proposalPayload decoders & units
Make measurement meaning explicit and testable.
Read guide ↗07 / Architecture proposalReliable ingestion & retries
Accept once, process safely and make failure visible.
Read guide ↗08 / Architecture proposalDownlink command lifecycle
A queued command is not a confirmed physical outcome.
Read guide ↗09 / Architecture proposalAlarms, state & notification delivery
Model an alarm as a state machine, not a repeated email.
Read guide ↗10 / Architecture proposalSecurity & tenancy boundaries
Make the trust boundary explicit in every integration.
Read guide ↗11 / Architecture proposalEdge buffering & offline recovery
Design for a connection that eventually comes back.
Read guide ↗12 / Architecture proposalCommissioning & acceptance
Prove the entire path before shipping or handing over.
Read guide ↗13 / Architecture proposalAPI contracts & versioning
Describe what clients can rely on—and how it changes.
Read guide ↗