Resilient backups
for the businesses
that can't afford to lose anything.
A small agent on each machine backs up whole drives, file by file, into per-device encrypted cloud storage — storage that machine hasno permission to delete a backup from. Scheduled, versioned, verified, and managed from one console.
Encrypted on the machine, with its own key per device. Deduplicated and compressed before anything is uploaded.
Fleet overview
Three moving parts. You only ever install one.
Paste a registration token into the agent once. Everything after that — schedules, retention, restores, updates — is driven from the console, and keeps running whether or not anyone is logged in.
1 · Agent on the machine
A Windows service that backs the machine up on schedule and keeps working when the console is closed and nobody is logged in. A backup source can be a folder or a whole drive.
- Whole drives, or the folders you name
- Open files read through a shadow copy
- Deduplicated, compressed and encrypted before upload
- Self-updating, with automatic rollback
2 · Your own encrypted vault
Every device gets its own repository inside your workspace's bucket, with its own key and its own scoped credentials. No key is shared between devices, and no device key can delete a backup.
- Per-device repository, per-device key
- Versioned restore points, not a mirrored copy
- Retention you set, in days and in count
- Old points expire from the server, never from the endpoint
3 · One console for the fleet
Health, jobs and failures for every machine in one place, updating live as jobs run — no refresh button, and no per-device remote session to check on a backup.
- Fleet health score and a failed-snapshot queue
- Browse any snapshot before you restore it
- Alerts when a scheduled backup does not happen
- Workspaces, roles and invites for your team
Not a sync folder. A versioned history of every drive.
File sync gives you the latest copy of a file — including the latest encrypted copy, if something got to it first. Backupinsta keeps every restore point separately, so there is always a version from before.
Every run adds a restore point.
Retention decides which ones age out — nothing overwrites.
A whole drive is a valid source
Point a policy at C:\ and D:\ and the agent walks the tree and takes what it finds — minus a built-in exclusion list of Windows scratch files: page file, hibernation file, recycle bin, browser caches,*.tmp, node_modules. The accounts data, the shared folders, the user profiles and the application directory nobody documented are in scope without anyone having to remember them. Or name specific folders instead, with your own exclusions on top.
Files that are open and locked, read through a shadow copy
A backup does not have to wait for everyone to go home. Each run asks Windows for a shadow copy of the volume and reads the files out of that, so a database or a mailbox that is mid-write is read as it stood at one instant rather than being skipped. If a run finds a shadow already stuck from a crashed one, it clears it and carries on.
If the shadow-copy service cannot start on a machine at all, the run still goes ahead without one — files that were locked at that moment are skipped, listed by name against the job, and the run is flagged rather than filed as a clean success.
Schedules and retention you actually control
A policy sets the frequency — hourly inside a window, daily, weekly or monthly — the compression, the exclusions, and how long restore points survive, in days and in number. It then applies to every device attached to it. Change the policy and the whole group follows. No per-machine scheduled task to maintain, and no cron job that quietly stopped firing in March.
Only what changed leaves the machine
Repeated content inside a machine's own history is stored once, and after the first run only new and changed content is uploaded — a nightly backup of a server that changed by 2 GB moves roughly 2 GB, not the whole drive again. The console shows the real split for every run: scanned, after dedup, after compression, uploaded. It is a measurement, not a vendor ratio.
Reading it back is the only feature that matters.
Most days it is one file someone deleted. Sometimes it is a folder tree. Sometimes it is everything that was on a machine that will not switch on again. The same restore points answer the first two outright, and get the third one's data onto a machine that still works — open a restore point, look inside it, and decide where it lands.
Look inside before you commit
Open any restore point and walk it like a filesystem — any folder, any depth. Filter, tick what you want, and the free space at the destination is checked before the restore starts rather than halfway through it.
One file, straight to your browser
A single file comes out of storage directly — no agent, no restore job, no waiting on the machine it came from. It works while that machine is switched off, lost, or in a box under someone's desk.
Back onto the machine
Every path returns to exactly where it came from, or into one folder you choose — each source landing in its own subfolder, so two drives never merge into one heap. Existing files are overwritten or skipped, and you pick which before it starts.
Onto a different machine
Restore one device's data onto another device in the workspace. The machine it came from does not have to be online — or still exist. Point at one that is, and the data lands there.
The agent runs as a service.
Nobody has to be logged in for a backup to happen.
Every machine, every job, every failure — on one screen.
Click the sidebar. This is the real UI, with demo data in it. Jobs stream live as they run: the console is fed by the backend as events happen, so what you are looking at is the current state and not a page you have to remember to refresh.
Fleet overview
Live jobs
3 runningFailed snapshots
Oldest firstFleet health · last 30 days
41 devices| Device | Status | Protected |
|---|---|---|
| ACC-SRV-01 Windows Server 2022 · agent 2.4.1 | Online | 1.9 TB |
| WH-NAS-02 Windows Server 2019 · agent 2.4.1 | Online | 842 GB |
| FIN-LAP-14 Windows 11 Pro · agent 2.4.1 | Online | 184 GB |
| FIN-LAP-09 Windows 11 Pro · agent 2.4.1 | Online | 151 GB |
| DEV-WS-03 Windows 11 Pro · agent 2.4.1 | Online | 410 GB |
| RETAIL-POS-07 Windows 10 IoT · agent 2.3.9 | Offline | 28 GB |
| OPS-WS-11 Windows 11 Pro · agent 2.4.1 | Online | 96 GB |
Nightly Active
- Runs
- Every day at 02:00
- Sources
- C:\ and D:\ — whole drives
- Keep
- 90 days · max 120 points
- Devices
- 9 servers
Laptops Active
- Runs
- Hourly, 08:00–20:00, weekdays
- Sources
- C:\Users — profiles and Documents
- Keep
- 30 days · max 200 points
- Devices
- 24 laptops
Shared drives Active
- Runs
- Every day at 23:00
- Sources
- E:\Shared
- Keep
- 365 days · max 400 points
- Devices
- 5 file servers
Retail 1 device offline
- Runs
- Every day at 22:30
- Sources
- C:\POS — excludes *.log
- Keep
- 14 days · max 30 points
- Devices
- 3 terminals
Click the sidebar, pick a restore point, tick files — it all works.
The boring part, done properly.
A backup product is a product that holds a copy of everything. Here is exactly what that copy is protected by, and what it is separated from.
🔐 Encrypted before it leaves
Data is deduplicated, compressed and encrypted on the machine, then uploaded. The agent's own configuration — tokens, repository credentials — is held AES-256 encrypted at rest, with the key protected by the operating system's own keystore on Windows.
🧱 One vault per device
Each device gets its own repository, its own encryption key and its own scoped storage credentials inside your workspace's bucket. That credential writes only to its own device's folder and can delete no backup data at all — and one endpoint's key cannot make sense of another endpoint's history, because it does not hold that repository's key.
🛡 Tenant isolation by construction
Every workspace is a separate bucket and a separate set of devices, and the workspace on a request is taken from the verified session token — never from a header, a body field or a URL. The identity is not something the request gets to state.
📡 The agent opens no inbound port
Commands reach the agent over an outbound, per-device stream with its own scoped credentials; results come back over ordinary HTTPS. There is nothing listening on the endpoint for an attacker to find, and no firewall hole to open.
⏱ A silent device is a visible device
Every agent checks in roughly once a minute. Miss enough of those and the device turns up in the failed-snapshot queue on its own — the failure mode of most backup setups is not a loud error, it is months of quiet, and quiet is what this watches for.
👥 Workspaces, roles and expiring invites
Separate workspaces per client or per site, owner / admin / member roles governing who can administer a workspace and who can remove things from it, and invite links that expire rather than sitting in an inbox forever.
The machine cannot delete its own backups
Encryption stops a backup being read. It does nothing about a backup beingdeleted — and ransomware looks for the backup target first. The credential we issue to an agent can write new data and read that device's own history. It carries no permission to delete backup data at all: there is no command the endpoint can send, no flag an attacker can pass and nothing a disgruntled admin can do from that machine that removes a restore point. Expiring old points happens from the server, with a credential the endpoint never sees — and every device key is re-checked against that policy hourly.
"It ran" and "it got everything" are two answers
When a run finishes, every snapshot it wrote is checked against the repository — the tree is walked and every object it references is confirmed present. If that check cannot finish, the run is recorded as unverified rather than quietly as a success. A run that stored far less than the pre-scan expected is flagged, and any file it had to skip is listed by name against the job.
Bring your own storage Roadmap
Point a workspace at your own S3-compatible bucket or an on-premise object store and keep the console. Priced as a seat rather than by capacity.
Agents update themselves
A new build is downloaded, checked against its SHA-256, and swapped in by the agent itself — with the old binary kept and rolled back automatically if the new one fails to start. The outcome is recorded per device. No login to forty machines to install a patch.
Reports you can hand to an auditor Roadmap
Scheduled PDF and CSV summaries — protection coverage, success rate, failures and retention proof — emailed on the first of the month.
Priced on the storage you hold. Nothing else is gated.
Every tier runs the same agent, keeps the same restore points and restores the same four ways — the plan changes how much you can store and how quickly we answer the phone, not what the product will do for you in an incident. No egress charge to read your own data back. Quoted ex-GST; 18% applies and is ITC-claimable.
Trial
50 GB across the workspace
- The whole product, nothing held back
- Whole-drive file backup
- All four restore paths
- Turns into a paid plan or stops
Starter
250 GB across the workspace
- Whole drives or named folders
- Open files read through a shadow copy
- Schedules, exclusions and retention
- Fleet console, alerts and activity
- Email support
Pro
1 TB across the workspace
- Everything in Starter — same engine, same restores
- Four times the storage allowance
- Priority support with response targets
- Onboarding and policy review
Enterprise
Allowance sized to your fleet
- Everything in Pro
- Storage sized and reviewed with you
- Named contact, agreed response times
- Supervised first restore on your own data
- Invoiced annually, PO accepted
Storage is measured from the object store itself, after deduplication and compression — not from what was on disk. Extra storage is ₹6 per GB per month.Restores and egress are free on every plan, including the trial.
The three things most businesses are already doing.
All three hold a copy of something. None of them tell you when they stopped.
| When you need to… | Cloud file sync | An external drive | Backupinsta |
|---|---|---|---|
| Get back a file deleted last Tuesday | If version history goes back far enough | If someone plugged the drive in on Tuesday | Any retained restore point |
| Recover from ransomware | The encrypted file syncs too | Encrypted as well, if it was connected | The machine's own key cannot delete a restore point |
| Get a dead machine's data onto a working one | Only what was in the sync folder | If you can find the drive, and it still reads | Pick the dead device's restore point, pick any online machine, restore |
| Back up a machine nobody logs into | Needs a signed-in user | Needs a person | Runs as a Windows service |
| Trust that last night's snapshot is readable | No check | No check | Verified after it is written; short runs and skipped files are flagged |
| Find out it stopped happening | Per-user, no fleet view | Ask around | Every missed slot is detected and alerted — and it tells a machine that was off from an agent that did not fire |
The ones people actually ask.
What exactly runs on my machines?
One Windows service and a small tray application. The service does the work and starts with the machine, so backups happen whether or not anyone is logged in. The tray app is only there to show status and let someone start a run by hand. Nothing listens for inbound connections — the agent reaches out, so there is no port to open and nothing on the endpoint for an attacker to find.
Do you have a macOS or Linux agent?
Not today. The agent ships for Windows, and that is the only platform we will put a number against. The file-level engine underneath it carries no Windows-specific code, so the remaining work for other platforms is building, signing and notarising rather than a rewrite — but nothing ships, and we are not going to give you a date for something that has not been built.
Can you read my data?
Data is encrypted on your machine before it is uploaded, and each device's repository has its own key. What we operate is the orchestration — schedules, job state, device health — not a readable copy of your files. To be precise rather than flattering about it: this is not a zero-knowledge product. The repository key is issued and held by the service, encrypted at rest, so that restores can be driven from the console and a lost password does not mean lost backups. If you need a key only you hold, we do not do that today.
Can it rebuild a whole machine — bare-metal recovery?
No. Backupinsta does not sell or support disk imaging or bare-metal recovery. It backs up files — including every file on a drive, if that is what you point it at — and it restores files. It will not rebuild a machine's operating system, its installed software or its licences.
So the honest shape of a dead-server day is this: you install Windows and your applications from your own media, and Backupinsta puts the data back — or you restore that machine's data onto a different machine in the meantime and keep working. If a one-click whole-machine rebuild is what you are shopping for, this is not the product for that job, and we would rather you knew now than in an incident.
What happens when a laptop is asleep or off the network?
The run is missed and the console says so — a sweeper walks every schedule slot using the same arithmetic the dashboard predicts with, so a missed slot raises an alert and can tell a machine that was switched off from an agent that failed to fire. The agent picks the schedule back up when the machine wakes, and it holds the machine awake for the duration of a run it started. A missed slot is not caught up retrospectively — the next scheduled run is the next one.
Does it slow the machine down?
The first run is the expensive one, because everything is new. After that the agent still walks the tree, but only new and changed content is hashed and uploaded, and repeated content inside that machine's own history is stored once. Schedules exist so the heavy runs land at 02:00 rather than at 14:00.
Where is the data stored?
In S3-compatible object storage — a dedicated bucket per workspace, and one repository per device inside it. Pointing a workspace at your own bucket or an on-premise store is on the roadmap and is not shipped; it is marked as such on this page rather than sold as available.
What if we leave?
Restores and egress are free, so you can pull everything back down before you go. There is no exit fee, and no charge that only appears when you try to read your own data.