OpsGate

OpsGate is a hybrid WordPress site operations and alert automation platform.

The OpsGate WordPress plugin connects a WordPress site to the OpsGate platform so the site can participate in evidence-backed triage, reports, alerts, history, and operational visibility.

The plugin is a compact site companion and connector. It is not a second full dashboard. Deeper account, report, alert, billing, portfolio, and agency management happens in the OpsGate web console according to the site’s plan.

OpsGate helps answer one practical question:

What is the condition of this site right now, why is it in that condition, and where do I need to act?

What OpsGate provides

• Public/external checks for Free sites.
• Connected WordPress triage for Starter and higher plans.
• Evidence-backed posture summaries.
• Site-scoped reports and history.
• Alert routing according to plan limits.
• Operational visibility for site owners, operators, and agencies.
• Hybrid plugin + web console workflows for Pro and Agency plans.

Tier model

Free:
External/public checks only. Free does not require connected plugin credentials and does not imply authenticated WordPress inventory, plugin, theme, PHP/runtime, or update-posture truth.

Starter:
Plugin-led connected triage for one connected site, with limited reports and alert routing according to the active plan.

Pro:
Hybrid plugin + web console operations for deeper site triage, reports, alerts, activity, and settings according to Pro limits.

Agency:
Hybrid multi-site and portfolio operations for agencies managing multiple WordPress sites.

Product surface model

The installed WordPress plugin is the local connector and site companion.

The OpsGate web console is the management layer for account, billing, reports, alerts, portfolio, activity, and deeper operations.

This separation keeps the plugin site-scoped and avoids exposing broad account or portfolio controls inside every connected WordPress admin.

Privacy and authority model

OpsGate uses the OpsGate API and canonical backend records as the source of truth for connected site identity, triage runs, reports, alerts, and plan limits.

The plugin does not act as the authority for plan entitlement, run truth, report truth, or alert truth.

External Services

This plugin connects your WordPress site to the OpsGate platform, a software-as-a-service operated by Cyber Eclipse (Québec, Canada), to provide site assessment, reporting, alerting, and operational visibility. This section discloses the external communication the plugin performs, in accordance with the WordPress.org Plugin Directory Guidelines.

OpsGate platform (api.opsgate.ca / mcp.opsgate.ca)

This is the only external service the plugin contacts directly. It is the service that performs and stores the site assessment, reports, alerts, and plan entitlements; the plugin is a connector to it.

• Data transmitted: your site address; and, for connected (Starter and higher) plans after you complete pairing, technical WordPress configuration data — plugin and theme inventory (names, versions, update status), rate-limited PHP error summaries (containing no site-visitor data), and aggregate WooCommerce order-volume counts (containing no order or customer details). Free public checks transmit only your site address and public signals; no authenticated inventory is collected.
• When data is transmitted: when you run a public check or connected scan, when the plugin refreshes site status, and when it checks for plugin updates (update metadata is served from the OpsGate platform).
• Account requirement: connected plans require an OpsGate account and a pairing step; free public checks do not require an account.
• Terms of Service: https://opsgate.ca/terms
• Privacy Policy: https://opsgate.ca/privacy

Sub-processors used by the OpsGate platform

