Architecture

Regulaxy is a web application that runs entirely inside your network. There is no cloud component, no external service, and no outbound internet call at runtime.

The components

Component	Role
Application server	The user interface and the API
Database	Application data: events, approvals, checklists, audit log
Inventory sources	Read-only. Hosts, systems and owners
Directory service	Contact search and group membership checks
Mail relay	Calendar invitations and notifications

The data the system owns

Four kinds, all created inside the system: the window events themselves, the approvals and invitations issued, the checklist responses, and the audit log.

Everything else — hosts, systems, owners, vulnerabilities — is a reflection of an external source and is re-read.

Behaviour when a source is unavailable

An unreachable inventory source does not take the system down. A short reachability probe runs before each read, so a failure surfaces in a few hundred milliseconds rather than in a long timeout. The interface states explicitly that the data is not current, rather than presenting stale rows as fresh.

Deployment

A single application process. No cluster is required, and the system is not designed to run as several concurrent copies — the reminder scheduler runs in-process, and two copies mean two reminders.