Blog

Notes from building Backvera — failure modes we ship around, architecture decisions, WordPress quirks worth knowing.

All Behind the scenes Engineering Product Security Uncategorized WordPress
WordPress 7.1 "Mary Lou" release artwork
WordPress

WordPress 7.1 “Mary Lou”: what actually changed, and what to test before you update

WordPress 7.1 brings responsive styles without CSS, hover and focus states in Global Styles, image processing that runs in the browser, and…
Uncategorized

wp2shell: The WordPress Core Pre-Auth RCE, What to Do and How to Recover Cleanly

A critical pre-authentication remote code execution bug (wp2shell, CVE-2026-63030 / CVE-2026-60137) affects stock WordPress installs. Here's how to patch, how to respond…

 Three-step restore flow: dry run to preview, safety backup as a rollback point, then restore, with the live site staying online.
Product

Restores you can run on a Friday

If a restore needs a maintenance window, it is not a restore — it is a migration.

 Timeline: WP-Cron runs a 3am backup at 7am when the first visitor arrives; Backvera runs it on time at 3am.
Engineering

Why WP-Cron is not your backup scheduler

WP-Cron only runs when someone visits your site.

 Bar chart: full backups store about 10 GB over five days, while incremental stores a 2 GB baseline plus small daily changes, about 2.2 GB.
Engineering

What “incremental” actually means for WordPress backups

"Incremental" gets sprayed across the backup space like glitter. Here is what it actually means at the database and file layer.
Behind the scenes

Naming things: the etymology of Backvera

Back is backup. Vera is Latin for true. Backups you can trust.

Protect your site today. Sleep better.

Start your free trial in minutes. No card required.

Start your free trial View pricing