UpdraftPlus Vault is the cloud destination tied to UpdraftPlus Premium, and it writes job records and quota state to wp_options under the updraft_ and updraftvault_ key prefixes. The Vault tab inside the plugin shows current quota and recent uploads in a flat list, but it does not let you slice the run history by status, by archive type (Full, Database, Files), or by the duration of each upload. A 0 byte upload sitting alongside a 3.8 GB Full looks identical until you click in.

SleekView reads the same option rows UpdraftPlus already writes and gives each Vault upload its own row with the columns that matter: started, archive type, size shipped, duration, quota remaining, outcome. The updraftvault_quota option becomes a trend instead of a single number, because every row records the quota state at the time the upload finished. Filters on outcome equals Failed and a date window of the last 14 days catches the quiet errors the Vault tab never highlights.

Edits route through UpdraftPlus, never around it. Pruning an old archive or revoking a Vault credential uses the plugin's own actions, so the schedule, the encryption, and the quota counters stay canonical. SleekView is the read layer plus a few safe write paths the plugin already exposes; it does not race the cron, and it does not invent a parallel history table.

UpdraftPlus Vault is the destination most paid UpdraftPlus customers default to, but its admin surface is still the same vertical list the plugin shipped with years ago. The data is good; the view is thin. Failed uploads, throttled shards, and quota burn all sit inside wp_options rows that no human reads directly.

Ops engineers find out about Vault problems the night they try to restore, not the morning the quota crossed 80 percent. Finance teams renew Vault plans without a quota burn chart to support the conversation. Multi-site agencies open one Vault tab per site to do work that should be a single grid.

SleekView changes the read layer, not the backup tool: UpdraftPlus keeps owning the schedule and the encryption, and the grid simply turns the data the plugin already writes into something a human can act on. That is the difference between a backup product and a backup operations product, and it is what Vault customers stop asking the plugin to be once a real grid sits over the same option keys.