This project has a successor
SiteWhere is now DeviceChain.
SiteWhere was an open-source IoT platform built on Java and Spring. It is no longer maintained — the last release was 3.0.5 in 2021, the last commit landed in early 2024, and the website it used to serve has been offline for some time.
Its successor is DeviceChain: a ground-up rebuild in Go that keeps the domain model SiteWhere got right — devices, types, assignments, the event pipeline — and replaces the stack that made it hard to run.
What this means
- Nothing is being deleted.
- The SiteWhere repositories stay on GitHub for reference, so existing deployments, forks and links keep working. They are not receiving fixes.
- The domain model carried over.
- If you modelled a fleet in SiteWhere, the concepts will be familiar. Device types now reference a versioned device profile, and assignments generalized into a typed relationship graph — the shapes you already know, with the rigidity taken out.
- The operational story is different.
- Two dependencies instead of a Java estate: NATS and TimescaleDB. Single-binary Go services, a Kubernetes operator, sub-second startup. Still Apache-2.0, still self-hosted, still no per-device metering and no open-core split.
If you ran SiteWhere, we want to hear from you
DeviceChain is pre-1.0 and in active development. The platform is built and exercised in CI, and its disaster-recovery and high-availability behaviour has been drilled against a live cluster — but it has not yet been run by many people who did not write it.
That is the gap, and people who ran SiteWhere are the best possible ones to close it: you already know where this kind of platform tends to break. Installing it and telling us where you got stuck is genuinely the most useful thing anyone can do for it right now. Rough reports beat polished ones — interfaces can still change in response to them, which stops being true at 1.0.