PRODUCT / HOLOVYX
A regulated estate generates evidence constantly — every change, every approval, every deviation, on every host. Holovyx turns that evidence into decisions you can defend: correlated, sealed, replayable. Not a dashboard over the mess. A layer under it.
ON-PREM · DATA-RESIDENT · MAKER-CHECKER
REACTIVE → PROACTIVE
Regulated estates run on tickets, spreadsheets, and after-the-fact audits. A change goes out. Weeks later, someone reconstructs what happened — from memory, from email threads, from whatever the ticket queue kept. Every audit is an archaeology project.
Holovyx inverts that. Every action on the estate produces evidence at the moment it happens: who proposed it, who approved it, what it touched, what moved downstream. The estate becomes observable — the whole of it. Decisions become defensible.
This is one layer, not a bundle of tools. Each module reads the same evidence, writes to the same ledger, and answers to the same controls. Patching is where it starts. It is not where it ends.
MODULE ARC
One evidence spine, one control model, successive modules. We mark status because credibility compounds: what says LIVE runs in production conditions today. What says NEXT or ROADMAP does not. No suite theater.
The first module, live today. Holovyx reads patch state across Windows, RHEL, AIX, and Oracle estates, correlates it against what BigFix and WSUS actually deployed, and seals every cycle into the ledger — what shipped, who made it, who checked it, what it touched downstream. When the auditor asks about one host on one night, the answer is a replay, not a reconstruction.
Runbook actions on regulated systems — executed under maker-checker, recorded to the same ledger as everything else.
Trace an incident backward through correlated change history instead of forward through guesswork.
The estate's evidence stream, watched continuously for deviations before they become findings.
MECHANISMS
Three mechanisms carry the layer. We describe them precisely enough to be inspected — specificity is the proof.
Change-to-impact correlation across the estate. When a change lands on a host, i-Trace maps what depended on it and what moved afterward — services, jobs, downstream systems. "What did this change affect?" becomes a query with an answer, not a meeting with a theory.
A sealed evidence ledger. Every decision on the estate becomes an entry, and Replay reconstructs it exactly as it was made — inputs, approvals, outcome. Tampering shows.
No unilateral action on regulated systems. Every consequential change requires an independent second approval, enforced in the layer itself. The approval is evidence, not etiquette — it lands in the same ledger as the action it authorized.
ENVIRONMENT MATRIX
Regulated infrastructure is not greenfield. The systems that matter have been running for fifteen years, and the tooling that runs them was chosen a decade ago. Holovyx meets the estate as it is — including the AIX host nobody wants to touch and the BigFix deployment that patches it.
Deployed inside your network. Your data never leaves.
Windows · RHEL · AIX · Oracle
BigFix · WSUS
On-prem · data-resident
ENGAGE
We don't run canned demos. Bring your environment — the platforms, the orchestration, the last audit finding that stung — and we'll run a working session against it. Holovyx came back from the field; forward-deployed engineering is where it started. Write to support@elixax.com.