simon.holliday

<p>FlexiCache is a fast, full-featured and flexible caching system which will improve the performance and availability of any WordPress site.</p>
<p>It is highly configurable to allow unlimited caching rules – expiring different pages at different times, not caching some pages at all, caching multiple versions of the same page depending on browser, language, and so on.</p>
<p>FlexiCache will also work straight out of the box without any need for complex configuration.</p>
<h4>Features</h4>
<ul>
<li>Extensively configurable using user-defined conditions</li>
<li>Handling of high-traffic periods where multiple clients may simultaneously request uncached or expired items</li>
<li>Standalone mode which bypasses WordPress and third-party theme and plugin code to serve cached pages faster</li>
<li>Choice of storage engines: Filesystem, Memcache and SQLite</li>
<li>Pre-caching functionality to cache new versions of pages before the existing ones expire</li>
<li>SQLite indexing of Filesystem and Memcache stores to speed up removing specific items from the cache (automatically enabled if SQLite is available)</li>
<li>Sends appropriate HTTP cache headers to the requesting client</li>
<li>Serves files in compressed formats accepted by the requesting client</li>
<li>Compatible with WordPress MU</li>
</ul>
<h3>Upgrading FlexiCache</h3>
<p>FlexiCache stores config and cache data within the plugin directory (see plugin documentation in versions 1.2.4.2 onwards for the reason why).</p>
<p>If you upgrade the plugin using WordPress’s built-in upgrade process, the entire plugin directory will be replaced, including your config and cache data.</p>
<p>To preserve these, take a copy of the “plugins/FlexiCache/_data” directory before upgrading, and then copy it back after the upgrade is complete.</p>
<p>If you upgrade directly via SVN, this should not be required, since only the files under version control will be updated.</p>
<h3>Deactivating FlexiCache</h3>
<p>FlexiCache can be disabled via the admin interface as with any plugin, however if you are running in Standalone mode, you should remove the .htaccess modifications before deactivating the plugin.</p>
<p>For a standard WordPress install, this modification can be done via the admin interface, however it is recommended that you make this change manually, especially if using WordPress MU, where multiple sites may share the same .htaccess file.</p>
<p>Please see the documentation supplied with the plugin (accessible via WordPress’s admin interface) for more information.</p>


FlexiCache

FlexiCache is a fast, full-featured and flexible caching system which will improve the performance and…

lukmeyer

