Enquiries

Vitrinode is still being built and isn't at v1.0 yet. You can send technical questions, business enquiries or interest in v1.0 now.

Commercial agreements, licensing, formal evaluations and design partnerships will wait until v1.0. There's no release date yet.

On this page: Who it's for· Service providers· Platforms· Status· Before and after v1.0· Contact

Who it's for

Teams looking after Linux servers, VMs and containers who want to see them in one place, give each host a proper identity, and have routine admin go through a route that's controlled and audited. Proxmox VE and hosts running Docker are both in scope.

Managed service providers

If you manage Linux infrastructure for customers, you need to see across a lot of hosts, keep privileged work controlled and attributable, and have a record of who did what. This is how Vitrinode covers that:

  • Visibility: enrolled hosts, their inventory and Proxmox VE guests in one place.
  • Privileged operations: a fixed set of signed operations, and privileged ones need a security-key check and a trusted device.
  • Device identity and trust: each host has its own identity, revocation is checked on every request, and there's attestation where the hardware supports it.
  • Audit: the same operations on every host, each one recorded in an append-only audit trail.

That said, it's currently built around a single estate. There's no multi-tenancy, customer isolation or delegated tenant admin, and none of that is promised for v1.0. It's management software. It doesn't replace qualified Linux engineers and it isn't a managed service.

Platforms

  • Linux: aimed at Ubuntu, Debian, SUSE Linux Enterprise and Red Hat Enterprise Linux. Debian is validated on real hosts. The platform table has where the others are up to.
  • Docker: container and image inventory on managed hosts.
  • Proxmox VE: read-only VM and container correlation with enrolled hosts.

Managed hosts need synchronised time (NTP), because job expiry and SSH certificate validity are checked against the host clock. Windows and macOS aren't in scope.

Current status

As of .

  • Implemented and tested: device enrolment, mutual TLS, passkey sign-in with step-up, inventory collection, signed jobs, device attestation, audit records and Proxmox correlation.
  • Short-lived SSH certificates are in development. Certificates bound to a single trusted host have been tested end to end with a development-only software CA.
  • Vitrinode-HSM, the signing device for the SSH CA key, is in development and not connected to the server yet.
  • Planned: the per-host inventory view, a timeline of changes on each host, and interfaces for jobs and audit.

The capability table has the detail, and the security model and architecture pages cover the controls and where they stop. Vitrinode has no certifications and hasn't had a third-party penetration test.

Before and after v1.0

  • Now: questions about the architecture, security model, platform plans or how it might fit your environment, and registering interest in v1.0.
  • From v1.0: commercial agreements, licensing and formal evaluations, on terms set at that point.

Sending an enquiry doesn't create an account, give you access to any software or commit either side to anything. There's no published pricing, support terms or release date.

Contact

Email a short description of what you're asking about. These subject lines help:

  • Technical question: architecture, security model or capabilities.
  • v1.0 interest: your environment, roughly how many hosts, which Linux distributions, and whether you use Proxmox or Docker.
  • Business enquiry: anything else, including service-provider use.

Please don't send credentials or sensitive details about your infrastructure. Company details are on the About page.