MonSPHERE

Administration

Licensing & Subscriptions

Plans, real enforced limits, and cloud / enterprise / offline license types.

Every organization has exactly one subscription, auto-created on registration.

Plans and real limits

PlanMonitorsAgentsUsersRetention
Free5137 days
Professional50102530 days
EnterpriseCustomCustomCustomCustom
CustomNegotiatedNegotiatedNegotiatedNegotiated

These aren't soft, advisory limits — creating a monitor, agent, or member past your plan's limit returns a real 403 quota_exceeded from the API, enforced server-side on the actual creation path, not just hidden in the UI.

What history retention covers

The Retention column is how long per-check history is kept. Older entries are removed automatically and never shown again, even before they're physically deleted:

  • Check history — every result of Cron Job, Synthetic, API Transaction, WHOIS, DNSBL, Screenshot, Cookie, Content Change, Certificate Transparency, Port Discovery, Core Web Vitals, Lighthouse, Accessibility, Typosquatting, Sitemap and Broken Link monitors, including step results, scores, violations and lookalike lists. A monitor's Check History opens with the latest results; Load older results goes back through the whole retention period.
  • Cron job ping history — every ping, with its run duration and caller (see Cron Job Monitoring).
  • Sitemap and broken link results — every URL of every run.
  • Notification history — every notification attempt per channel, with its status.
  • Integration logs — every webhook delivery attempt, with the response code.

Audit logs (who changed what) are kept for a platform-wide period instead — currently 180 days — see Platform Administration.

Metric time series behind dashboards and reports (response times, uptime, scores over time) are kept separately — see Infrastructure Monitoring. Deleting a monitor deletes its history right away.

Checking your usage

curl https://api.monsphere.com/api/v1/organizations/:orgId/subscription \
  -H "X-Api-Key: msph_live_..."

License types

Separately from subscription plans, a License record tracks activation for cloud, enterprise, and offline deployments. Offline licenses activate with a key that doesn't require an outbound validation call — see Deployment for air-gapped setups. Licenses can be activated, renewed, and revoked from the Platform Admin console.

Upgrading

Plan changes are applied by a Platform Admin and take effect immediately, resetting limits to the new plan's defaults — no re-provisioning required.