<p>LukStack Uptime Monitor is a lightweight yet powerful website monitoring solution built for agencies, freelancers, and web professionals who manage multiple websites.</p>
<p>Track uptime, response times, and SSL certificate expiration for all your client sites from a single WordPress dashboard. When something goes wrong, you will know immediately through email notifications or webhook integrations with Slack, Discord, and other services.</p>
<h4>Reliable Monitoring Out of the Box</h4>
<p>Unlike plugins that rely on WordPress Cron (which only runs when someone visits your site), LukStack Uptime Monitor includes a <strong>built-in remote cron server</strong> operated by the plugin author and hosted on AWS in the EU (Frankfurt) region. Your site is automatically registered on plugin activation and the server triggers your monitoring checks every minute — reliably, even on low-traffic sites. Aggregate environment data (WordPress/PHP versions, locale, site count) is transmitted to keep the service compatible; no admin emails, user accounts, or visitor data are sent. See the Privacy section for the full field list. No third-party cron services like cron-job.org or UptimeRobot required.</p>
<h4>Free Plan Features</h4>
<ul>
<li><strong>Uptime Monitoring</strong> – Automatic checks every 15 minutes</li>
<li><strong>Monitor up to 2 websites</strong></li>
<li><strong>Webhook Support</strong> – Native integration with Slack, Discord, Microsoft Teams, and generic webhooks</li>
<li><strong>Manual Checks</strong> – Test any site instantly with one click</li>
<li><strong>Dashboard Widget</strong> – Quick status overview right on your WordPress dashboard</li>
</ul>
<h4>Pro Plan Features</h4>
<ul>
<li><strong>Everything in Free</strong></li>
<li><strong>Monitor up to 100 websites</strong></li>
<li><strong>5 minute check interval</strong> for faster downtime detection</li>
<li><strong>SSL Certificate Monitoring</strong> – Get warned before certificates expire</li>
<li><strong>Website Performance Tracking</strong> – Monitor response times with millisecond precision</li>
</ul>
<h4>Who Is This For?</h4>
<ul>
<li><strong>Web Agencies</strong> managing client websites</li>
<li><strong>Freelancers</strong> maintaining multiple projects</li>
<li><strong>Site Owners</strong> who want peace of mind</li>
<li><strong>DevOps Teams</strong> needing a simple monitoring solution</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Add a website URL to monitor</li>
<li>LukStack Uptime Monitor checks the site automatically</li>
<li>If the site goes down or returns an error, you get notified</li>
<li>When the site recovers, you get a recovery notification</li>
</ol>
<h4>Webhook Integrations</h4>
<p>LukStack Uptime Monitor automatically formats notifications for popular services:</p>
<ul>
<li><strong>Slack</strong> – Rich message attachments with color-coded severity</li>
<li><strong>Discord</strong> – Embedded messages with status information</li>
<li><strong>Microsoft Teams</strong> – Via generic webhook connector</li>
<li><strong>Zapier / Make</strong> – JSON payload for custom automations</li>
</ul>
<h4>Privacy</h4>
<p>LukStack Uptime Monitor stores the URLs you choose to monitor and their status data. No personal information (admin emails, user accounts, site content) is collected by the plugin itself.</p>
<p>The plugin does transmit data to the following external services:</p>
<ul>
<li><strong>LukStack Cron Server</strong> (operated by the plugin author, hosted on AWS EU Frankfurt) — receives your site URL, a locally generated shared secret, and aggregate environment data (WordPress/PHP versions, locale, site count, multisite flag, Freemius opt-in status) on plugin activation and on each authenticated trigger response, then triggers monitoring checks on your site every minute. Your Freemius user ID is included <strong>only</strong> if you have actively opted in via the Freemius dialog. See the External services section below for the full field list.</li>
<li><strong>Freemius</strong> (license management and opt-in usage tracking) — anonymized data only when you explicitly opt in. See https://freemius.com/privacy/</li>
<li><strong>Webhook URLs</strong> (Slack, Discord, etc.) — only when you configure them and only when a monitored site changes status.</li>
</ul>
<p>All external transmissions are described in detail in the External services section below.</p>
<h3>External services</h3>
<p>This plugin connects to external services as part of its core monitoring functionality. Below is a description of each service, what data is sent, and when.</p>
<h4>Monitored Websites</h4>
<p>LukStack Uptime Monitor sends HTTP requests to the website URLs you add for monitoring. This is the core functionality of the plugin and is required to check uptime and response times. An SSL connection on port 443 is also made to check the SSL certificate expiration date for HTTPS sites (Pro). These requests are sent automatically by the built-in cron server (see below) and when you manually click “Check now”. The data sent is a standard HTTP GET request with a custom user agent header. No personal data is transmitted.</p>
<h4>LukStack Cron Server</h4>
<p>This plugin connects to the LukStack cron server to ensure reliable monitoring checks even when your WordPress site has no visitors. Because no dedicated privacy policy URL is published for this service, the full data-handling details are documented below.</p>
<p><strong>Service operator</strong></p>
<p>Operated by Luk Meyer (plugin author). Contact: via the WordPress.org support forum for this plugin (https://wordpress.org/support/plugin/lukstack-uptime-monitor/).</p>
<p><strong>Hosting and location</strong></p>
<p>Hosted on Amazon Web Services (AWS), region eu-central-1 (Frankfurt, Germany). Data does not leave the EU. The service uses AWS Lambda, AWS DynamoDB, and AWS EventBridge Scheduler. AWS acts as a data processor under a standard data processing agreement.</p>
<p>Server endpoint: https://gt5zheubf8.execute-api.eu-central-1.amazonaws.com</p>
<p><strong>What data is transmitted FROM your site TO the cron server</strong></p>
<p>On plugin activation and when an admin visits the WordPress admin (throttled with exponential backoff):</p>
<ul>
<li>Your site URL (value of WordPress home_url())</li>
<li>A 48-character shared secret, randomly generated on your site, stored in your own wp_options table. This secret is used only to authenticate incoming trigger requests. It is not a WordPress password or account credential.</li>
<li>The plugin version (e.g. “2.4.0”)</li>
<li>Aggregate environment fields used to understand which WordPress/PHP combinations are in use: WordPress version, PHP version, site locale (e.g. “en_US”), multisite flag, and the number of websites you have added to monitoring.</li>
<li>A coarse Freemius opt-in status label: one of “paying”, “trial”, “pending”, “registered”, “anonymous”, or “unknown”. This lets the operator distinguish anonymous from opted-in installs in aggregate metrics.</li>
<li>Your Freemius user ID (numeric) — <strong>only</strong> if you have actively opted in via the Freemius dialog. Anonymous installs never transmit this field.</li>
<li>The same payload is included in the response of each authenticated trigger request, so the operator sees up-to-date environment data over time.</li>
</ul>
<p>No admin email, no user account email, no site content, no visitor data, and no credentials are transmitted. Sites running on <code>localhost</code>, <code>127.0.0.1</code>, or reserved TLDs (<code>.local</code>, <code>.test</code>, <code>.localhost</code>, <code>.example</code>, <code>.invalid</code>) are excluded from registration entirely.</p>
<p><strong>What data is transmitted FROM the cron server TO your site</strong></p>
<p>Every minute, the cron server sends an HTTP POST request to the REST endpoint /wp-json/lukstack/v1/trigger on your site, authenticated via the X-LukStack-Secret header. The request body is empty. The sole purpose of this request is to trigger the plugin’s internal monitoring logic.</p>
<p><strong>What data is stored on the cron server</strong></p>
<ul>
<li>Site URL</li>
<li>Shared secret (needed to authenticate triggers — transmitted over HTTPS only)</li>
<li>A SHA-256 hash of the site URL used as record key</li>
<li>Plan type (Free or Pro) — used to gate trigger frequency server-side</li>
<li>Plugin version, WordPress version, PHP version, site locale (e.g. “en_US”), multisite flag, and the number of monitored sites — used to understand environment compatibility and prioritize fixes</li>
<li>Freemius opt-in status label (“paying”, “trial”, “pending”, “registered”, “anonymous”, “unknown”) — used to distinguish opted-in installs from anonymous in aggregate metrics</li>
<li>Your Freemius user ID — <strong>only</strong> if you have actively opted in via the Freemius dialog</li>
<li>Timestamps: registration time, last successful trigger, last failed trigger, consecutive failure counter</li>
<li>Last error message if any</li>
</ul>
<p>No logs of monitored sites, no uptime data, no visitor data, no admin emails, no user account emails, no site content.</p>
<p><strong>Data retention</strong></p>
<p>Data is kept only as long as the plugin is installed on your site. When the plugin is uninstalled, the plugin best-effort calls a <code>/v1/deregister</code> endpoint on the cron server with your site URL and secret, after which the record is removed. If the deregister call fails (e.g. network error or transient backend issue), the site is additionally marked inactive on the cron server after approximately 100 consecutive failed trigger attempts (about 100 minutes) and no further requests are sent. Inactive records may be purged periodically.</p>
<p><strong>Your rights and how to exercise them</strong></p>
<p>You can at any time:</p>
<ul>
<li>Disable the remote cron by deactivating the plugin — triggers stop, but the record remains on the server until auto-expiry. To remove the record immediately, fully uninstall the plugin: the plugin sends a deregister call on uninstall.</li>
<li>Request deletion of your site’s record by posting in the plugin’s WordPress.org support forum with your site URL (or a hash of it). Records are typically deleted within 7 days of a confirmed request.</li>
<li>Rotate the shared secret by re-registering (the settings page exposes a “Force re-register now” button when WP_DEBUG is enabled in your wp-config.php).</li>
</ul>
<p><strong>Security</strong></p>
<ul>
<li>All transmissions are over HTTPS (TLS).</li>
<li>Incoming triggers to your site are validated using hash_equals() (constant-time comparison) to prevent timing attacks.</li>
<li>The shared secret is stored with autoload disabled and is not exposed in the admin UI unless WP_DEBUG is enabled.</li>
</ul>
<p><strong>Legal basis (GDPR)</strong></p>
<p>The processing described above is necessary for the performance of the service you enabled by installing this plugin (Art. 6 (1) (b) GDPR). The data processed consists of technical identifiers (URL, secret, timestamps), aggregate environment metadata (versions, locale, site count, multisite flag, opt-in status), and — only when you opt in via Freemius — your Freemius user ID. No special categories of personal data (Art. 9 GDPR) are involved.</p>
<h4>Freemius</h4>
<p>This plugin uses Freemius SDK for license management, usage tracking (opt-in only), and the upgrade flow. When a user opts in, anonymized data such as the site URL, WordPress version, PHP version, and plugin version may be sent to Freemius servers. Users can opt out at any time.</p>
<p>This service is provided by Freemius, Inc.<br />
Terms of Service: https://freemius.com/terms/<br />
Privacy Policy: https://freemius.com/privacy/</p>
<h4>Slack (optional)</h4>
<p>If you configure a Slack webhook URL in the plugin settings, LukStack Uptime Monitor sends POST requests to the Slack Incoming Webhooks API when a monitored site changes status (goes down, recovers, or has SSL issues). The data sent includes the website URL, its status, response time, and a timestamp. No personal data is transmitted.</p>
<p>This service is provided by Slack Technologies, LLC / Salesforce, Inc.<br />
Terms of Service: https://slack.com/terms-of-service<br />
Privacy Policy: https://slack.com/privacy-policy</p>
<h4>Discord (optional)</h4>
<p>If you configure a Discord webhook URL in the plugin settings, LukStack Uptime Monitor sends POST requests to the Discord Webhooks API when a monitored site changes status. The data sent includes the website URL, its status, response time, and a timestamp. No personal data is transmitted.</p>
<p>This service is provided by Discord, Inc.<br />
Terms of Service: https://discord.com/terms<br />
Privacy Policy: https://discord.com/privacy</p>
<h4>Generic Webhooks (optional)</h4>
<p>You may configure any third-party webhook URL (e.g. Microsoft Teams, Zapier, Make, or a custom endpoint). When a monitored site changes status, a POST request with a JSON payload is sent to that URL. The data sent includes the website URL, its status, response time, and a timestamp. No personal data is transmitted. Please refer to the terms of service and privacy policy of the respective service you configure.</p>
<h3>Additional Information</h3>
<h4>Requirements</h4>
<ul>
<li>WordPress 5.8 or higher</li>
<li>PHP 7.4 or higher</li>
<li>PHP extensions: curl, openssl, json</li>
</ul>
<h4>Support</h4>
<p>For support questions, please use the WordPress.org support forum for this plugin.</p>
<h4>Credits</h4>
<p>Developed by Luk Meyer.</p>


LukStack Uptime Monitor

Monitor multiple websites for uptime, performance, and SSL certificate expiration. Built-in remote cron for reliable checks — no third-party services  …

FlexiCache vs LukStack Uptime Monitor