Aleph Vigil
Aleph Vigil is our persistent operational-awareness platform. It is designed to continuously watch the systems, networks, identities, applications, and environments Aleph is responsible for—then surface meaningful situations before small degradations become client-visible problems.
Less noise. Better data. Earlier action.
The problem with traditional support
A user notices slow Wi-Fi. A backup fails. A circuit becomes unstable. A service has been restarting for days. A certificate expires. Someone opens a ticket. Then the investigation begins.
Vigil is designed around a different assumption:
Aleph should notice first.
If a network is gradually degrading, a backup window is stretching, an endpoint loses protection, or an application dependency is becoming unreliable, Vigil should already be observing the change.
Architecture
Systems, networks, identities, applications, and sites.
Narrowly scoped workers that observe specific parts of the environment.
Correlates signals into situations.
Where situations are worked.
Review evidence, investigate causes, recommend action.
Approved responses, carried out and checked.
Sentinels are narrowly scoped workers that continuously observe specific parts of the environment. They remember enough state to recognize change, evaluate what they see, and create structured signals when something matters.
Vigil correlates those signals into situations rather than flooding people with telemetry.
Bridge is where Aleph's human and non-human intelligence can work those situations together—reviewing evidence, investigating causes, recommending action, and executing approved responses.
Examples
Instead of waiting for users to complain, Vigil can track rising retries, disconnects, latency, AP load, or other changes against historical behavior. A meaningful trend can become a situation before the site experiences a hard outage.
Packet loss, route instability, tunnel reconnects, failover events, and application latency can be correlated into one situation rather than five unrelated alerts.
Vigil can watch duration, retries, storage latency, and missed windows so a deteriorating backup process can be investigated before the day it fails completely.
If an endpoint stops reporting, a protection service becomes unhealthy, or an unexpected privilege change occurs, Vigil can surface the condition with the evidence and context needed to investigate it.
Less noise, better data
We do not measure operational maturity by how many dashboards, alarms, or tickets we can produce.
The goal is comprehensive machine awareness with minimal unnecessary human attention.
When everything is healthy, Vigil should be quiet. When something meaningful changes, it should provide enough context to understand what happened, why it matters, what has already been checked, and what should happen next.
Coverage
Vigil grows through a fleet of reusable Sentinels covering different parts of the client environment. Coverage families include:
Each Sentinel in the catalog carries a public status—Available, Pilot, or Planned—that reflects implementation evidence.
By design
Vigil is not intended to be bolted on after a project is complete. Aleph client builds—including MDC, CHEF, BOSS, infrastructure, identity, ERP, and future platforms—should be designed with Sentinel coverage from the beginning.
When Aleph takes responsibility for an environment, our goal is that environment becomes increasingly observable, understandable, secure, and proactively maintained.
More than monitoring
Vigil is being built to understand change over time, correlate multiple conditions, bring the right intelligence into the situation, and—where the client has authorized it—take bounded, auditable action.
Plans
Continuous sensing, situation formation, visibility, and proactive recommendations.
Observe plus active Aleph triage, proactive maintenance coordination, recurring optimization, and approved low-risk remediation.
Higher-assurance operations with wider Sentinel coverage, continuity and failover monitoring, stronger response commitments, and broader governed intervention authority.
Final commercial scope, pricing, and service commitments are established per engagement.
The outcome
Self-hosting matters. Open systems matter. Lower infrastructure cost matters. Good architecture matters.
Vigil exists so Aleph can keep watching after the build is finished—finding degradation, risk, and change early enough to do something useful about it.
The best support experience is often the problem the client never had to report.