Enori Documentation

Manage your Enori account — profile, plan and usage limits, add-ons, notifications, connected sign-in providers, GDPR data export, account deletion, and scoped API keys.

Plans and prices, the 14-day trial and what happens when it ends, subscribing and changing plan, every add-on and what it costs, VAT, payment failures, cancelling and resubscribing.

Monitor any URL for uptime, status codes, keywords, JSON and header assertions, response size and speed — with automatic TLS certificate expiry alerts, security-header grading and content-change detection.

Monitor DNS records for hijacks, bad zone edits and failover mistakes — pick a record type, set expected values and match mode, and alert per condition or on cross-region divergence.

Track domain registration expiry, registrar, transfer locks, nameservers and DNSSEC — with a 60/30/14/7/3/1-day warning ladder and domain-hijack early-warning alerts.

Check whether a host is reachable and how fast it answers, measure real ICMP packet loss and alert on it — plus when a Port or Website monitor is the better tool.

Monitor cron jobs and scheduled tasks by having them ping Enori — get alerted when a run is late, fails or hangs, with copy-paste snippets for cron, CI, Kubernetes and systemd.

Monitor real user journeys — login, checkout, signup — in an actual browser, with per-step screenshots, video on failure, encrypted credentials, Core Web Vitals, and what each interval costs.

Monitor any TCP or UDP port — SSH, SMTP, databases, brokers — with one-click presets, and assert on the reply so you know the right service answered, not just that a socket opened.

Monitor multi-step API workflows — log in, extract a token, call the protected endpoint — with per-step assertions, encrypted variables and TOTP, failure artifacts, and an auto-pause circuit breaker.

Your first screen — six panels you can reorder and hide, a time range and client scope you can save as named views, and a live activity feed that marks itself read.

Track reliability against measurable targets, get alerted when burn rate is unhealthy, generate customer-facing SLA reports.

Send OpenTelemetry traces from your app to debug latency and errors span by span — with a service map, RED health charts, RED alerts, and AI root-cause analysis.

Generate uptime and SLA reports for any period on demand or on a recurring schedule emailed to your clients, export them to PDF or CSV, and share a public link — with accurate, maintenance-excluded metrics.

Embed a live uptime, status or response-time badge for one monitor in your README or docs — switching it on per monitor, what that publishes, the four shields.io styles, and the five-minute cache.

Publish the live status of your services at a public URL — on your own domain and branding, with components derived from your monitors, incident and maintenance history, email and webhook subscribers, an RSS feed and a status badge.

Every configuration change on your account is recorded automatically — who did what, when, and from which IP. Filter, search, and export your audit history to CSV.

See every cron job and scheduled task in one place — live Up/Down/Late status, a month calendar of runs, and a day-by-day timeline, all shown in UTC.

Declare planned downtime so deploys and migrations never page you — checks keep running, alerts and incidents are suppressed, and the window is excluded from your uptime numbers.

See everything firing right now in one place, set up where downtime alerts go — email, Slack, Discord, Teams, webhooks or PagerDuty — then tune what each monitor fires on and escalate to an on-call rota when nobody answers.

The bell and the notification centre — every event Enori records for you, what each one means, where clicking takes you, how long they are kept, and how they differ from alert channels.

One forward-looking list of what is about to happen — certificate and domain expiries, the next run of every cron job, scheduled maintenance, snoozes ending, report deliveries and billing deadlines — grouped by urgency over a horizon you choose.

One calendar for every event across all your monitors — incidents, maintenance, cron runs, alerts, SSL and domain expiries, and config changes. Export a range or subscribe from your calendar app.

Share monitors with colleagues without sharing your account — invite by email, set Viewer or Editor, and understand exactly what each role can touch (incidents stay with the owner).

The record of every outage — when Enori opens one, the six statuses, acknowledging and resolving, evidence captured at the first failure, post-incident reviews, and how MTTA and MTTR are actually measured.

Disconnect an AI client, rotate an API key with a 24-hour overlap, or revoke one outright — and why removing the connector inside Claude revokes nothing.

REST API for programmatic monitor, incident, alert, and status-page management.

Drive Enori from Claude Desktop, Claude.ai, or any MCP client. OAuth-or-API-key auth, 57 tools covering monitors, incidents, alerts, status pages, browser checks, and SLOs.

Static source IPs for browser (synthetic) checks — add them to your firewall, IP allowlist, or bot-protection rules so our monitors can reach you.