What we commit to
- Verification results attach to the recovery point as evidence you can show.
- Non-payment suspends service. It never shortens existing immutability.
- No per-appliance license. The hardware is yours, in the region you choose.
Continuity that proves it boots
Coming soon. A server dies at 4 PM on a Thursday. Your client asks how long. The answer is minutes, because that recovery point already booted in a test.
Recovery point manifestVerified
rp-2026-08-05T02:00:14Z-9f42c81a
Capture completed02:00:14
Integrity digest matchsha-256 ✓
Boot verificationpassed ✓
Immutability lockrenews daily ✓
Signed • ed25519inspectable by your client
Most backups stay unverified until the worst possible moment
Backup products report success. Few of them prove the image would start. You find out during the outage, with the client on the phone. You learn what you own in front of the person who trusted you with it.
The three ways it goes wrong
Jobs that report green
A completed job proves data moved. Only verification proves the machine starts.
Hardware that locks you in
Per-appliance licensing and closed boxes turn a technical decision into a procurement negotiation.
Recovery you have never rehearsed
A restore test that needs a maintenance window never happens, so the runbook stays untested.
Whole-system protection, proven before you need it
Everything that matters, protected
Windows and Linux, physical and virtual. Agent-based protection for machines, agentless for VMware and Hyper-V, and a universal image path where neither fits. We state every capability difference between those modes up front.
Boot-verified recovery points
Verification boots the point on the schedule you set, and attaches the result to it as evidence.
Instant local virtualization
Run a failed server on the appliance in minutes while you repair the original. Boot an isolated test copy any afternoon without touching production.
Immutable cloud vault and cloud DR
Off-site copies land in the region you choose with rolling immutability locks. The locks survive a compromised appliance, console, or administrator account. When the site itself is gone, recovered systems run in a secure cloud environment.
Clean points after an attack
Ransomware turns recovery into forensics. Find the last clean point and hold the suspect ones. Systems come back in staged waves, with the evidence trail your insurer will ask for.
Your hardware, your region, your margin
Open appliance hardware and regional storage choice, with no per-appliance license. Growth reprices through published volume bands.
What EnterProtect protects, and how
Protection mode changes what recovery can do. This table states the differences, and the console repeats them on the resource itself.
| Protected system | Protection mode | Recovery available |
|---|---|---|
| Windows servers, physical | Agent-based |
|
| Windows desktop workloads | Agent-based |
|
| Linux servers, physical and virtual | Agent-based |
|
| VMware virtual machines | Agentless or agent-based |
|
| Hyper-V virtual machines | Agentless or agent-based |
|
| Systems without a supported agent path | Universal image path |
|
Every protected system, one status column
Protection state and health stay separate, so an exception stays visible in a fleet that is otherwise healthy.
- Capture
- Boot in isolation
- Stamp the point
Verifiedrp-2026-08-05T02:00:14Z
Where a recovery can come from, and where it can land
| Recovery source | Recovery target | Typical use |
|---|---|---|
| Appliance local repository | Instant virtualization on the appliance | A failed server this afternoon |
| Appliance local repository | Bare metal, original or unlike hardware | Rebuilding the machine properly |
| EnterProtect cloud vault | Cloud disaster recovery environment | The site itself is unavailable |
| EnterProtect cloud vault | Back on premises | The site is back and you are returning home |
| Qualified NAS secondary repository | Local recovery | A second copy on your own storage |
| External rotation member | Independent recovery | An offline copy that leaves the building |
Three steps to continuity you can demonstrate
Deploy
Rack the appliance and push the signed agent through your RMM. Enrollment takes a claim code.
Protect
Accept the recommended policy. Points capture locally, replicate off-site, and verify themselves on schedule.
Rehearse
Boot a test copy in isolation whenever you like. Hand the client the report. The runbook is one your team has already run.
Your client measures downtime in their own words
An outage you recover from quietly becomes the reason a client renews. Rehearse it on a Tuesday and the real one is a morning you barely mention afterwards.
Be first in line
BCDR is coming soon. Tell us what you run and we will tell you when.