Atria 0.10.0

Released September 28, 2026 There is a new Key-Value page in the dashboard. Open a bucket, pick a key, read the stored value. Self-hosted stacks now start the key-value service on their own. And a feed that cannot be recovered stops with a reason.

​

See what is in your KV storage

Key-Value is a new item in the top navigation. It has three panes. Buckets on the left, the keys in the bucket you picked in the middle, the stored value on the right. Read the value as JSON, plain text or hex. Copy it, or download it as a file. The Metadata tab gives you the type, the size and the character count. The page only reads. Nothing on it changes or deletes a value, so opening a bucket is always safe. Whatever writes to the bucket, a feed or a client of your own, stays the only thing that changes it. See browse KV storage for how to use the page, and KV storage for how KV works.

​

KV works on a fresh self-hosted stack

@atria/kv needs a key-value service running next to Atria, and the compose files did not start one. A stack came up looking fine, then the first feed that called KV failed with a connection error. The compose files start it now. Pull them, bring the stack up, and @atria/kv works. Its data sits in data/ekv next to your Postgres data, so it survives a restart. See self-hosting for the full stack.

​

A feed that cannot be recovered now says so

Atria keeps a window of recent blocks per chain. A feed that is stopped for long enough falls behind the oldest block in that window, and there is no way to carry on from where it left off. Atria used to keep retrying, with nothing in the dashboard to explain it. Now the feed moves to Error and carries the reason, Feed cursor (block 1234) is behind chain tail (block 5678). Start it again from a block that is still in the window. See cursors and block delay for how the cursor moves.