ClaimStead is a local-first device claiming and ownership transfer system for self-hosted embedded devices.
It is for situations where a device should belong to its operator, not to a vendor cloud. A new device should be able to enter a home, lab, workshop, or field network, be claimed by its owner, and continue to identify itself as part of that local trust domain.
ClaimStead is built around a simple expectation: when you buy, build, repair, or reflash a device, you should be able to bring it under your own control without handing long-term authority to a remote platform.
In ClaimStead, a device starts with a bootstrap identity and is then claimed by an owner. After that point, ownership is meant to stay explicit, portable, and verifiable. The relationship between device and owner is not supposed to depend on a permanent vendor account, a public cloud login, or a closed onboarding service.
Many embedded products still treat activation as account binding to a vendor service. That model may be convenient for a platform operator, but it is often the wrong fit for:
- self-hosted smart home deployments
- home labs and workshop equipment
- research devices and test rigs
- robotics nodes and edge boxes
- field systems that may be disconnected or reassigned
ClaimStead is for people who want device onboarding to feel more like local stewardship than remote enrollment.
ClaimStead is centered on a few practical user outcomes:
- a new device can be claimed into a local trust domain
- ownership can be transferred without treating the old owner or a vendor cloud as a permanent authority
- device identity can be checked locally
- trust decisions can remain understandable and inspectable
- local operation stays the baseline instead of becoming a degraded fallback mode
ClaimStead fits environments where device ownership is real and changes over time:
- a lab controller moves from one bench owner to another
- a smart home gateway adopts a new sensor without exposing the household to a public SaaS dependency
- a robot subsystem is replaced in the field and needs to join the site's local trust model
- a reused development board is reassigned after reflashing or repair
- a small deployment needs proof that a device belongs to the current operator before accepting commands, configuration, or updates
ClaimStead is intentionally local-first.
That means the normal expectation is:
- the owner relationship is managed by the user or site operator
- device trust can be checked inside the local environment
- ownership transfer does not require a default always-online service
- the most sensitive trust decisions do not have to leave the user's control boundary
Optional external systems may still exist around a deployment, but they are not supposed to be the foundation of ownership.
ClaimStead is built for a simple trust story:
- a device should be able to identify itself
- an owner should be able to prove that the device now belongs to their local domain
- a previous owner should not remain an invisible permanent authority
- a third party should not need to be involved every time local trust changes
- verification should be possible without treating black-box infrastructure as magic
This puts ClaimStead close in spirit to the parts of decentralized systems that many people actually value: user-held control, portable identity, verifiable state, and reduced dependence on a single central operator. ClaimStead is not about tokens, speculation, or forcing every trust problem onto a blockchain.
ClaimStead is guided by a few deliberate design choices:
- keep ownership explicit instead of hiding it behind account systems
- keep local operation as the normal mode, not a disaster fallback
- keep trust relationships portable when devices move between operators
- keep identity verification understandable instead of opaque
- keep the system narrow enough to stay useful for real embedded deployments
The project is intentionally more interested in stewardship than in platform lock-in. It favors user-held control, inspectable trust boundaries, and local authority over models that quietly turn device ownership into a subscription to someone else's infrastructure.
git clone https://github.com/Zw-awa/ClaimStead.git
cd ClaimSteadStart with this README for the public scope, trust model, and user-facing meaning of ClaimStead. The hands-on getting-started flow can be expanded later when the first concrete project path is ready.
ClaimStead is not trying to be:
- a public cloud IoT platform
- a cryptocurrency project
- a generic home automation suite
- a full remote device management stack
- a replacement for transport encryption or secure boot
- a promise that "decentralized" automatically means safe
It stays focused on one narrower question: who legitimately owns and claims a device in a local deployment, and how that relationship can remain clear, portable, and verifiable.
ClaimStead is about ownership and identity, not magic security. Real protection still depends on hardware capabilities, key handling, firmware integrity, update policy, and the operating environment. A local-first trust model is useful because it makes those boundaries clearer, not because it removes them.
ClaimStead is licensed under the Apache License 2.0. See LICENSE.