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.
A small agent on each machine does the work, and a console you sign into manages it. Your data goes straight from your machines to the storage you chose, and never passes through our servers on the way. This page covers how it works, what it does and what is coming next.
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.
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.
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.
Switch on Object Lock and every backup is locked for the days you choose. Ransomware, a stolen password or a mistake cannot delete or change it until the lock ends. Satkosh storage uses Governance mode, which keeps one emergency route through the storage provider. On your own storage, Compliance mode leaves none.
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.
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.
Copying a running database's files does not give you a usable backup. So for MySQL, MariaDB and PostgreSQL, Satkosh asks the database for a consistent copy at each backup, with its users and permissions, while people carry on working. The database password never leaves your server.
Pick a date, look at what was there, and bring back a single file or an entire folder, to wherever you choose on the machine.
If the folder you restore to already exists, the files land in a new folder inside it. Check them, then move them where they belong. A restore cannot make a bad day worse.
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.
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.
A database comes back as a new database beside the live one, so the one in use is never touched. Check it, then switch over. It works onto a replacement server too, or you can take the dump files and load them yourself.
A restore puts back owners, permissions, ACLs and SELinux labels, not just the contents of the files, so restored services can read what they need.
Three views show whether each machine is covered, how its backups ran and whether the machine itself is in good condition.
Whether each machine is covered, measured against its schedule.
The result of every run, with files, data, duration and any errors.
Disk space, memory and warnings for each machine, with a forecast of when a drive will be full.
What Satkosh can read from, and where it can write to. Anything marked on the roadmap is not available in the pilot.
Windows Server 2016 and later. Runs quietly in the background, and 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.
Ubuntu 22.04 and 24.04, Debian 12 and 13, and Red Hat, Rocky Linux, AlmaLinux and Oracle Linux 8, 9 and 10. One command installs it. The same schedules, retention and reports as Windows, so a mixed set of machines stays one thing to look after instead of two.
Windows 10 and 11. 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, it catches up when it comes back, and the gap is written down rather than quietly skipped.
MySQL, MariaDB and PostgreSQL, on Linux and Windows servers. Satkosh asks the database itself for a consistent copy at each backup, and a restore loads it into a new database beside the live one. Other software, such as Microsoft SQL Server, works through a script that runs before the backup.
Buy storage from us and we set up a bucket for you alone, sized to what you need, and look after it. 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.
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.
A shared folder on your office NAS, or a second disk on each machine. Genuinely useful as a fast local copy you can restore from in minutes, and Satkosh logs in to a NAS only while it works, so ransomware on a PC does not see the share. We would not recommend it as your only copy, though: storage in the same room as the servers it protects shares their fire, their flood and their burglary.
None of these is available yet, so please do not plan around them. If one matters to your business, tell us: it helps us decide what to build first.
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.
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. We start on the console once our pilot is done.
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.
One schedule that writes a local copy for speed and an off-site copy for safety. Today that takes two policies, one for each repository.
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.
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.