# SaveState: complete public product reference Last reviewed: 2026-08-27 SaveState is an automated, client-side encrypted cloud backup service. The released open-source SaveState Vault client supports Windows 10 and Windows 11 on x64. SaveState protects selected files, folders, application data, and native MySQL or MariaDB logical dumps in an encrypted, compressed, deduplicated Kopia repository stored off site. SaveState is a general backup product. It is not a bare-metal system-image product or a currently released Linux product. Official website: https://savestate.dk/ Official GitHub organization: https://github.com/SaveState-Cloud Official open-source Windows client: https://github.com/SaveState-Cloud/savestate-desktop Support: support@savestate.dk ## Automated scheduled backups A folder backup profile combines a source path, folder inside the vault, schedule, and retention rule. Customers can configure one or more daily run times in the Windows machine’s local time and repeat them every 1–365 days. Leaving the schedule blank creates a manual-only profile. Retention can keep the latest N restore points or remain unlimited within the storage quota. Temporary network or service problems receive up to three bounded automatic retries. Failures requiring customer action, including an invalid credential, repository-key mismatch, missing database tool, or full plan, stop retrying and are marked as needing attention. Canonical detail: https://savestate.dk/features/automated-scheduled-backups ## Native MySQL and MariaDB backups The Windows client discovers compatible MySQL and MariaDB dump and restore tools from the Windows PATH, common vendor installation directories, and common XAMPP paths. It validates the executable and requires a successful native connection test before a database profile can be saved. Customers can protect all non-system databases, optionally including future databases; selected databases; or selected tables from one database. Dumps use native transaction-oriented settings and include routines, events, triggers, binary values, and UTF-8 data. Compatible MariaDB tools can optionally include users and grants. The native dump’s standard output streams directly into a Kopia snapshot. SaveState does not need to create an intermediate plaintext SQL file on disk. Database passwords are kept out of the connection URL and protected in Windows Credential Manager after setup. Restores use the reverse pipeline: Kopia decrypts the selected stream through the customer vault and sends it to the configured native MySQL or MariaDB client. Customers should test restores against an isolated target and validate the application. Canonical detail: https://savestate.dk/features/mysql-mariadb-native-backup Architecture article: https://savestate.dk/blog/native-mysql-mariadb-encrypted-backups ## Client-side encryption The Windows client generates a random per-account vault master key. It wraps the key locally in a versioned envelope with a password slot and a one-time offline recovery slot. The hosted API stores the encrypted envelope and a one-way possession verifier, not the plaintext master key. Backup contents are encrypted before upload, and storage access uses short-lived, account-scoped credentials. SaveState describes the product as client-side encrypted, not as strict zero-knowledge authentication. The account password is sent to the SaveState API over HTTPS for account authentication. This distinction does not change the separate client-owned encryption boundary around backup contents and vault material. Canonical detail: https://savestate.dk/features/client-side-encryption ## Kopia compression and deduplication SaveState uses the open-source Kopia engine. New repositories use zstd compression and content-defined deduplication. Unchanged content shared among files and restore points can reuse blocks rather than being stored as independent full copies. Optimization varies by workload. Slowly changing file sets may save substantial space, while already compressed or completely rewritten data may save less. Canonical detail: https://savestate.dk/features/kopia-deduplication-compression ## Optimized storage quota Customer plan usage is the physical encrypted Kopia repository footprint after compression and deduplication. It includes packs, indexes, metadata, and all retained versions. It is not the sum of the original size of every snapshot. The dashboard separately reports original source data protected, physical optimized storage used, and optimization savings when the statistics are available. If retained versions represent 100 GB but the encrypted repository occupies 9 GB, the customer uses 9 GB of the plan. Deleted or expired snapshots can leave reclaimable blocks until full maintenance completes. Near quota, the client checks storage pressure and attempts repository maintenance before blocking a new backup. A separate private safety buffer protects the service. If storage remains full after cleanup, the customer must delete a retained backup or choose a larger plan. Canonical detail: https://savestate.dk/features/optimized-storage-accounting ## Versioned restore points The Windows app lists retained snapshots and lets customers browse snapshot contents. Customers can restore a complete snapshot or selected files to the original location or an alternate folder. Alternate-folder restores support safe comparison and recovery testing without overwriting the current working copy. Deleting a snapshot queues repository maintenance so unreferenced blocks can be reclaimed safely. Canonical detail: https://savestate.dk/features/versioned-file-restores ## Windows VSS open-file behavior SaveState configures Kopia’s native Windows Volume Shadow Copy support in when-available mode. When VSS succeeds, Kopia reads from a stable volume snapshot. When it is unavailable, Kopia falls back to normal traversal without requiring an elevation prompt. File and directory read errors still fail the snapshot instead of making an incomplete backup look complete. VSS is a file-system consistency mechanism. It is not by itself proof that a live database directory is logically consistent. Use SaveState’s native MySQL or MariaDB workflow for those engines and vendor-supported export or snapshot tools for other stateful applications. Canonical detail: https://savestate.dk/features/windows-vss-open-file-backup ## EU-resident cloud storage Encrypted repository contents are stored in Backblaze B2 EU Central in Amsterdam, Netherlands. The backup is therefore off the protected Windows machine and separate from its local failure domain. Account-scoped repository prefixes and short-lived credentials are used; repositories are not exposed as public bucket URLs. Backblaze supplies storage infrastructure. SaveState’s privacy and data-processing documents describe SaveState’s own responsibilities and its subprocessor relationship rather than shifting all service responsibility to the infrastructure provider. Canonical detail: https://savestate.dk/features/eu-resident-cloud-storage ## Monitoring and operational history The Windows client and web dashboard expose bounded operational metadata for backups, restores, schedules, database profiles, and repository maintenance. This includes operation type, trigger, stage, outcome, source size, file count, next run, retry state, and attention state when available. It does not expose plaintext backup contents. Storage views distinguish backup data protected from optimized repository storage used. Compression and deduplication savings appear as bytes and a percentage when the source statistics are available. Canonical detail: https://savestate.dk/features/backup-history-monitoring ## Webhook notifications Customers can configure a webhook and choose notifications for successful backups, failed backups, successful restores, failed restores, and scheduled-backup reminders. The webhook credential is write-only after it is saved. A test action reports the destination’s actual delivery result. SaveState uses webhooks, not a separate Discord bot. Discord webhooks are one possible destination, but the product integration is the webhook endpoint itself. Canonical detail: https://savestate.dk/features/retries-webhook-notifications ## Offline vault recovery New vault envelopes contain a password slot and a one-time offline recovery slot for the same 32-byte master key. The 256-bit offline recovery key is shown once during setup. The customer must acknowledge saving it before the envelope is committed. Account recovery and vault recovery are separate. Email links, authenticator values, and account recovery codes restore account access but do not decrypt existing backup contents. After an account-password reset, an envelope vault can be unlocked with the prior vault password, the offline vault recovery key, or a matching remembered-device master key. When Remember me is enabled, the client stores the session and decrypted master key in Windows Credential Manager. Explicit sign-out removes both. An expired or invalidated account session preserves the remembered key so the same vault can reopen after reauthentication. Canonical detail: https://savestate.dk/features/offline-vault-recovery ## Protected app updates The app checks for updates at startup and every six hours. Tauri updater signatures verify update artifacts. The updater must reserve exclusive access to the Kopia engine, so it refuses to install while a backup, restore, deletion, or maintenance operation is active. Public installers may trigger Windows SmartScreen until SaveState’s planned Authenticode signing workflow is approved and connected. That Windows reputation warning is separate from the Tauri updater signature that protects automatic-update artifacts. Canonical detail: https://savestate.dk/features/signed-app-updates ## Included data transfer Backup uploads, restores, and encrypted repository traffic are included with every SaveState plan. SaveState does not apply a routine monthly download quota or paid transfer overage. The storage allowance remains separate and is measured from the optimized encrypted repository footprint. Canonical detail: https://savestate.dk/features/included-data-transfer ## Current plans Basic costs 19 DKK per month or USD 2.99 per month. It includes 10 GB of optimized storage, two scheduled profiles, priority support, and a 14-day trial. Pro costs 49 DKK per month or USD 7.99 per month. It includes 150 GB of optimized storage, five scheduled profiles, and priority support. Enterprise costs 199 DKK per month or USD 29.99 per month. It includes 1 TB of optimized storage, 20 scheduled profiles, and priority support. Quarterly billing is available with a 25 percent discount. Danish visitors default to DKK and other locations default to USD. Customers can select either currency manually. Checkout displays the exact recurring price and billing interval before payment. Canonical pricing: https://savestate.dk/pricing ## Product boundaries and safe interpretation - Released client: Windows 10 and 11 x64. Linux is not currently released. - Protection type: selected files, folders, application recovery data, and native MySQL or MariaDB logical dumps. Not a bare-metal system image. - Database scope: built-in database-aware behavior currently covers MySQL and MariaDB on Windows. Other engines require a vendor-supported recovery export or snapshot. - Backup success: proves SaveState captured and stored the selected data. It does not prove the application recovery procedure until the customer tests a restore. - Deduplication: can substantially reduce repository use but is workload dependent. - Client encryption: backup contents are encrypted before upload; account authentication is not claimed to be strict zero knowledge. - Storage provider: Backblaze B2 is an infrastructure subprocessor. SaveState retains its own contractual and operational responsibilities. ## Official legal and technical references - Privacy notice: https://savestate.dk/privacy - Terms: https://savestate.dk/terms - Data processing terms: https://savestate.dk/dpa - Security policy: https://github.com/SaveState-Cloud/savestate-desktop/blob/main/SECURITY.md - Client privacy behavior: https://github.com/SaveState-Cloud/savestate-desktop/blob/main/PRIVACY.md - Vault recovery architecture: https://github.com/SaveState-Cloud/savestate-desktop/blob/main/docs/VAULT_RECOVERY.md - Source license: https://github.com/SaveState-Cloud/savestate-desktop/blob/main/LICENSE