Documentation

ORTUS CHEQIT Product Overview

Updated 2026-04-30

What CHEQIT Is

ORTUS CHEQIT is an on-premises CCTV health monitoring platform. It helps organisations keep camera fleets usable by detecting camera, stream, recorder, network, and visual-quality problems before missing evidence becomes an operational issue.

CHEQIT is designed for businesses, enterprises, managed service providers, and public-sector teams that operate CCTV across one or many locations.

Why It Is Needed

Most CCTV systems are checked only when somebody needs footage. By then, the camera may have been offline, blocked, blurred, misaligned, dark, overexposed, frozen, or not recording for days or weeks.

CHEQIT provides a dedicated operational layer for camera readiness:

  • It watches camera and VMS health continuously.
  • It prioritises issues in an alert queue.
  • It gives operators enough context to decide what needs action.
  • It keeps licensing, updates, and support workflows inside the installed product.
  • It can run locally, including in restricted or air-gapped environments.

Problems CHEQIT Solves

  • Silent camera outages.
  • Cameras that are connected but unusable because the image is degraded.
  • VMS or recorder issues that do not surface clearly in daily operations.
  • Manual camera-check routines that do not scale across large fleets.
  • Distributed sites where each location processes cameras locally but operations need one combined view.
  • Environments where cloud-only monitoring is not acceptable.

Core Capabilities

  • Dashboard views for fleet status: Nexus, Tree, and Map.
  • Alerts Console for queue-based triage, filtering, sorting, batch actions, and alert detail review.
  • Alert detail pages with timeline, occurrence history, image evidence, VMS archive video review where available, downloadable evidence clips, and workflow actions.
  • Operator-accepted baselines for valid camera orientations and recurring scene modes, plus camera/site alert policy for expected camera behaviour.
  • Licensing-first operation with online activation, offline key files, camera allocation, and feature/alert-type entitlements.
  • Settings for users, enterprise authentication, alert policy, notifications, connectors, maps, licensing, system updates, support bundles, and federation/HA.
  • Connectors for Shinobi VMS and direct RTSP/ONVIF camera sources, gated by licence entitlements.
  • Federated deployments with primary, leaf, and warm-standby HA roles for Enterprise deployments.
  • Signed software update workflow with update checks, confirmation, queued installation, restart, health check, and rollback support.
  • Support-bundle export with redaction of secrets and sensitive identifiers.

Deployment Shape

CHEQIT is installed on customer-controlled infrastructure. The recommended Linux deployment uses the systemd installer and runs the API and static web UI from the installed host.

Supported operating models:

  • Standalone: one CHEQIT instance monitors local VMS/cameras.
  • Primary/Leaf federation: leaf instances process cameras locally and sync metadata to a primary for a single operational surface.
  • Enterprise HA: one active primary and one warm standby. DNS/VIP/load-balancer routing is recommended, with cached endpoint fallback available for browsers and leaves.
  • Air-gapped: machine request .key files and signed activation .key files support offline activation.

Licensing

CHEQIT is licensed per camera, with plan-specific feature and alert-type entitlements. All plans default to one activation. Enterprise is the commercial lane for federation, HA, and custom activation pools.

Customers can activate online with an activation code or offline with signed key files. Administrators can review licence details, entitlements, expiration, and camera allocation inside Settings -> Licensing.

Positioning

CHEQIT is not a replacement for the customer VMS. It is a health and readiness layer that helps the VMS estate remain trustworthy.

Compared with generic monitoring or VMS-native health checks, CHEQIT focuses on the operational question that matters most: are the cameras and recordings usable when evidence is needed?

Current Release Boundaries

This release focuses on the installed web app, licensing, Linux deployment, Shinobi/direct camera onboarding, alert operations, federation, HA control-plane behavior, and signed updates.

Windows installers and some deeper enterprise integrations remain planned for later releases.