Every image is a real capture of the St0r interface at 1440 × 1000, taken against an isolated demo environment. The endpoints, customers, IP addresses, file names and metrics are all fabricated sample data — no production system or customer information appears anywhere in this gallery.
Each screenshot is labelled Light or Dark. Click any image to open the full-size original.
← Back to the README · Quick start · MSP Reboot
- Overview and dashboards
- Visual insights and monitoring
- Everyday workflows
- Management and configuration
- Access and administration
- How these were made
Endpoint counts, seven-day job totals, replication health, server resources, storage capacity, running backups and anything needing attention, on one screen.
The same overview in the dark theme. Theme choice is per user and persists between sessions.
Every endpoint with its customer, last file and image backup, storage against an optional quota, address and status. Filter by state or by customer.
The same list in dark, with the quota bars and status badges tuned for the dark palette.
Live progress for every running job: percentage, data transferred, throughput and estimated time remaining, with filters for state, type, endpoint and period.
Active alerts you can acknowledge or dismiss, and the rules that raise them — thresholds and delivery channels per rule.
Estate summary over a chosen period: totals, storage, backup timeline and success rate, exportable to CSV or PDF.
Health across every target, worst replication lag, and the most recent runs.
Per-target history: status, trigger, duration and bytes sent for every run, including failures.
The disk guard: free space against warning, critical and pause thresholds, with manual reclaim and the orphan prune. Backups pause before the volume can fill and resume once cleanup reclaims space.
One endpoint's status, backup history and per-endpoint actions, with its pre-configured client installers.
Pick a day that has a backup, open it, and browse into the backup to download individual files or whole folders.
Restore media and the step-by-step procedure for restoring a full system image to new hardware. The endpoints with a restorable image are listed further down the page.
Incremental and full intervals, backup windows, and how many snapshots to keep — per endpoint, with UrBackup's defaults shown beside each field.
An optional per-endpoint quota with warning and critical thresholds.
Which folders are backed up, whether the server or the client decides, and the exclusion patterns.
Which volumes are imaged, and the Windows VSS writer components to include.
Transfer mode, compression, encryption and bandwidth limits for this endpoint.
Estate-wide defaults for new endpoints, including the retention floors that an out-of-space cleanup will not delete below.
The public hostname and port that generated client installers and agent install commands point at, plus the CORS lock for the St0r API.
Storage path, ports, and the address internet clients connect to.
UrBackup's own storage, performance and speed-limit settings, edited without leaving St0r.
Each configured standby with its host, current status, replication lag and last successful run, plus per-target run, test and edit actions.
Group endpoints under a customer — expanded here to show the endpoints assigned to one. That assignment is what scopes a read-only account's visibility.
Administrator and read-only accounts. A read-only account sees only the endpoints of the customers it is assigned to.
What the client may do locally: silent updates, background backups, exiting the tray icon, which manual backups it can start, and whether it can restore.
Captured from an isolated demo environment — a separate database, a fabricated UrBackup database, and a
mock UrBackup API so the demo instance can never reach a real backup server. The tooling is in
scripts/demo/ and each shot's route and theme are recorded in the capture
manifest, so the whole gallery can be regenerated reproducibly.
Themes are switched using the application's own theme selector and verified before each capture.
The Logs page is deliberately absent: it renders the host's journalctl output, which is real system data
even when the rest of the environment is demo data.

























