- What is GAEZLA?
- GAEZLA is an operations platform for infrastructure teams. It provides investigation cases, managed execution, integration settings, alert routing, security workflows, compliance records, and temporary access controls in one operator interface.
- What does the name GAEZLA mean?
- GAEZLA comes from the Old Norse word gæzla: keeping, guardianship, or guard. The brand writes æ as ae and keeps the historic z. It fits an AI SRE built to keep watch over an estate, understand what changed, and help operators act with control.
- Who is it for?
- Small infrastructure teams responsible for infrastructure, endpoints, security, operations, and compliance records across a configured estate.
- What can the product actually do?
- Investigation cases, signed execution through agents and playbooks, queues, schedules and routines, configured integrations, an appliance app catalog, asset ownership review, rightsizing analysis, alert qualification and routing, vulnerability findings, hardening workflows, NIS2 and ISO 27001 workspaces, temporary access requests, and custom graph adapters.
- How is it different from a passive monitoring portal?
- A passive portal stops at status. GAEZLA also provides managed playbooks, queues, schedules, routines, and enrolled agents that return execution state and output. Investigation action proposals have their own evidence and approval controls.
- How does GAEZLA handle endpoint and execution trust?
- Dashboard access uses configured human identity and role checks. Each enrolled agent authenticates independently, polls for assigned work, verifies signed workloads, and returns status and logs. Investigation mutations use a separate proposal and approval path; managed schedules and routines follow their configured controls.
- Where do security and compliance fit?
- Vulnerability surfaces retain managed scanner assets, scan state, findings, and provenance. Supported hardening profiles provide checks, evidence, and remediation. NIS2 and ISO 27001 workspaces hold framework records, while calendar occurrences accept operator-attached evidence and artifacts.
- How does the appliance platform fit in?
- The appliance bootstrap installs the base local runtime and deployment controller. Optional apps can then be configured, installed, reconciled, exposed, and inspected through one visible lifecycle.