Satkosh

Calls: Monday to Saturday, 9 AM to 7 PM IST

Book a demo
Documentation

How Satkosh works

Two things do the work: an agent on each machine, and a console you sign into. They travel deliberately different routes, and that split explains most of the rest of the documentation.

Last updated 7 November 2026

The agent and the console

  • The agent reads the files you told it to protect, encrypts them on the machine, and sends them straight to your storage over your own connection
  • The console decides what runs and when, and records what happened. That is all it ever sees
  • Your backup data never passes through a Serverstock server. It comes to rest on storage we provide only if you chose to buy storage from us
  • We hold your storage credentials encrypted, which is what lets backups run unattended and lets us help you recover
  • Choose zero-knowledge instead and we hold nothing we can read, at the cost that a lost password means nobody can recover that data, including us
  • Each machine holds its own credential rather than a shared one

Words the console uses

Client
The business a machine belongs to. This is the hard boundary in the product: devices, policies, jobs and reports never cross it, and one client can never see another's.
Device
One protected machine, physical or virtual.
Repository
Where backups are stored, plus the encrypted credentials needed to reach it.
Policy
The whole definition of a backup: what to protect, how often, how long to keep it, and where it goes.
Job
One run of a policy against one device. It succeeds, it fails, or it is recorded as missed.
Restore point
What a successful job leaves behind, and what you browse and restore from.
Retention
How long copies are kept, on tiers that hold the latest, hourly, daily, weekly, monthly and yearly copies at the same time.

Supported systems

All 64-bit. Each machine needs outbound HTTPS (port 443) to the Satkosh server and to your storage. No inbound ports are needed, because the agent always starts the connection.

  • Windows PCs: Windows 10 and 11
  • Windows servers: Windows Server 2016 and later
  • Linux servers: Ubuntu 22.04 and 24.04, Debian 12 and 13, and Red Hat Enterprise Linux, Rocky Linux, AlmaLinux and Oracle Linux 8, 9 and 10, on Intel or AMD with systemd
  • Databases: MySQL, MariaDB and PostgreSQL, on Linux and Windows servers