Description
Beamfar is a website monitoring service. It checks your site from outside, from two regions, and calls it down only when both agree. It also watches the TLS certificate, the domain registration and SEO signals such as noindex. Monitoring needs nothing installed on the site.
This plugin is an optional companion. It shows this site’s Beamfar status in wp-admin, so the person who works in WordPress sees it too.
The dashboard widget shows
- The status of this site: steady, slow, verifying, regional issue, down, waiting for the first check, paused, not monitored, or data unavailable. Always a word and an icon, never colour alone.
- The latest incidents of this site, with Beamfar’s explanation.
- When the TLS certificate and the domain registration expire.
- The SEO guard: what changed in the last 30 days, and whether a noindex, a robots.txt block or a canonical that points to another host is still in place, page by page.
- One link to the site’s page in Beamfar.
The widget reads only answers about this site. It never asks Beamfar on a normal page load: it shows what it saved, and refreshes a part that is due once the widget is on screen.
Heartbeat (optional)
WP-Cron runs when the site gets visits. If it stops, scheduled tasks stop without a sound. With the heartbeat on, the plugin sends a short request to the ping URL of a heartbeat check in Beamfar on a schedule. When the requests stop, Beamfar opens an incident.
Beamfar plans
New Beamfar accounts start on the Free plan: one site, with its page, certificate and DNS checked every 5 minutes and confirmed from two regions, alerts by e-mail and push, and the read-only API with 3,000 requests a month and 10 a minute, which the API and MCP share. Heartbeat checks and the security scan start with the Solo plan. The plugin itself locks nothing and shows no upgrade prompts.
External services and privacy
This plugin relies on one external service, Beamfar (https://beamfar.com/), the website monitoring service whose data it shows. Beamfar is made by the authors of this plugin. Terms of service: https://beamfar.com/legal/terms. Privacy notice: https://beamfar.com/legal/privacy.
Nothing is sent before an administrator connects this site or sets up the heartbeat. Requests go only to https://app.beamfar.com, and only over https: the address is fixed in the plugin.
What is sent, and when:
- Status of this site: when an administrator views the dashboard and part of the widget’s data is due, or presses Refresh. Read-only requests about this site only, at most 48 a day by default, with the API key in the Authorization header and the plugin name and version as the user agent (Beamfar-WordPress/1.1.0). The request path names the site’s Beamfar id.
- Connecting: when an administrator presses Save and test the key or Test the saved key, a request that checks the key, and the list of the organisation’s sites, page by page until this site is found. These count toward the same 48 a day.
- Heartbeat, off until an administrator turns it on: one GET request to the ping URL every 5 to 60 minutes, with no data, and one more each time an administrator presses Ping the saved URL now.
- Create a Beamfar account: your browser opens Beamfar’s sign-up page with this site’s address and two labels (utm_source=wordpress, utm_medium=plugin) after the # of the link, a part the browser does not send to any server; Beamfar’s sign-up page reads them in your browser and keeps the address there for up to a day to fill in the first-site box. If you sign up, Beamfar keeps the two labels with your new organisation, and this site’s address only if you add the site. The plugin itself sends nothing.
Not sent in any request: visitor data, user names or e-mail addresses, post content, the WordPress version, the site address. The plugin has no tracking and no analytics, and loads no scripts, fonts or images from other sites. Like any web request, a request shows your server’s IP address to Beamfar.
The plugin adds suggested text to Settings, Privacy, Policy Guide.
Screenshots



Installation
- Install the plugin from Plugins, Add New, and activate it.
- Open Settings, Beamfar. No account yet? Press Create a Beamfar account: once you have signed up, Beamfar’s first-site step starts with this site’s address (in the same browser, within a day), and you add the site there.
- In Beamfar, open Settings, API keys, and create a key with the read scope.
- Paste the key in Settings, Beamfar, check the host name of this site as Beamfar lists it, and press Save and test the key.
- Open the Dashboard. The “Beamfar status” widget shows the site.
- Optional, on the Solo plan and above: create a heartbeat check in Beamfar, paste its ping URL under Heartbeat, choose an interval shorter than the check’s period, and switch the heartbeat on.
On a single site, to keep the key out of the database, set it in wp-config.php, define( 'BEAMFAR_API_KEY', 'bfk_...' );, or in the BEAMFAR_API_KEY environment variable. BEAMFAR_PING_URL does the same for the ping URL. Such a key connects only this site’s own host name, with or without www; if Beamfar lists the site under another name, set that name in BEAMFAR_SITE_HOST.
FAQ
-
Do I need this plugin to monitor my site?
-
No. Beamfar checks the public site from outside and needs nothing installed. The plugin shows the result in wp-admin and adds the optional heartbeat.
-
Is the plugin made or endorsed by WordPress?
-
No. It is made by the Beamfar team. WordPress is a trademark of the WordPress Foundation, and this plugin is not affiliated with it.
-
Does the widget use my API requests?
-
Yes. Each request counts against your organisation’s API requests, which the API and MCP share. The widget reads the status at most every 5 minutes, the incidents when the status changes (else every hour), and the certificate, domain and SEO guard every 6 hours, one refresh at a time. It makes at most 48 requests a day, and testing the key in the settings counts toward the same 48, so the widget asks less that day. When Beamfar asks it to slow down, or says the month’s requests are used up, it waits as long as Beamfar says and shows the last saved status. Developers can change the daily limit with the
beamfar_daily_request_budgetfilter. -
Which API key should I use?
-
A key with the read scope, made for this site: the plugin refuses a key that can do more than read. A Beamfar key can read every site of your organisation, not only this one. The plugin keeps the key for the site it was saved with (another site needs the key pasted again), but every administrator of this WordPress site could get to the key, for example by running code on the site. Use it here only if they may see all your sites. For a client’s site, use a separate Beamfar organisation for that client.
-
Where is the key stored?
-
On a single site with BEAMFAR_API_KEY set in wp-config.php or in the environment, there, and it is never written to the database. Otherwise in this site’s options table, with autoload off, sealed with sodium under a key derived from the site’s secret keys: the ones in wp-config.php or, when wp-config.php has none, the ones WordPress keeps in the database, which a database leak exposes too (the settings page then warns). With secret keys in wp-config.php, the seal protects the key in a leaked database or database dump; it does not protect it from someone who can run code on the site or read wp-config.php. The plugin never prints the key back or logs it, and sends it only in the Authorization header to app.beamfar.com. Deleting the plugin removes it from the database, not from backups made before.
-
Why does the heartbeat report a problem on a quiet site?
-
WP-Cron needs visits. On a quiet site the pings come late. Run wp-cron.php from your server’s cron, or give the heartbeat check in Beamfar a longer grace time.
-
Does it work on multisite?
-
Each site is set up on its own, with its own key. On a network, BEAMFAR_API_KEY, BEAMFAR_PING_URL and BEAMFAR_SITE_HOST in wp-config.php or the environment are not used: every site of the network would share them.
-
How do I report a security problem?
-
Write to the contact address on https://beamfar.com/legal/imprint, not in the support forum.
-
What does uninstalling remove?
-
The settings, the saved key and ping URL, the cached data and its lock, the saved notices and form drafts, and the cron event. A key in wp-config.php or in the environment stays there. Revoke keys you no longer use in Beamfar.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Beamfar Monitoring” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “Beamfar Monitoring” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.1.0
- First release in the WordPress.org directory.
- The service address is fixed to https://app.beamfar.com: there is no address field.
- The widget reads only answers about this site, on its own schedule, at most 48 requests a day, and honours Beamfar’s “slow down” and “requests used up” answers.
- The API key and the ping URL can come from wp-config.php or the environment; otherwise they are stored sealed with sodium.
- A saved key stays with the site it was saved with, and a key that can do more than read is refused.
- Create a Beamfar account from the settings page, with this site’s address filled in.
