Backup & archiving
Scheduled, incremental backups from Windows, macOS and Linux, with restore points you can preview and verify. Archiving keeps older material out of the way without deleting it.
Real EverBox Desktop Agent interface. Device name and version are from the captured build; no customer data is shown.
Two different jobs
Both keep copies. They answer different questions: “can I recover this?” and “must I still keep this?”. Mixing them usually makes both harder.
A backup captures copies on a schedule so a deleted, corrupted or encrypted file can be restored from an earlier point.
An archive holds files you no longer work on but must retain, in a location that is separate from daily storage.
How a job runs
The Desktop Agent executes the job, but the policy lives on the server. That keeps a fleet of laptops consistent.
Choose the folders on the device that need protection. The job is defined in the Everabyte console and mapped to the local path.
Set the schedule, the retention period and the destination bucket. Exclusions keep caches and temporary files out of the backup.
The Desktop Agent scans the folder, compares content hashes and uploads only what changed through the encrypted pipeline.
Preview a restore point, recover the files you need, then verify the result before closing the incident or the request.
The agent protects the files and folders you select. It is not a disk-image, bare-metal or virtual-machine backup product, and it does not claim to restore an operating system.
The Desktop Agent
The agent runs as a single desktop application. API credentials are stored in the operating system keystore, and the app talks only to Everabyte — provider credentials never reach the device.
API keys are held in Windows Credential Manager, macOS Keychain or the Linux Secret Service — not in a configuration file and not in logs.
Recovery
Recovery is a procedure, not a button. These are the four steps that make it defensible.
Each completed run creates a point you can return to. Retention determines how far back the list goes.
Compare the selected point with the current state so you know which files will be replaced or added.
Run a restore to a separate folder and open the files. A backup that has never been tested is still a hypothesis.
When the same path exists in the backup and on the device, choose to keep both rather than lose the local copy.
Platforms
The same application is packaged for Windows, macOS and Linux. Installation files and version notes live on the downloads page.
See installation packagesRetention depth and archive options depend on the plan and the destination configuration.
Installer package for managed desktop fleets, with credentials held in Windows Credential Manager.
Application bundle with credentials stored in the macOS Keychain.
Binary for workstations and server-side file sets, using the Linux Secret Service.
Before you rely on it
If a folder is not in the job, it is not protected. Review the selection when a user changes role or device.
Older restore points expire according to the retention you configured. Long-term legal archiving is a separate decision.
Schedule a periodic test restore and record the result. Without it, the first real recovery becomes the test.
Install the agent on a single workstation, run a backup, restore two files and compare them. That short exercise answers more than a feature list.
Tell us how many devices you manage, what must be recoverable and how long you need to keep it. We will help size the jobs and the archive.
Retention, capacity and Object Lock availability depend on the selected plan and configuration.
