Title: BackupBeacon
Author: bostondeveloper
Published: <strong>Ọwẹ́wẹ̀  14, 2026</strong>
Last modified: Ọwẹ́wẹ̀  15, 2026

---

Ṣàwárí àwọn plugin

![](https://ps.w.org/backupbeacon/assets/banner-772x250.png?rev=3694961)

![](https://ps.w.org/backupbeacon/assets/icon-256x256.png?rev=3694961)

# BackupBeacon

 Láti ọwọ́ [bostondeveloper](https://profiles.wordpress.org/bostondeveloper/)

[Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/backupbeacon.3.6.6.zip)

 * [Àwọn àlàyé](https://yor.wordpress.org/plugins/backupbeacon/#description)
 * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/backupbeacon/#reviews)
 * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/backupbeacon/#developers)

 [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/backupbeacon/)

## Àpèjúwe

Most backup failures are silent: the job stopped running weeks ago and nobody noticed.
Backup plugins grade themselves. BackupBeacon is the independent watchdog that does
not.

**How it works**

 1. Add each backup destination (UpdraftPlus to Drive, database dumps to S3, your hostÌtumọ̀
    Yorùbá: ’s nightly snapshots) with a freshness limit in hours.
 2. Point your backup job at the token-authenticated ping endpoint: `POST /wp-json/
    backupbeacon/v1/ping/<destination-id>?token=...`. Every successful backup pings;
    the token is rotatable and pings are rate-bounded.
 3. BackupBeacon evaluates every destination hourly (WP-Cron): fresh, stale (past its
    limit), or silent (never recorded, or a clock-skewed future timestamp). Backdated
    recordings are refused.
 4. When a destination turns stale or silent, the site admin gets an email and a persistent
    admin notice Ìtumọ̀ Yorùbá: – once per incident, not once per cron tick. A dashboard
    widget rolls every destination into one ALARM/OK beacon, and the event log records
    when each destination went stale and when it recovered.

No account, no external service, no per-site fees. Your backup jobs ping your own
site; the watchdog runs where the backups matter.

**Optional premium plans** unlock faster checks (15-minute cadence), more alert 
channels (Slack/Discord/webhook), escalation and maintenance windows, per-destination
alert routing, a status API, multisite and white-label agency tooling. Upgrades 
happen inside your dashboard Ìtumọ̀ Yorùbá: – no reinstall, no license-key copying
Ìtumọ̀ Yorùbá: – and every feature you use today stays free forever.

**What it is not**: BackupBeacon does not make backups. It is the alarm for the 
tools that do.

## Àwọn àwòrán ìbòjú

[⌊The BackupBeacon dashboard: every destination rolled into one ALARM/OK beacon,
with per-destination freshness state.⌉⌊The BackupBeacon dashboard: every destination
rolled into one ALARM/OK beacon, with per-destination freshness state.⌉[

The BackupBeacon dashboard: every destination rolled into one ALARM/OK beacon, with
per-destination freshness state.

[⌊Destination setup: token-authenticated ping endpoint with rotatable token and 
freshness limit in hours.⌉⌊Destination setup: token-authenticated ping endpoint 
with rotatable token and freshness limit in hours.⌉[

Destination setup: token-authenticated ping endpoint with rotatable token and freshness
limit in hours.

## FAQ

### Which backup plugins does it work with?

Any of them. If your backup tool can run a curl command (or a WP-CLI line) after
it finishes, it can ping BackupBeacon. It is deliberately backup-plugin-agnostic.

### Does it need an external account?

No. Pings arrive at your own WordPress site and evaluation runs on WP-Cron. Nothing
leaves your server except the alert email to the admin.

### What happens if my backup job never pings?

That is the point. Silence past the freshness limit flips the destination to stale(
or silent if nothing was ever recorded) and the alarm fires.

## Àwọn àgbéyẹ̀wò

Kò sí àwọn àgbéyẹ̀wò fún plugin yìí.

## Àwọn Olùkópa & Olùgbéejáde

“BackupBeacon” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa
sí plugin yìí.

Àwọn Olùkópa

 *   [ bostondeveloper ](https://profiles.wordpress.org/bostondeveloper/)

[Túmọ̀ “BackupBeacon” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/backupbeacon)

### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?

[Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/backupbeacon/), ṣàyẹ̀wò
[ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/backupbeacon/), tàbí ṣe àgbékalẹ̀
sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/backupbeacon/) nípasẹ̀
[RSS](https://plugins.trac.wordpress.org/log/backupbeacon/?limit=100&mode=stop_on_copy&format=rss).

## Àkọsílẹ̀ àwọn àyípadà

#### 3.6.6

 * Cloud email alerts (edge relay delivery) are now an Accelerator/Studio feature:
   the relay never sends on Free/Starter/Pro, relay controls are locked with an 
   upgrade link on lower tiers, and stored relay settings are preserved (never used)
   while unentitled.

## Àkójọpọ̀ Meta

 *  Ẹ̀yà **3.6.6**
 *  Ìgbàgbọ́hùn tó kẹ́yìn **ọjọ́ 2 sẹ́yìn**
 *  Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **Tó kéré sí 10**
 *  Ẹ̀yà WordPress ** 6.0 tàbí ju bẹ́ẹ̀ lọ **
 *  Dánwò dé **7.1**
 *  Ẹ̀yà PHP ** 7.4 tàbí ju bẹ́ẹ̀ lọ **
 *  Èdè
 * [English (US)](https://wordpress.org/plugins/backupbeacon/)
 * Àwọn àmì
 * [alerts](https://yor.wordpress.org/plugins/tags/alerts/)[backup](https://yor.wordpress.org/plugins/tags/backup/)
   [cron](https://yor.wordpress.org/plugins/tags/cron/)[monitoring](https://yor.wordpress.org/plugins/tags/monitoring/)
   [watchdog](https://yor.wordpress.org/plugins/tags/watchdog/)
 *  [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/backupbeacon/advanced/)

## Àwọn ìbò

Kò sí ìwádìí tí a tíì fi ránṣẹ́.

[Your review](https://wordpress.org/support/plugin/backupbeacon/reviews/#new-post)

[Wo gbogbo àwọn àgbéyẹ̀wò](https://wordpress.org/support/plugin/backupbeacon/reviews/)

## Àwọn Olùkópa

 *   [ bostondeveloper ](https://profiles.wordpress.org/bostondeveloper/)

## Ìrànlọ́wọ́

Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́?

 [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/backupbeacon/)