Aleph Vigil · Sentinel Fleet
Vigil grows through a fleet of narrowly scoped Sentinels. Each Sentinel watches a defined part of the environment, keeps enough state to recognize meaningful change, and reports when something deserves attention.
The Sentinel Fleet is how Vigil keeps expanding what Aleph can understand, protect, and improve across client environments.
How to read this catalog
Each card shows a public status. A Sentinel is labeled Available only when it is implemented and approved for client deployment; until then it is shown as Pilot or Planned.
No Sentinels match these filters.
8 Sentinels
Designed to track the quality of a site's internet and WAN paths over time.
Designed to detect gradual wireless-quality deterioration before a hard outage.
Designed to notice when name resolution becomes slow or unreliable.
Designed to notice when devices may soon be unable to join the network.
Designed to follow the stability of routes and tunnels between sites and services.
Designed to check that a backup connection is ready before it is needed.
Designed to build a long-term picture of provider quality at a site.
Designed to notice wireless clients crowding onto some access points while others sit underused.
8 Sentinels
Designed to notice when a Sentinel stops reporting, so silence is not mistaken for health.
Designed to notice a backup process becoming less healthy before the day it fails completely.
Designed to spot storage that is filling or slowing at a rate that points to a future problem.
Designed to notice a service that keeps restarting, even when it looks up at any given moment.
Designed to give early notice of certificates and credentials approaching expiry.
Designed to notice resource pressure or hardware warnings developing on a host.
Designed to check that virtual machines and their hosts are in their expected state.
Designed to detect battery or power degradation before it affects continuity.
6 Sentinels
Designed to notice when an endpoint stops reporting or a protection service becomes unhealthy.
Designed to surface unexpected changes to privileged roles and administrative accounts.
Designed to notice configuration moving away from its approved state.
Designed to notice a service listening or reachable where it was not expected.
Designed to surface sign-in activity that departs from an account's usual pattern.
Designed to notice a Sentinel that stops unexpectedly or changes outside an approved change.
5 Sentinels
Designed to notice an API becoming slower or less available than usual.
Designed to notice data that stops moving between connected systems, or moves with errors.
Designed to notice work piling up or no longer being processed.
Designed to connect symptoms in one application to a failing service it depends on.
Designed to notice application errors rising over time, including after a change.
4 Sentinels
Designed to notice ERP workflows ending in exceptions more often than usual.
Designed to notice approvals that have waited longer than expected.
Designed to notice transactions failing or being rejected at an unusual rate.
Designed to notice records in connected systems drifting out of agreement.
5 Sentinels
Designed to notice temperatures moving outside an expected range, or trending toward it.
Designed to notice refrigeration that is struggling to hold its target temperature.
Designed to notice loss or instability of power at a site or piece of equipment.
Designed to notice a sensor that has gone silent or is reporting implausible values.
Designed to notice doors or enclosures left open, or opened at unexpected times.
Plan fit is indicative: the Sentinels that apply to an environment, and the action authority they carry, are agreed with each client. Final commercial scope, pricing, and service commitments are established per engagement.