Architecture

Regulaxy is a web application that runs entirely inside your network. Nothing in it depends on a cloud component, there is no online licence check and no telemetry — a fully disconnected network is the environment the system was built inside.

An outbound internet call is a deployment choice, not a property of the product. Some of the source systems you can connect to are cloud services, and connecting one does produce an outbound call — but only after somebody has explicitly configured it. On a disconnected deployment you simply do not configure those, and the system works in full without them. The system catalog says so on the row itself wherever the answer is not a plain yes.

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.