Documentation

ORTUS CHEQIT Customer Release Notes

Version: 1.0.1

Released: 2026-07-29

Release Summary

This release provides the installed ORTUS CHEQIT web application for on-premises CCTV health monitoring, activation-gated licensing, alert triage, connector management, signed updates, support bundles, and Enterprise federation/HA workflows.

CHEQIT is intended to help teams keep camera fleets usable by finding camera, stream, VMS, network, storage, and visual-quality issues before missing evidence becomes a business problem.

Version 1.0.1 Highlights

  • Public waiting-list and limited-release customer workflow with protected installer access.
  • Signed Linux installer and online/offline activation workflows.
  • Hardened public/customer API boundaries and request throttling.
  • Bounded artifact-retention reconciliation with path and symlink safety.
  • Signed in-place update staging, health checks, and rollback support.
  • Unattended online retrieval of customer-gated update archives for active cloud-licensed instances, using short-lived artifact-scoped grants.
  • Durable audit, redacted support bundles, and verified backup/restore procedures.
  • Improved live fleet health rendering and evidence-backed degradation monitoring.
  • Security and dependency refresh with no reachable Go vulnerability or npm audit finding at release validation.

Included Capabilities

  • Web dashboard with Nexus, Tree, and Map fleet views.
  • Alerts Console with search, filters, sorting, pagination, live update handling, and batch actions.
  • Alert detail pages with timeline, occurrences, image evidence, VMS archive video review where available, downloadable evidence clips, and workflow actions.
  • Activation-first operation: online activation, offline key-file activation, and delegated federation activation.
  • Licence entitlement enforcement for features, alert types, connectors, and camera allocation.
  • Camera limit management with manual selection, grouping, search, filters, sorting, pagination, and warning confirmation.
  • Local user management and profile/security workflows.
  • Enterprise authentication configuration for OIDC, LDAP/Active Directory, and trusted SAML proxy mode.
  • Per-user email notification opt-in with immediate or digest delivery.
  • Optional additional notification recipient.
  • SMTP-backed test notification.
  • Settings -> System version/update status, support bundle, and signed update installation workflow.
  • Shinobi VMS connector.
  • Direct Camera Connector for RTSP/ONVIF sources.
  • Map upload and camera placement.
  • Enterprise federation: primary/leaf operation with leaf-initiated sync.
  • Enterprise HA: active primary plus warm standby with signed replica sync, switchover, failback, and browser/leaf endpoint fallback.

Installation And Activation

Install CHEQIT on a Linux host using the signed release archive and systemd installer. After installation:

  1. Sign in as admin.
  2. Activate online with an activation code or offline with signed .key files.
  3. Confirm Settings -> Licensing shows the expected plan, expiry, features, alert types, and camera allocation.
  4. Add connectors and confirm cameras appear in the dashboard.

Before activation, normal monitoring and alert review are locked. Only the workflows needed to activate or join a licensed primary remain available.

Updates

CHEQIT supports signed in-place updates through Settings -> System. When a trusted update is available, an administrator can queue installation. The update worker verifies the release, backs up state, restarts the service, checks health, and rolls back on failure.

Installer archives remain customer-gated. Connected cloud-licensed instances retrieve an entitled archive automatically after an administrator confirms the update. Air-gapped and offline-licensed environments use the same signed offline update bundles, with identical signature, checksum, health-check, and rollback protections.

Instances still running 1.0.0 need the normal entitled portal download/offline bundle once to move to 1.0.1, because the grant client is introduced by this release. Updates initiated from 1.0.1 and later use unattended retrieval.

Federation And HA

Federation is intended for distributed deployments where remote sites process cameras locally but operations need a central view.

Recommended HA deployment uses:

  • one active primary,
  • one warm standby,
  • customer DNS/VIP/load balancer where possible,
  • shared session key/cookie-domain configuration for seamless browser handover.

CHEQIT can also recover without DNS/VIP movement after a prior browser load by using cached endpoint discovery and the app-shell service worker. This fallback does not help first-time visits to a dead hostname.

Current Limits

  • Windows installer is deferred to a later release.
  • Avigilon Unity connector work is in progress but not yet claimed as full release-supported customer workflow.
  • Milestone XProtect remains a planned future integration candidate and is not claimed in this release.
  • Full first-party SAML service-provider flow is not included; current SAML support is trusted proxy/gateway mode.
  • Production go-live tasks such as final pricing approval and production Stripe cutover are operational launch steps.

Recommended Post-Install Verification

  • /api/v1/health reports healthy.
  • Settings -> Licensing is active and shows the right entitlements.
  • Settings -> System can check update status.
  • Connectors test successfully.
  • Cameras appear in Nexus and Tree.
  • Camera allocation matches the licence.
  • Alerts Console loads and filters quickly.
  • Notification test email succeeds if SMTP is configured.
  • Support bundle downloads and is redacted.

Where To Find Help

Start with:

If contacting ORTUS support, include product version, deployment mode, licence source, approximate camera count, recent changes, relevant alert IDs, and a redacted support bundle.