Technical evaluation

Vitrinode is Linux infrastructure management software in active development by Vitrinode Ltd. A technical evaluation is an opportunity to assess its current capabilities against a defined environment and share feedback on what needs to improve.

Start with a lab or isolated test environment and a specific question to assess. Access is arranged directly after discussing suitability and scope. No general availability date has been set.

How access is arranged · Send an evaluation enquiry

On this page: Who it is for· Platforms· Scope· Status· Security· Access· Contact

Who an evaluation is for

Engineers and small infrastructure teams managing Debian or Ubuntu hosts who want to assess centralised inventory, device identity and constrained remote operations. Vitrinode is designed around smaller estates, including Proxmox environments and Linux hosts running Docker workloads.

An evaluation should have a clear technical question, an agreed set of test hosts and someone able to review deployment and security requirements. A lab or isolated test environment is the starting point.

Platforms and compatibility

  • Debian and Ubuntu: the current Linux target, using APT/dpkg and systemd.
  • Docker: collection of workload and object inventory on managed Linux hosts.
  • Proxmox VE: read-only VM and container inventory, correlated with enrolled agents.

Exact OS releases, host configuration and deployment requirements are confirmed during scoping. Windows management and VMware integration are outside the current evaluation scope. See the platform overview.

What an evaluation covers

The scope is agreed individually around capabilities already implemented. Depending on the environment, it can cover:

  • Device enrolment, host connectivity and inventory collection.
  • WebAuthn sign-in, step-up authentication and device revocation.
  • Signed, typed remote jobs and their audit records.
  • Read-only Proxmox correlation and device trust-state behaviour.

Choose a small set of questions to answer, such as whether device enrolment fits your process, how Proxmox records correlate with agents, or how the permitted job set meets a routine task. The evaluation scope is based on those questions and the build being assessed.

Current status and limitations

Status reviewed: . Vitrinode remains in active development; evaluation access is subject to individual agreement.

  • Inventory collection is implemented. Full inventory rendering and change timelines remain planned.
  • SSH access through short-lived certificates and a browser terminal remain planned.
  • The HSM is a separate hardware prototype. Persistent CA storage is in development, and server integration is not yet implemented.
  • Proxmox integration is read-only; VM lifecycle actions are not implemented.

The capability table distinguishes implemented features from work in development and planned features. Evaluation scope is based on the build being assessed.

Security model

Devices generate their own identity keys and connect using mutual TLS, with revocation checked on authenticated requests. Human access uses WebAuthn, with step-up authentication for sensitive actions. Agents initiate connections to the server, and privileged operations are separated into a local executor.

Remote jobs are typed, signed and replay-protected. Device authentication and attestation are tracked separately; software evidence is explicitly weaker than TPM-backed evidence. There are no certification or third-party penetration-test claims.

Read the security principles and architecture when assessing suitability for your environment.

How access is arranged

  1. Describe the use case. Send a brief enquiry using the checklist below. We discuss whether the current product is suitable for what you want to assess.
  2. Agree a bounded evaluation. Confirm OS releases, test hosts, permitted operations, duration and success criteria. Deployment, removal, feedback, assistance and any commercial terms are agreed before access.
  3. Arrange access if there is a fit. Access and deployment are coordinated directly. Sending an enquiry does not create an account or commit either party to an evaluation.

Use the current capability list and architecture to prepare. Features still in development or planned are not assumed to be part of the evaluation.

Send an evaluation enquiry

Email Vitrinode Ltd with the subject Technical evaluation enquiry and a short description covering:

  • Environment: Debian or Ubuntu releases, approximate host count, and any Proxmox or Docker use.
  • Use case: the task or question you want to assess and what a useful result would look like.
  • Test setup: the lab or isolated hosts available and any deployment constraints.
  • Contact: who will coordinate the technical evaluation.

A high-level description is enough for the initial discussion. Leave out credentials and sensitive infrastructure data.

Company information is available on the About page and below.