GAEZLA brings the work of running an estate into one operator interface:
- alert qualification, routing, delivery state, and feedback
- investigation cases using typed read-only tools from configured connections
- operation-level search and schema lookup over supported distributed API specifications
- bounded repository inspection and approval-gated pull-request proposals for IaC and configuration files
- agents, playbooks, queues, schedules, and routines for managed execution
- managed scanner assets, scan state, findings, and source provenance
- supported hardening assessment, evidence, and remediation workflows
- NIS2 and ISO 27001 workspaces plus recurring compliance-calendar tasks
- appliance bootstrap and optional-app lifecycle management
- asset ownership review, validation email history, and configured rightsizing analysis
- temporary access requests with mappings, eligibility, duration, approval, and step-up checks
- custom graph adapters with non-persistent preview and governed mutation paths
One interface without one ambiguous status
Cases, jobs, alerts, findings, calendar occurrences, access requests, and app reconciliation each keep the state and controls their workflow needs. That lets an operator move between them without flattening different kinds of work into one vague ticket status.
The configured connections and target permissions define what GAEZLA can read or act on in each environment. Writes follow the execution or proposal controls for the workflow rather than inheriting authority from discovery alone.
Continue with the detailed guides: