The platform
Everything between the scan and the night it actually happens.
Regulaxy is patch coordination software. It is not a scanner, not a deployment agent and not a ticketing system — it is the layer that turns all three into a decision about one specific night, with an owner, in writing.
- Estate
- Score
- Window
- Collision
The lifecycle
Five stages, and five things a human receives.
This is the only diagram you need to understand the product. Every capability on this page hangs off one of these stages.
Group
CVEs arrive from your scanner or your SOC feed at one row per vulnerability per host. Regulaxy folds them into the patch — the only thing you can actually schedule.
producesOne schedulable patch
Rank
Each patch is scored against the systems it touches, using your own business-impact analysis rather than CVSS on its own.
producesA score with its terms
Propose
A window that respects the system's patch cadence, its exposure tier, and whatever is already booked that night on the systems it is connected to.
producesA dated window
Agree
The system owner gets a calendar invite they can accept. The approval is recorded against the event, and an SMS goes out before the window opens.
producesAn approval and an invite
Prove
The operator works a checklist during the window, a summary goes to the owner, and the record stays in an audit log that survives deletion.
producesAn audit record
Figure 2 — the lifecycle of a maintenance window
The product map
Twelve capabilities, hung off the stage they act at.
Not a card grid. If you know where in your own week the problem sits, this tells you which page to open.
Group
One schedulable patch
Rank
A score with its terms
Propose
A dated window
Agree
An approval and an invite
Prove
An audit record
Reads the inventory, the topology and the contacts you already keep, and writes back invites, messages and tickets.
Boundaries
What Regulaxy is not.
The market is crowded at both ends — finding it and pushing it — and empty in the middle, where when gets decided. We are only the middle, on purpose.
- What to patch
Find it
Vulnerability scanners and SOC feeds. Solved, and not by us.
- When, and who agreed
Coordinate it
Windows, owners, approvals, collisions, evidence.
Regulaxy - How to install it
Push it
WSUS, SCCM, deployment agents. Solved, and not by us.
Not a vulnerability scanner
Regulaxy scans nothing. It ingests your scanner's output, and if you do not have a scanner it will not stand in for one.
Not a deployment agent
No update is installed by Regulaxy. It decides the night and records what happened in it; the installation itself stays with your own tools.
Not a CMDB, not an ITSM
The inventory is read from the sources you already keep and is not stored as a second source of truth. The ticket is raised in your system — Regulaxy only holds its number.
Regulaxy
Application server and database, on your side
- Active Directory — identities and contacts
- Exchange — calendar invites
- SQL Server and Oracle — inventory and databases
- Dynatrace and SolarWinds — topology and equipment
Architecture
All of it on your side of the boundary.
Regulaxy installs on your servers, against your database. There is no Regulaxy cloud, and no component that needs the public internet to function — not a font, not a CDN, not a licence check.
- Version updates arrive as a file you carry in, not as a download.
- No telemetry and no usage reporting. We did not collect it, so there is nothing to hand over.
- Windows Server against MSSQL, or Linux. The same build in both environments.
Integrations
It reads what you already have.
Most of what Regulaxy knows about your estate was never typed into it. It is read from the sources your teams already maintain, read-only.
- Identity and access
- Active Directory
- LDAP
- Mail and calendar
- Microsoft Exchange
- Outlook
- ICS
- SMTP
- Databases
- Microsoft SQL Server
- Oracle
- Inventory and topology
- Dynatrace
- SolarWinds
- WSUS
- Feeds and export
- CSV
- JSON
- Excel
- Notifications and tickets
- SMS gateway
- SOAP ticketing
Show us your worst window.
Bring the one that keeps slipping. Thirty minutes, your estate, no slides.
- The system with four owners
- The cluster nobody will take down
- The quarter-end freeze