One API, four languages
Java, Python, Rust, and TypeScript share the same config schema, CLI contract, subsystem boundaries, and on-wire message envelope. Java is the canonical reference.
EdgeCommons
EdgeCommons — the same library in Java, Python, Rust, and TypeScript, so your components carry only business logic.
EdgeCommons bundles the cross-cutting concerns every edge component needs — configuration,
messaging on a unified namespace, metrics, heartbeat, logging,
credentials, parameters, and telemetry streaming — behind clean interfaces, implemented as
deliberate mirrors across four languages in the edgecommons library.
Platform × transport
Run the same component on Greengrass (IPC), a bare host or Docker (dual-MQTT), or Kubernetes — selected at startup, auto-detected by default.
Batteries included
Configuration, messaging, metrics, heartbeat, and logging out of the box; opt-in credentials, parameters, and telemetry streaming when you need them.
Edge-first
Offline-capable by design — encrypted local vault, offline parameter cache, and durable store-and-forward streaming that survives cloud disconnects.
Start here
Section titled “Start here”IntroductionWhat EdgeCommons is and how the pieces fit together.
QuickstartScaffold, build, and run your first component in your language.
GuidesConceptual guides for every subsystem, in all four languages.
API ReferenceThe public API surface, verified against source.
ComponentsReady-to-deploy adapters, processors, and sinks — with operator/deployer guides.