VMKeeper · NEURONTEX EU<br>For small ESXi environments, VMKeeper brings order to backups: what is protected, what broke, and the evidence to verify it , visible on one screen, without manual scripts or enterprise licensing.
Why it exists<br>Free utilities copy files but cannot answer the operational questions<br>01Did yesterday's backups complete, on every VM?<br>02Did a scheduled job go silent overnight?<br>03Is the copy intact, or a corrupt file that will fail a restore?<br>04How much storage remains, and what is consuming it?<br>05How do you show an auditor that copies are made, verified, and retained per policy?
Scope<br>Who it is for<br>VMKeeper is built for small ESXi estates, not for enterprise datacenters.<br>Standalone ESXi hosts, including free ESXi, with no vCenter.<br>Environments of one to five hosts.<br>One administrator carrying many responsibilities.<br>Auditors or clients who ask for verifiable backups.
Discipline<br>Discipline pillars<br>Each pillar maps to functionality that ships today.<br>Scheduled backups<br>Native host-side cron triggers each job. A short-lived snapshot is taken per run and released immediately. Jobs keep running with the console closed.
Verification<br>Every backup gets a disk-chain integrity check and a checksum baseline; restore re-verifies before it touches anything. Test recovery boots an isolated copy, network disconnected, for you to verify.
Offsite copy<br>Deduplicated copies to a NAS over SSH or to Amazon S3, using the restic engine. A 3-2-1 layout without touching production VMs. Manual copy on Starter (one SSH target); scheduled copies, Amazon S3 and multi-host from Standard.
Capacity control<br>A fail-closed free-space precheck runs before any snapshot. Capacity and snapshot deltas are monitored and alerted on.
Alerts and reports<br>Branded HTML email reports per job, an optional Telegram channel, and an event log in the console.
Recovery<br>Test recovery in an isolated, network-off VM, and guided replace that keeps the original VM folder for rollback. Restore to the same host or to a different one; a migration keeps the source folder and vmx names on disk. Recovery is never license-gated.
Capabilities<br>The full cycle: capture, verify, retain, alert<br>Working today<br>Job wizard and schedules Create a backup in a few steps, with a readable schedule builder instead of cron, and one-click runs.<br>Integrity-checked copies Quiesced snapshots when VMware Tools are healthy (crash-consistent otherwise), disk-chain checks on every run, and a checksum baseline that restore re-verifies. A copy that fails verification is refused, never passed off as good.<br>Windows installer A signed installer sets VMKeeper up as a Windows service; upgrades install in place over the existing version. Nothing to compile.<br>Recovery wizard Test recovery into an isolated, network-off VM, restore to the same or a different host, and guided replace that keeps the original folder for rollback.<br>Dashboard and inventory Protected VMs, recent failures, what is running now, and free space, at a glance. Protection status per machine.<br>Audit evidence trail Every copy leaves a manifest, a checksum, and a history, ready material for an ISO/IEC 27001 audit.
Coming next<br>Scheduled restore verification Regular automatic checks that a copy actually restores, with a report.<br>Immutability ZFS snapshots on TrueNAS to protect backups from ransomware.<br>Audit pack A packaged evidence bundle mapped to control requirements.<br>DR runbook A step-by-step disaster-recovery plan tied to real copies.
Architecture<br>One controller on the network, nothing resident on your hosts<br>Windows console<br>The console runs on Windows as a service. Management opens in a browser. No Linux, no command line.
No resident agent on the host<br>No guest agents and no resident daemon on the host's system disk. VMKeeper keeps small helper scripts and the job schedule on your backup datastore and drives them through the host's native cron, so scheduled backups keep running even when the console is off. Nothing is installed inside guest VMs.
Fully on-premise<br>The controller and the copies stay inside your perimeter. Storage is your NAS. No vendor cloud, no telemetry.
VMKEEPER · WINDOWSController (service)Console · schedulerHistory · manifests · alertsESXi HOSTProduction VMssnapshot to clone to verifySTORAGENAS · TrueNAS / NFSbackup copiesSSH deploycopiesruns from host cron<br>VMKeeper deploys small helper scripts over SSH and runs them from the host's native cron against your backup datastore. Nothing is installed inside guest VMs, and there is no resident daemon on the host's system disk: zero standing load on production VMs, no guest agents.
Comparison<br>The discipline of enterprise backup, without its weight<br>Manual scripts and free toolsVMKeeperWeb console and schedules○●Integrity verification of every copy○●Alerts on failures, by email or Telegram○●Audit evidence trail○●Nothing installed inside guest VMs●●Works on standalone and free ESXi●●
Pricing<br>Pricing<br>Annual licensing, EUR, VAT excluded.<br>Starter
€249per year<br>1...