Simple Network Backup Public beta
Living product reference

What SNB supports now—and what comes next.

A plain-language guide to the protection, verification, Fleet, and restore features available in the current beta—with unsupported work kept clearly separate.

Desktop 0.4.12 public beta Agent 0.4.12 beta 1 Target service 0.4.12 beta 1 Central service 0.4.12 beta 1 Updated 15 August 2026

Current release

Supported now

These capabilities are present in the current Apple Silicon beta. Beta status still means you should keep an independent, tested backup.

Selected folders

Back up what matters

Protect chosen folders without treating SNB as a full-system imaging tool.

  • Protect multiple folders on local, external, or mounted storage.
  • Run scheduled or on-demand backups.
  • Configure exclusions, retention, and post-backup verification.
  • Continue protection in the background after closing the window.
Remote Agent

Protect remote Macs

Install a visible, outbound-only Agent on every Apple Silicon Mac you want to protect.

  • Choose folders, schedules, exclusions, bandwidth limits, and network rules.
  • Follow preparation, transfer, verification, and total backup time.
  • Validate, start, stop, and update Agents from Fleet.
  • Close the Agent window without stopping its background engine.
Recovery evidence

Know what is Recovery Ready

SNB separates a completed attempt from a recovery point that the target has actually verified.

  • Only a non-empty, zero-error point verified by the target is labeled Recovery Ready.
  • Missing, altered, incomplete, or unexpected data fails safely.
  • Browse recovery points and selectively restore files or folders.
  • Backup duration is useful status information, but never substitutes for recovery verification.
Efficient encryption

Transfer less data securely

Reduce repeat transfers while keeping plaintext on the source and target Macs you control.

  • Reuse unchanged data between backups.
  • Compress data only when compression provides a benefit.
  • Encrypt backup content on the source Mac before transfer.
  • Resume eligible interrupted preparation only after retained data is rechecked.
Fleet

Manage every Mac clearly

Use one focused view to understand Agent health, backup work, and update state.

  • See online state, last contact, version, folder access, backup status, and recovery readiness.
  • Search and filter Agents, then open one focused Agent panel.
  • Install service-listed signed updates and confirm the restarted Agent's actual version.
  • Keep delayed or failed command evidence visible instead of hiding it behind a healthy heartbeat.
Recovery authority

Keep control on the target

The central service connects authorized devices; it is not the backup repository.

  • The service is designed not to receive plaintext backup content, paths, or decryption keys.
  • Remote Agents cannot delete recovery data or control retention.
  • The target verifies a complete point before publishing it to recovery history.
  • Packages, release catalogs, and updates are signed and verified before installation.
Technical safeguards in the current beta
  • Content-defined chunking and repository-scoped content IDs allow unchanged encrypted data to be reused.
  • Adaptive Zstandard compression is retained only when beneficial, followed by AES-256-GCM authenticated encryption on the source Mac.
  • Paginated inventories, authenticated segmented manifests, and bounded transfer windows support large recovery points.
  • The target validates the exact encrypted object set in isolated staging and publishes a recovery point only after zero-error cryptographic verification.
  • Private encrypted preparation can resume after eligible network failures only after its inventory, ciphertext, content IDs, and manifest are revalidated.
  • Signed service information, release catalogs, packages, and updater metadata are checked before use.

Clear boundaries

Not supported yet

These are product boundaries, not hidden options. They remain unsupported until their implementation and acceptance evidence are published.

Beta limitation

Platform and recovery limits

  • No Intel Mac, Windows, Linux, mobile, or NAS Agent.
  • No bootable clone, bare-metal restore, or macOS system recovery.
  • No application-consistent guarantee for active databases or virtual machines.
  • No ransomware detection or immutable-storage guarantee.
  • No stable-release durability, uptime, or data-recovery guarantee.
Remote beta limitation

Operational limits

  • The target Mac must remain online with adequate destination storage.
  • The first 0.4 Agent installation requires administrator approval; later verified Agent updates can use the restricted updater.
  • Full Disk Access still requires one local user approval or an administrator-deployed MDM PPPC profile.
  • Remote schedules run in a logged-in macOS user session; logged-out system-level scheduling is not available yet.
  • Do not install an Agent update during an active backup. Wait for completion or stop the backup first.
  • Recovery evidence is tracked per configured source; aggregate cross-source history, audit export, alerting, and revocation controls are not available yet.
  • Mounted-destination replication is available; unattended cloud replication and disaster recovery remain beta roadmap work.
  • High availability for the target Mac and central service is not supported yet.
  • Verifying one very large recovery point can delay another Agent long enough for that backup to time out. Existing recovery points remain intact; avoid overlapping large jobs and retry any failed run.
  • Large-folder and multi-Mac physical acceptance now includes a verified 426,699-file recovery point; broader packet-loss, storage-pressure, and long-duration stress testing remains beta work.

Development sequence

Roadmap

Roadmap order reflects current engineering priorities. It is not a delivery-date commitment and may change as testing reveals new risks.

1
Operational hardening

Coordinate busy targets and active Agents

  • Coordinate large Agent schedules so one long target verification does not delay another backup past its progress limit.
  • Prevent Agent updates while a backup is active, then install them safely once the Agent is idle.
  • Exercise disconnect, sleep, retry, permission, and wrong-version failures on physical Macs.
  • Extend the verified 426,699-file case across heavier live-folder churn, storage pressure, sleep, and network interruption.
2
Fleet hardening

Expand administration evidence

  • Expand the current per-Agent proof into aggregate per-source history, revocation controls, audit export, and alerting.
  • Add policy revisions, acknowledgement state, staged rollout, and exception reporting.
  • Exercise multi-target failover and tenant-isolation acceptance.
3
Release promotion

Harden staged unattended updates

  • Add staged rollout rings, maintenance windows, and automatic rollback beyond the restricted verified installer.
  • Exercise Desktop/target and Agent rollback on clean Apple Silicon Macs.
  • Publish component compatibility and migration evidence with every version.
4
Offsite automation

Turn replication into disaster recovery

  • Schedule separately verified replication to S3-compatible and remote SNB targets.
  • Add replica retention, health alerts, recovery drills, and protected credential rotation.
  • Document recovery when the original target Mac is unavailable.
5
Platform expansion

Broaden coverage after macOS acceptance

  • Evaluate Windows and Linux Agents after the macOS recovery contract is stable.
  • Add application-aware quiescing for databases and virtual machines.
  • Evaluate bare-metal and system-recovery workflows separately from folder restore.

Keep another tested backup.

SNB is proprietary pre-release software. Do not use this beta as the only copy of important, regulated, legally preserved, safety-critical, or irreplaceable data.

Download the current beta