Built transparently — what is in 1.00, what is still being sharpened, and what comes next.
We believe in building GWS Backup transparently. Below is the live development pipeline: what is available now, what has shipped but is still being refined, and what comes after version 1.00.
Shipped · refining means the feature is in the product and working, not that it is waiting in a queue. It is there because calling it finished would overstate it — the behaviour is right, and the edges are still being tested and improved on real estates.
| Feature / Module | Description | Status |
|---|---|---|
| Overview | Core interface for monitoring backup health and alerts: what needs attention, what is running now, and the figures. | Implemented |
| Differential SQLite Engine | Incremental backup engine utilizing local file signature tracing. | Implemented |
| Clients | Every client in one list, with one word for its health, and each with its own Status, Restore, History and Settings. | Implemented |
| Google Auth Scopes | OAuth 2.0 integration for connecting Workspace domains. | Implemented |
| Restore | Granular recovery of individual files and emails directly to source, from one page per client. | Implemented |
| Encryption by default | New in 1.00: Drive files are encrypted by default for new clients, and email subjects, senders, recipients and labels are encrypted as well as the messages. A tool reads your backups without the app, with your key. | Implemented |
| Data Retention Logic | Automated policies for data lifecycle management. In the product and working; the windows and their wording are still being tested and sharpened. | Shipped · refining |
| Backup Scheduler | Job orchestration preventing overlapping backup runs. In use; still gathering evidence from real estates before we would call it settled. | Shipped · refining |
| Updates from the console | New in 1.00: the console tells you when an update is out and, on cPanel and Windows, installs it when you click Install. On cPanel a version that fails to start is rolled back by itself. Docker shows the two commands to run. | Shipped · refining |
| Mobile-friendly console | A console that works on a phone or tablet. From 1.00 the sidebar becomes a bar across the top on a small screen, and checking a backup ran no longer needs a desk. Still being tested on more phones. | Shipped · refining |
| Remote Purge | Ability to securely purge isolated data remotely from endpoints. Not in 1.00. | After 1.00 |
| Microsoft 365 Support | Expanding the differential engine to support Microsoft Graph APIs. | Upcoming |
| macOS installer | A native installer for macOS, in the shape of the Windows one — its own runtime, started by the system, nothing to set up by hand. | Upcoming |
Things we know about and have not fixed yet. They are here because you are more likely to trust a list that includes the awkward parts — and because finding one of these yourself, with no acknowledgement anywhere, is a worse afternoon than reading about it first. Most are aimed at the next patch.
| Issue | What you would see | Plan |
|---|---|---|
| Storage Held under-counts | Items backed up before file sizes were recorded have no size against them, so the storage figure and its forecast are both lower than reality. The console says so where it shows the number. Display only — nothing in backup, restore or retention depends on it. | Next patch |
| The Windows installer is not code-signed | Windows warns about an unrecognised publisher: More info, then Run anyway. Verify the SHA-256 on the download page if you would rather be certain — that tells you the same thing a signature would. | After 1.00 |
| Cloudflare Tunnel setup is untested | The Windows installer offers to configure a Cloudflare Tunnel. It is labelled as untested there and we mean it — leave that page blank unless you are willing to be the one who tries it. It also publishes the console to the internet with no identity check in front of it. | After 1.00 |