Operanse
Sign inSign up

Documentation

Reference for a site that has the Operanse plugin installed, or is about to. For what the product observes, how it learns a store’s normal and what it costs a request, read how it works first.

Set up

  • Install and connectInstall the plugin, add the site in the dashboard, pair the two, and what happens in the first days.
  • Server setupThe two lines in wp-config.php: a private directory for the buffer and a system cron. Paths for common hosts, and what the admin notices mean.
  • The plugin’s settings pageEvery row of the status table, the settings decided on the site, the actions, and the constants.
  • Connection modesHow a read job reaches the site: cron polling, a persistent outbound stream, or a signed inbound request.
  • WP-CLI commandsThe wp operanse command: pair, status, flush, stream, and running a capability by hand.

Use

  • Alerts and notificationsRecipients by email, Slack, SMS and WhatsApp; each one’s minimum severity; rules, quiet hours and summaries.
  • AI assistants over MCPConnect Claude, ChatGPT or Cursor to your store’s data, read-only, with your account or a personal token.
  • Reporting from your own codeSix WordPress actions that report a form, an event, a timing, an integration call or an error from code the plugin cannot see.
  • Team and rolesOwner, admin, member and viewer, and limiting a person to certain sites.
  • Plans and billingThe trial, what each plan does with the same data, AI review limits, and the billing portal.

Reference

  • Data, privacy and deletionWhat the plugin sends, family by family, what is never sent, how long it is kept, and how to delete it.
  • TroubleshootingNot connected, cron not running, buffering in the database, a blocked uptime check, a missing alert.

Elsewhere