// Siteorium by DEVECTUS

Know what is failing before customers do.

Siteorium is a multi-tenant website monitoring and incident escalation platform. Regional probes collect evidence, deterministic rules confirm incidents, and policy controls who is contacted by email, SMS or voice.

  • Regional evidence
  • Deterministic incidents
  • Controlled escalation
Siteorium secure sign-in screen
Secure access to tenant-scoped monitoring operations.

// Operational clarity

One calm view from signal to resolution.

Siteorium connects website checks, probe health, incidents, escalation policy, reporting and audit history without mixing one customer's operations with another's.

WebsitesPortfolio viewTenant scoped
ChecksHealthyHTTP and TLS
IncidentsConfirmed onlyEvidence attached
Probe networkRegionalHeartbeat visible

Illustrative interface summary. Status data is fictional.

Regional monitoring

Schedule HTTP and TLS checks across enrolled probes, or run a check on demand when operators need fresh evidence.

Tenant isolation

Merchant websites, roles, checks, incidents and reports remain scoped to their tenant, backed by PostgreSQL row-level security.

Deterministic incidents

A repeatable state model separates a suspected failure from a confirmed incident and prevents duplicate alert storms.

Incident operations

Acknowledge events, add notes, review a complete evidence timeline and calculate downtime when service recovers.

Policy-based notifications

Severity and routing policy decide whether configured email, SMS or voice channels should be used.

Reports and audit history

Operational reports, maintenance windows and audit records make decisions and changes easier to review.

// Signal without noise

A failure is evidence. An incident is a decision.

Siteorium uses a deterministic state model per check and region, so transient failures do not immediately become noisy incidents.

  1. 01Suspect

    The first regional failure records evidence and marks the check as suspected.

  2. 02Confirm

    A second consecutive failure opens one incident for that check and region.

  3. 03Enrich

    Later failures append evidence to the same incident instead of creating an alert storm.

  4. 04Resolve

    A successful result resolves the event and records calculated downtime.

// Built for operators

Clear boundaries, useful evidence, accountable action.

Platform roles manage the service globally while merchant roles stay tenant-scoped. Operators can inspect probe evidence, acknowledge an incident, add notes, manage escalation and review billable work without losing the history behind a decision.

  • Platform and merchant role separation
  • Probe enrolment, heartbeat, rotation and revocation
  • SSRF-aware destination validation and redirect checks
  • Maintenance windows, reports and audit records
INC-2048P1 confirmed

Customer portal availability

Australia East - HTTP availability

  1. Probe evidence receivedFirst failure marked suspected
  2. Incident confirmedSecond consecutive failure
  3. Escalation evaluatedTenant policy and route checked
  4. Service recoveredDowntime calculated and recorded

Illustrative incident using fictional data.

// Siteorium + Donova

When policy calls for a voice, Donova can make the call.

Siteorium remains the operational system of record. When voice escalation is enabled, it sends bounded incident context through a validated Donova connection so the responder can be notified and directed back to Siteorium.

01Probe evidence
02Confirm incident
03Evaluate policy
04Authenticated MCP
05Donova make_call
06Return to Siteorium

Purposeful context, not an open data pipe

Voice context is limited to the incident reference, severity, website name, detection time and operational reason. Tokens are encrypted at rest and only a fingerprint is shown in the platform.

Country-matched and fail-closed

Validated routes match the sender country. Siteorium does not fall across countries, and a disabled or invalid configured route fails closed instead of silently bypassing policy.

Siteorium architecture showing the web control plane, PostgreSQL and Redis services, regional probes, monitoring targets and notification boundaries
Initial vertical-slice architecture. Dashed areas show pilot direction; current managed notification connections are described above.

// Technical foundation

Modern infrastructure with explicit trust boundaries.

The control plane is a TypeScript and Next.js application backed by PostgreSQL with row-level security. Redis and BullMQ coordinate work, while regional probes communicate over outbound HTTPS and submit authenticated, idempotent results.

Next.jsTypeScriptPostgreSQL + RLSRedis / BullMQRegional HTTPS probesAudited provider boundaries

// See the platform

Turn monitoring evidence into controlled action.

Open Siteorium or talk with DEVECTUS about a managed monitoring setup for your websites and operational teams.