Nodebyte — the inventory I wish I had years ago

October 2, 2026 update: keep the docs with the systems

NodeByte now keeps documents, reference links, and channel directories alongside your inventory. Save the original link, add a summary, and connect the resource to the systems it describes. You can find the context you need before opening another tab.

A useful record behind every link

The Knowledge view gives a document somewhere to live with a summary, separate notes, tags, and a source label such as Google Docs or Slack. You can also record when the source was created and last edited. Those dates stay separate from the dates NodeByte maintains for its own record.

A backup guide can explain what it covers. A solution design document can say which implementation it belongs to. A channel directory entry can describe what the channel is for. Search can use that saved context even when you cannot remember the resource's exact name.

Documentation connected to inventory

Link a recovery runbook to a server and the relationship appears on both records. Open the server to find its runbook, or open the runbook to see the system it describes. The same approach works for design documents, reference links, and channel entries.

Inventory has its own view, and the existing table, bulk actions, and parent-child relationships remain available. The Knowledge view gives documents and references their own space, while shared search looks across both.

Collections that fit your work

Collections bring related resources together. A Home lab collection might contain a NAS, its backup guide, and networking notes. An internal platform team might collect an API service and its recovery runbook. For customer work, a rollout collection could include the systems, a solution design document, and the implementation channel.

A resource can belong to several collections or none. You can start with a single useful document without setting up a customer or a project. Removing a collection leaves its resources in NodeByte.

Collections organize the team's resources. Existing team permissions still apply: viewers can read, and members, admins, and owners can curate. Saved summaries and notes are visible to that NodeByte team; the original document keeps its source's access controls.

Shared search, with manual curation first

The search field above the workspace searches saved names, summaries, notes, tags, source labels, and inventory fields such as hostnames and URLs.

This first release uses manual curation. You write the summary and enter source dates when you know them. A Google Docs or Slack source label identifies where a link comes from; it does not connect an account or synchronize content. Search covers what is saved in NodeByte. Automatic document ingestion, metadata refresh, AI-generated summaries, and Slack message or thread indexing are not included.

To try it, open NodeByte, save one document, and link it to a system you already track. If a collection helps, add one. The GitHub README includes a walkthrough and a home-lab example for the self-hosted app.

The original NodeByte story

I’ve been doing IT for about 20 years now, and everywhere I’ve worked has had the same problem:

Inventory.

Not just tracking assets—but having a consistent way to track them.

I’ve used everything:

spreadsheets
RMMs
Active Directory
MDMs
NetBox
Snipe-IT
custom scripts
probably a dozen other tools

And honestly?

They’re all… fine.

But they all mostly stink.

The Real Problem Nobody Solves

What was always missing for me wasn’t just devices.

It was services.

“This is our customer onboarding app”
“This is the internal tool finance depends on”
“This is the public site that breaks = everyone panics”

That stuff never lived in the same place as infrastructure.

So now you’ve got:

one tool for servers
one tool for networking
one spreadsheet for apps
random docs for “important things”

And suddenly your “inventory” is spread across five tabs and tribal knowledge.

I hated that.

So I Built What I Actually Needed

I got tired of jumping between tools, so I built my own.

That became Nodebyte.

This isn’t even version one—this is like version five. It used to be called Nodeboard, but it wasn’t doing what I needed.

Nodebyte is.

What Makes Nodebyte Different

The big shift is simple:

👉 Everything is inventory. Not just machines.

servers
containers
services
websites
dependencies
relationships between all of it

Now I can see:

I have 30 LXD instances inside one of those are 30 Docker containers and those containers power specific services I actually care about

All in one place.

Automation Was Non-Negotiable

The other thing I needed was automation.

Nodebyte has an API, so I can:

run a cron job on my LXD host
scan my environment
post updates automatically

No manual updates. No drift. No guessing.

Same thing for apps: When I spin up a new self-hosted service, my workflow updates Nodebyte automatically.

Why This Actually Matters

Inventory isn’t just “nice to have.”

It’s the difference between:

reacting vs understanding
guessing vs knowing
scrambling vs operating

Most tools track what exists.

Nodebyte helps you understand: 👉 what matters and how it’s connected

Final Thought

This isn’t some theoretical system.

It’s the tool I kept wishing existed—so I built it.

And honestly?

I use it every day.