The plugin does not contact any of these services directly. The OpsGate platform uses them on its own servers to deliver the Service; they are listed here for transparency because your data may reach them through OpsGate. Their use, the data involved, and the applicable jurisdictions are described in full in the OpsGate Privacy Policy (https://opsgate.ca/privacy).

• Stripe — payment processing for paid plans. Data: billing details you enter at checkout. When: only during subscription signup or management. Terms: https://stripe.com/legal | Privacy: https://stripe.com/privacy
• Anthropic — optional AI-generated report summaries. Data: your site’s assessment findings (no site-visitor data). When: only when an AI summary is generated for a connected scan. Terms: https://www.anthropic.com/legal/consumer-terms | Privacy: https://www.anthropic.com/legal/privacy
• WPVulnerability and the NIST National Vulnerability Database (NVD) — vulnerability intelligence. Data: plugin/theme names and versions from your inventory, to look up known advisories. When: during a connected scan. WPVulnerability: https://www.wpvulnerability.net/ | NVD: https://nvd.nist.gov/developers/terms-of-use
• RDAP domain registries — domain-expiry lookups. Data: your site’s domain name only. When: during a scan that checks domain/SSL expiry.

Alert delivery channels (optional, you configure them): if you choose to receive alerts through a messaging channel, you paste that channel’s destination (for example a Discord or Slack webhook URL such as https://discord.com/api/webhooks/…, or a Telegram bot token and chat_id) into OpsGate. The plugin only stores the destination you provide; it does not itself contact the channel. The OpsGate platform performs the actual delivery when an alert fires, sending only the alert content you have configured. Channels supported this way include Telegram (https://telegram.org/privacy), Slack (https://slack.com/trust/privacy/privacy-policy), Discord (https://discord.com/privacy), Microsoft Teams (https://privacy.microsoft.com/privacystatement), Amazon SNS (https://aws.amazon.com/privacy/), and Twilio/WhatsApp (https://www.twilio.com/legal/privacy). No alert channel is contacted unless you configure one.

By installing and connecting this plugin, you acknowledge that site data is transmitted to the OpsGate platform as described above and governed by the linked Terms of Service and Privacy Policy.

From WordPress.org when publicly listed

1. In WordPress Admin, go to Plugins > Add New.
2. Search for “OpsGate”.
3. Click Install.
4. Click Activate.
5. Open the OpsGate menu in WordPress Admin.
6. Follow the onboarding instructions to run a public check or connect the site to OpsGate.

From a ZIP package during beta or custom distribution

1. Download the current OpsGate plugin ZIP from the official OpsGate distribution path.
2. In WordPress Admin, go to Plugins > Add New.
3. Click Upload Plugin.
4. Choose the OpsGate ZIP file.
5. Click Install Now.
6. Activate the plugin.
7. Open the OpsGate menu in WordPress Admin.

Free public check

Free users can run public/external checks without connecting authenticated WordPress inventory.

The plugin may help identify the current site URL and guide the user to the public check or upgrade path.

Starter, Pro, and Agency connection

Connected plans use an OpsGate-authorized pairing flow.

1. Create or open your OpsGate account.
2. Add or select the WordPress site.
3. Generate or open the connection flow from OpsGate.
4. Complete pairing from the WordPress plugin.
5. Once connected, run site triage and review results according to your plan.

Do not manually invent account IDs, site IDs, or API credentials. Use the OpsGate connection flow.

1. 

   OpsGate compact WordPress companion surface in the WordPress admin.

2. 

   Connected site evidence breakdown: inventory, updates, vulnerabilities, uptime and performance.

3. 

   Evidence-backed scan summary with per-dimension scores and recorded evidence.

4. 

   OpsGate web console overview for a connected site.

5. 

   Alert destinations and supported delivery channels.

6. 

   Client-ready report generation with tier-aware output formats.

7. 

   Generated report history with per-format downloads for a connected site.

0.10.8

• Remote companion rebuilt as premium 2026+ SaaS connector experience (Slice 5.12).
• Two-path onboarding: Free public check vs Connect with Pairing Code.
• State-aware shell: onboarding_required, free_public_companion, connected_companion, credential_invalid, disconnected variants.
• Repair banner for credential_invalid and disconnected states with direct CTA.
• Hero band: identity block (site name + URL), tier badge, connection mode/status pills.
• 2-card topline grid: score with tone-color left border, last-checked timestamp.
• Scope card in secondary column sidebar: scope label, site, URL, mode.
• Support diagnostics section: collapsed behind Open support diagnostics affordance.
• Refresh tertiary action in connected_companion hero actions.
• Surface shape policy harness updated to locked tab architecture (no standalone clients tab for Free/Starter/Pro).

0.10.7

• Aligned release version contract to 0.10.7 across plugin header, update metadata, and DB release row.
• Closed the Multi-Site Onboarding + Context Law implementation: canonical onboarding session table, 6 API endpoints, remote plugin creates DB session before every central handoff, central resolver reads session token first.
• Closed the remote onboarding to paid connection lifecycle: pending_auth sessions can be claimed by any operator account, pairing session auto-advances onboarding session to pairing_ready.
• Closed requested-site paid lifecycle on remote proof sites: wrong-account safe handoff, setup/pairing binding to requested site, remote connected readback from API-backed truth.

0.10.6

• Fixed remote paid-pairing lifecycle: roster suppression, pairing button states, account_id mismatch on session resolve.
• Fixed pending_auth session claim and pairing auto-bind for remote to paid lifecycle.
• Fixed remote onboarding to paid connection lifecycle.

0.10.5

• Closed the final central WP Admin Alerts and Activity readback gap for the entitled vulnerability-delivery proof path.
• Recorded human-confirmed Gmail receipt for the canonical vulnerability alert proof destination.
• Promoted the stable public package and update metadata to 0.10.5.