Built transparently — what is done, what is still being sharpened, and what is promised before 1.0.
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 is committed before version 1.0.
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 |
|---|---|---|
| Dashboard UI | Core interface for monitoring backup health and alerts. | Implemented |
| Differential SQLite Engine | Incremental backup engine utilizing local file signature tracing. | Implemented |
| Backup Console | Aggregate statistics and active endpoint management. | Implemented |
| Google Auth Scopes | OAuth 2.0 integration for connecting Workspace domains. | Implemented |
| Restore Console | Granular recovery of individual files and emails directly to source. | 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 |
| Deep Investigations | Indexed searching across all backups for specific communications. Usable now; performance and result presentation both have work left in them. | Shipped · refining |
| Workspace Admin Tools | In-app management of domain-wide settings and user provisioning. Present and working, with more of the admin surface still to cover. | Shipped · refining |
| Global Reporting PDF/Docx | Custom branded audit reports generated directly from the dashboard. | Before v1.0 |
| Remote Purge | Ability to securely purge isolated data remotely from endpoints. | Before v1.0 |
| Microsoft 365 Support | Expanding the differential engine to support Microsoft Graph APIs. | Upcoming |
| VPS/cPanel Server Backup | Direct WHM API integration to trigger and store account-level .tar.gz backups. | Upcoming |
| Mobile-friendly console | A console that works properly on a phone or tablet, rather than the desktop layout squeezed onto a small screen. Checking a backup ran should not require sitting at a desk. | 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 |
|---|---|---|
| Console screens are slow on a large workspace | The Dashboard, Backup and Restore screens worked their figures out from scratch on every visit, which on a big workspace meant a wait of seconds — and on the worst of them, long enough to look like a failure. The database layer is synchronous, so while that ran the whole console paused. Nothing was ever lost or at risk; it was a wait, not a fault. Fixed in v0.9611 — those figures are now worked out once and kept, and recalculated only when something actually changes. See the release notes. | Fixed v0.9611 |
| Windows: an upgrade keeps the old port | Upgrading from a build earlier than v0.9610 can leave the console on port
3001 instead of 3000. An upgrade never rewrites .env, because
that file holds the only copy of your encryption key. The
FAQ has the one-line fix; a fresh install is
unaffected. |
Next patch |
| 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. | Before v1.0 |
| 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. | Before v1.0 |