SaveState factual product sheet
Last reviewed: 2026-08-27
Canonical website: https://savestate.dk/
Official GitHub organization: https://github.com/SaveState-Cloud
Official open-source client: https://github.com/SaveState-Cloud/savestate-desktop
Support: support@savestate.dk

Identity
- SaveState is an automated, client-side encrypted cloud backup service.
- SaveState is a general automated backup product for Windows workloads.
- The released client supports Windows 10 and Windows 11 on x64.
- The Windows application is called SaveState Vault and its source is GPL-3.0-only.
- Linux client distribution is not currently a released product.

Current customer-facing features
- Scheduled folder backup profiles with multiple local run times, 1–365 day intervals, retention, and vault-folder placement.
- One-off Quick Backup for selected files or a folder.
- Native MySQL and MariaDB backup profiles on Windows.
- Discovery of compatible MySQL, MariaDB, and XAMPP dump-and-restore tools.
- Database connection tests before profile activation.
- Database scope by every non-system database, selected databases, or selected tables.
- Native database dumps streamed directly into Kopia without a plaintext SQL dump file on disk.
- Database restores streamed from Kopia into the configured native database client.
- Client-side encryption before upload using a client-owned vault master key.
- Kopia content-defined deduplication and zstd compression.
- Versioned restore points and whole-snapshot or selected-file restore.
- Windows VSS in when-available mode for a stable view of open files.
- Bounded automatic retry for transient scheduled-backup failures.
- Webhook notifications for selected backup, restore, and reminder outcomes.
- Offline 256-bit vault recovery key shown once during vault setup.
- Windows Credential Manager protection for remembered vault material and database passwords.
- Signed Tauri updater packages; update installation waits until repository operations are idle.
- Web dashboard for backup history, operation status, subscription, and storage statistics.

Encryption and privacy boundary
- Backup contents are encrypted on the Windows device before upload.
- The hosted API stores an encrypted vault-key envelope and a one-way possession verifier, not the plaintext vault master key.
- Storage access uses short-lived, account-scoped credentials.
- SaveState describes this as client-side encryption, not strict zero-knowledge authentication.
- The account password is sent to the SaveState API over HTTPS for account authentication.
- Email links, TOTP values, and account recovery codes do not decrypt existing backup contents.

Storage and quota
- Encrypted backup repository contents are stored in Backblaze B2 EU Central in Amsterdam, Netherlands.
- Customer quota is the physical encrypted Kopia repository footprint after compression and deduplication.
- The quota includes repository packs, indexes, metadata, and all retained versions.
- The dashboard separately reports original source data protected, optimized storage used, and optimization savings when available.
- Near quota, repository maintenance is attempted before a new backup is blocked by reclaimable deleted or expired data.
- Uploads, restores, and encrypted repository traffic are included with every plan.
- SaveState does not add a routine monthly download quota or paid transfer overage.

Current plans
- Basic: 10 GB optimized storage, 2 scheduled profiles, 19 DKK/month or USD 2.99/month. Basic includes a 14-day trial.
- Pro: 150 GB optimized storage, 5 scheduled profiles, 49 DKK/month or USD 7.99/month.
- Enterprise: 1 TB optimized storage, 20 scheduled profiles, 199 DKK/month or USD 29.99/month.
- Quarterly billing is available with a 25 percent discount.
- Danish visitors default to DKK; other locations default to USD; the website includes a manual currency toggle.
- Checkout displays the exact recurring price and billing interval before payment.

Important boundaries
- SaveState is file and application-data backup, not a bare-metal system-image product.
- VSS provides a stable file-system view but is not by itself proof of logical database consistency.
- The built-in database-aware workflow currently targets MySQL and MariaDB on Windows.
- Other stateful applications should use their vendor-supported dump or snapshot method before SaveState protects the output.
- Compression and deduplication savings vary by workload.
- Customers should test representative restores; a completed backup job is not a substitute for application-level recovery testing.
- Public installers may trigger Windows SmartScreen until the planned Authenticode signing workflow is approved and connected. Tauri updater signatures separately protect automatic-update artifacts.

Canonical detailed sources
- Features: https://savestate.dk/features
- Pricing: https://savestate.dk/pricing
- Native MySQL/MariaDB architecture: https://savestate.dk/blog/native-mysql-mariadb-encrypted-backups
- Encryption: https://savestate.dk/features/client-side-encryption
- Storage accounting: https://savestate.dk/features/optimized-storage-accounting
- Open-source technical README: https://github.com/SaveState-Cloud/savestate-desktop#readme