About & roadmap

Vitrinode is a management platform for Linux infrastructure, being built by Vitrinode Ltd. It covers host inventory, device identity and remote operations. It started out in a Proxmox and Linux homelab spread across several sites. Least privilege and a proper audit trail have shaped it the whole way through.

On this page: Company· Naming· Status· Roadmap· Development· Contact

Company

Vitrinode Ltd is a private company limited by shares, incorporated on .

Registered name
Vitrinode Ltd
Company number
17494950 (Companies House)
Registered in
England and Wales
Registered office
Barnsley, England

The name

Vitri- comes from vitreous and vitrine, a glass-fronted display cabinet. The point of one is that you can see everything in it while it's kept in order. Node is the hosts, VMs, containers and so on that the platform is meant to make visible.

There's a local bit to it as well. Vitrinite and vitrinoid are coal terms for material with a glassy lustre, which ties back to vitri- and to where the project comes from: Barnsley and the South Yorkshire coalfield.

Development status

As of .

Stage
In development, working towards v1.0.
Verification
Automated tests in CI, plus end-to-end runs on real Debian hosts, a live Proxmox VE cluster, VMs with TPMs and disposable test hosts. Not just fixtures.
Source
Private for now.
Availability
No release date yet. Commercial agreements, licensing and formal evaluations will wait until v1.0.

Roadmap

Things move when they're built and tested, so there are no dates on any of this.

Now

  • Short-lived SSH certificates: rolling device-bound certificates out to enrolled hosts and finishing Phase 8
  • Vitrinode-HSM Phase 3 closure: leak proofs, resource checks and the full acceptance run
  • Rolling executor hardening out to enrolled hosts

Next

  • SSH certificates signed by the HSM, from the server

Later

  • A timeline of changes on each host, and full per-host inventory in the interface
  • Production HSM key protection, trusted time, device audit and sealing

Recent development

Newest first.

  1. October 2026: fixes from end-to-end testing. Agents stop polling for jobs once they're revoked, provisioning sets up TPM access on Debian cloud images, and a step-up check can only refresh a session belonging to the same user.
  2. October 2026: device-bound SSH certificates. Each certificate only works on one trusted host and only for accounts set up for certificate login, and the executor installs the CA key against a pinned fingerprint. Accepted end to end on disposable hosts with a development-only CA.
  3. October 2026: the executor refuses privileged jobs when the host clock isn't synchronised.
  4. October 2026: privileged jobs are only created and dispatched for a TRUSTED device, and if trust is lost after a job's been delivered, that's recorded in the audit trail.
  5. October 2026: executor hardening accepted. Root-owned trust paths, a pinned device identity and at-most-once execution, tested on disposable hosts. Not rolled out to enrolled hosts yet.
  6. October 2026: first short-lived SSH certificates. A certificate issued after a security-key check logged in through stock OpenSSH, and expired, unauthorised and replayed requests were refused. Development-only software CA.
  7. October 2026: Vitrinode-HSM Phases 3c and 3d.5. On-device CA provisioning with a physical button press, and defined behaviour if power is lost at any stage of provisioning, checked on the development board.
  8. October 2026: Vitrinode-HSM Phase 3b. Persistent CA storage and loading at boot accepted on the development board.
  9. : Vitrinode Ltd incorporated.
  10. September 2026: HSM Phase 2 complete. A certificate issued by the RP2350 board authenticated against stock OpenSSH. Server integration is still to do.
  11. Phase 7 complete: device attestation with vTPM quotes and a clearly weaker software-evidence fallback, checked on real TPM hardware
  12. Phase 6 complete: read-only Proxmox VE inventory and device correlation, tested against a live cluster
  13. Phase 5 complete: signed, replay-protected remote jobs and a separate privileged executor
  14. Phase 4 complete: inventory collection (system, storage, network, systemd, APT, Docker)
  15. Phase 3 complete: WebAuthn/FIDO2 sign-in and step-up
  16. Phase 2 complete: device provisioning, mutual TLS and certificate revocation
  17. Phase 1 complete: server/agent heartbeat and host list
  18. Project start: repository structure, architecture and threat model docs

Contact

Technical questions, business enquiries or interest in v1.0. Enquiries has what's useful to include.

hello@vitrinode.com Replies may take a few days.