Welcome to DeviceChain Discussions

[derekadams]

DeviceChain is an IoT application enablement platform — device lifecycle, telemetry
ingestion, command and control, organizational modeling, and multi-tenancy, all exposed
through a GraphQL API. It is Apache-2.0, self-hosted, and unmetered: no open-core split,
no per-device pricing.

This space is for the conversations that do not fit in an issue.

Where things go

What you have	Where it goes
A question, or something that confused you	Right here, in Q&A or General
An idea or a feature request	Ideas — accepted ones become tracked issues
Something is broken	Open an issue
A security vulnerability	Email admin@devicechain.io — please do not file publicly

You do not need to be sure something is a bug before raising it. If you could not tell
whether the behaviour you saw was intended, that ambiguity is worth reporting on its own.

Where the project actually is

v0.9.0 is out — the first released build, and the honest summary is that it is
pre-1.0 and behaves like it. Interfaces can still change, and we would rather change them
now in response to what people hit than after 1.0 when we cannot.

Two things worth knowing before you install:

• v0.9.0 cannot be upgraded into. It collapsed every database migration chain into a
  single baseline, so an existing instance is recreated rather than migrated. This is a
  one-release exception, not the policy going forward — the details are in
  Releases and upgrades.
• Bring-up is the part we can least easily reproduce, because we only have our own
  machines. dcctl preflight catches many environment problems on its own.

What is most useful to us right now

Install and first-run reports, more than anything else. A platform that runs on the
maintainers' laptops and nowhere else is a platform with a bug it cannot see — so if
bring-up failed on your Kubernetes distribution, your OS, or your CPU architecture, that
is genuinely the most valuable thing you can post.

Close behind: places where the documentation said something that turned out not to be
true, or did not say the thing you needed. A page that sends someone down the wrong path
is a defect, and it is one we cannot find by re-reading our own writing.

What to expect

DeviceChain is maintained by a small team, so a reply may take a few days — a thread
sitting quiet for a little while has not been ignored. Reports that name a version
(dcctl version) and the last step that worked before the first that did not get
resolved fastest, because nobody has to come back and ask.

One housekeeping note: Discussions are public, and logs and command output can carry
tokens, connection strings, and internal hostnames. Worth a glance before pasting.

Getting help has the longer version of all of
this, including the three things that most often make telemetry vanish silently.

Welcome aboard.