Runs on a schedule, or whenever you ask
Set the schedule once for one machine or for a whole client. You can also start a backup by hand at any time, and it takes exactly the same path as the scheduled one, so testing it actually proves something.
Platform
What it does, and how
A small agent on each machine does the work, and a console you sign into manages it. Your data goes straight to your storage and never touches ours. This page is the whole picture, including the parts that are not built yet.
Backup Policies
Define what gets backed up, when, and whereSA
Serverstock AdminSERVERSTOCK TENANT
+ New Policy
| NAME | SCHEDULE | SOURCES | RETENTION | STORAGE | DEVICES | ACTIONS |
|---|---|---|---|---|---|---|
| Windows Server Policy | Every day at 11:00 PM | D:\Serverstock, D:\CorporateData | 30 latest | ● S3 | 6 | ViewEditDelete |
| Linux Infrastructure Policy | Every day at 01:00 AM | /etc, /var/www, /srv | 30 latest | ● S3 | 8 | ViewEditDelete |
| Staff Workstations Policy | Every Monday, Tuesday, Wednesday, Thursday, Friday at 5:00 PM | C:\Users, D:\WorkData | 15 latest | ● S3 | 10 | ViewEditDelete |
Restore filesPut files back on the machine they came from
Recover a deviceMove a lost machine's backup onto a replacement
STEP 1 — DEVICE
WIN-SRV-DC01 (Windows Server 2022) ▾
| DEVICE | SNAPSHOT | TARGET PATH | STATUS | REQUESTED | COMPLETED |
|---|---|---|---|---|---|
| WIN-SRV-DC01 | d5f3598f94182d19 | D:\ | ● SUCCESS | 30/8/2026, 6:09:15 pm | 30/8/2026, 6:09:21 pm |
Architecture
Two paths that never meet
Your data travels one way and your management travels another. The agent reads the files you asked it to protect, encrypts them on the machine, and sends them straight to your storage over your own connection. Separately, the console handles what to run, when to run it, and what happened, and that is all it ever sees.
The trade-off worth understanding runs the other way. Because we hold your storage credentials in encrypted form, we can run backups unattended and help you recover. Choose zero-knowledge instead and we hold nothing we can read, at the cost that a lost password means no one can recover that data, including us. Both options are real, and we would rather explain the choice than round it into a slogan.
- On your machinesA lightweight agent that runs in the background. Nothing to keep patched separately, and no on-premise backup server to look after.
- In your browserA console for schedules, monitoring and restores. For you, and for your clients if you want them to have it.
- Operated fromIndia, by Serverstock, with your backup data resting wherever you choose to put it.
- In transitEncrypted end to end, with every machine holding its own credential rather than a shared one.
Backup
Getting data off the machine
Encrypted the whole way
Data is encrypted on the machine before it moves and stays encrypted where it lands. Your encryption password never travels alongside the backup it protects.
Immutable backups
Lock a backup for a period you choose and, until that period is up, nothing can delete it or change it. Not ransomware, not someone holding stolen credentials, and not us. Available on Satkosh storage and on your own cloud storage.
Only the changes get uploaded
After the first backup, a nightly run moves a fraction of the data it protects. That means shorter backup windows, less of your internet line taken up during the working day, and a smaller storage bill.
Retention that matches how audits work
Keep hourly, daily, weekly, monthly and annual copies on one schedule, so you can answer both 'restore yesterday' and 'show me last March' without paying to keep everything forever.
Old copies actually free up the space
When a backup passes its retention date the space it was using is genuinely released. Without that, storage grows quietly forever while the console shows a tidy list, and you find out on the invoice.
Recovery
Getting it back
Go back to any date you kept
Pick a date, look at what was there, and bring back a single file or an entire folder. Put it back where it was or somewhere else, without disturbing anything around it.
Recover onto a brand new machine
When a machine is destroyed or stolen, its data goes onto a replacement. The backup belongs to the work, not to the hardware that happened to be running it, so losing the hardware does not lose the work.
Recover a machine that is already gone
The case that actually matters. You can look through and restore a dead machine's backups without that machine being switched on, reachable, or in one piece.
Database restore
On the roadmapA written, repeatable path back to a working database, so the first time you follow it is not during an incident at two in the morning.
Operations
Knowing where you stand
You hear about failures by email
A backup that fails, a machine that is overdue, a device that has stopped checking in: each raises an alert by how serious it is and emails the people you nominated for that client.
Missed backups are written down
A backup that was scheduled and can never now happen is recorded as missed rather than quietly vanishing. A machine that was off for a week reads as a week of gaps instead of a clean history.
Audit trail
Comprehensive logging of logins, restores, policy modifications, and device administration, exportable for compliance and security reviews.
You decide when the software updates
Nothing is pushed to your machines behind your back. You choose when agents update, from the console, and each one checks that an update is genuinely ours before it installs anything.
Sign in with Microsoft 365
Your tenant admin connects the Satkosh console to Microsoft 365 once, then creates users in the console. After that, anyone in your directory can sign in with their existing Microsoft account instead of a separate password. Removing someone from your directory revokes their console access instantly.
Multi-tenant MSP module
On the roadmapEvery device, policy, job and report already belongs to exactly one client, and one client can never see another's. The partner console built on top of that, with your own branding and one invoice across a client base, is still in development.
Role-based access control (RBAC)
On the roadmapGranular administrative roles, operator permissions, and read-only auditor access across console and tenant management.
Coverage
Sources and destinations
What Satkosh can read from, and where it can write to. Anything marked on the roadmap is not available in the pilot.
Sources
Windows servers and VMs
Runs quietly in the background. Files that are open or in use are captured properly rather than skipped, so a busy server does not leave holes in its own backup.
Linux servers and VMs
The same schedules, the same retention and the same reports as Windows, so a mixed set of machines stays one thing to look after instead of two.
Staff laptops and desktops
A small icon in the corner of the screen shows the person using it that they are protected, without anyone having to log in and check. If a laptop misses its backup because it was shut all week, that gets written down rather than quietly skipped.
Databases
On the roadmapPostgreSQL and MySQL automated dumps and application-consistent state capture are currently in active development on our roadmap.
Destinations
Satkosh storage, kept in India
Buy storage from us and we look after it. Your data stays in India, it stays encrypted, and if you change your mind you can move it to a bucket of your own without paying us to hand it back.
Your own cloud storage
Already have an Amazon S3 bucket, or storage with another provider? Point Satkosh at it. Your account, your access rules, your bill from them. We hold nothing except the key needed to write to it, and that is encrypted.
Local Drive
Supported, and genuinely useful as a fast local copy you can restore from in minutes. We would not recommend it as your only copy, though: a drive sitting in the same room as the servers it protects shares their fire, their flood and their burglary.
Configured Cloud & Local Storage Vaults
Zero Vendor Lock-InBackup Repositories
Configure where backup data is saved (Local or S3)SA
Serverstock AdminSERVERSTOCK TENANT
+ New Repository
| NAME | TYPE | TENANT | CAPACITY | DETAILS | ACTIONS |
|---|---|---|---|---|---|
| AWS-S3-MUMBAI-VAULT | ● S3 | Serverstock | 14.8 TB (Unlimited) | S3 Bucket: serverstock-prod-backups-mumbai | EditDelete |
| WASABI-CLOUD-ARCHIVE | ● S3 | Serverstock | 8.2 TB (Unlimited) | S3 Bucket: serverstock-cold-archive | EditDelete |
| LOCAL-STORAGE-VAULT | ● Local | Serverstock | 3.8 TB (Unlimited) | Path: /mnt/serverstock-backup-vault | EditDelete |
Roadmap
What we have not built yet
Published on purpose. A supplier who tells you what is missing is easier to check than one whose feature list has no edges. You will find out either way, and ideally not during an incident.
- Planned
Multi-tenant MSP module
The partner console: many clients under one login, your branding instead of ours, and a single invoice. Client separation and per-client reporting work today. The module built around them is not final, so we are not selling it as finished.
- Planned
Sign in with Google
Google Workspace single sign-on, so organisations that run on Google can sign in with the account they already have. Microsoft 365 SSO is already live.
- Planned
Microsoft 365
A second copy of the mailboxes (Exchange Online), OneDrive folders, SharePoint document libraries and Teams channels your business runs on, so anything deleted from them can be brought back.
No dates, deliberately. We build at a pace that lets each of these be tested properly, and a date on this page would be a guess presented as a commitment.
Book a demo
See Satkosh on your own servers
The honest test of a backup product is a recovery, not a dashboard. Book 30 minutes and we will run a real restore against a real snapshot, including onto a machine that has never seen the data before.
No spam, just a reply from our team. Managed backup by Serverstock. Made in India.