AHEGAO Kit¶
Adminguide Helper: Enforce, Guard, Automate, Observe Kit — a self-hosted infrastructure administration platform to which kits attach.
The platform itself does nothing application-specific. It provides what every kit needs in the same way, and does it once: users and rights, licences and limits, a job queue and schedules, a registry of resources with owners and on-call people, monitoring, alerts, storages with retention, encrypted secrets, and export to outside systems. The application work lives in kits. The name is a list of what the platform does on behalf of all kits at once: enforce — rights, limits and the licence; guard — secrets, organisation isolation and refusals that do not reveal existence; automate — jobs and schedules; observe — metrics, dashboards and export.
A kit is a separate service with its own schema in the shared PostgreSQL and
its own ui.js. The core contains no mention of any particular kit: the
list of kits is deployment configuration, not code. A kit is added by adding a
service to the compose file and its name to AG_MODULES. Kits are published
one at a time as each is finished, so this repository carries the ones that
are ready rather than all of them at once; the table below is what this
release ships.
It is built for self-hosting inside an internal network: Docker Compose on a VM or in an LXC container, one PostgreSQL, one schema per service. The free level is the absence of a licence key — no internet, no registration, no calls home — and its limits are chosen so that a single administrator of their own infrastructure has enough. The platform is not a general-purpose monitoring system (it monitors itself and what its kits are responsible for, and exports to Zabbix or Prometheus rather than replacing them), not an orchestrator (it does not manage containers or deploy software), and not a CMDB in the full sense.
The source is open and the licence is Elastic License 2.0 — read, change, build and run it in your own infrastructure, including production, for free and for good. It is not open source by the OSI definition: three things are forbidden (offering it to third parties as a service, circumventing the licence-key check, removing the copyright notices), and the free level has limits that a key raises. Details are on the Licence page.
State¶
The table below is the state of each part at this release — the same table
as in the repository's README.md.
| Part | State |
|---|---|
| Core: skeleton, organisations, rights, licences | works |
| Core: jobs and schedules | works |
| Core: resources, metadata, teams | works: the network a host was found in, and a pile edited at once |
| Core: on-call — rotations, overrides, "who is on call" | works |
Core: monitoring — metrics, history, /metrics, JSON |
works |
| Core: alerts — facts, thresholds, channels, templates | works |
| Core: storages, copies, grandfather-father-son rotation | works: local path, NFS/SMB, S3 |
| Core: secrets — encryption, hand-out, rotation | works |
Core: export to outside systems (/export/v1) |
works |
| Shell: menu on the left, kit sections | works |
Network Map Kit (net) |
works, the map is in place |
PostgreSQL Kit (postgresql) |
works: backup, encryption, restore with verification |
Nexus OSS Kit (nexus) |
works: plan, clean-up, compaction, list of what was removed |
Where to go next¶
- Quickstart (self-hosted) — from nothing to the first login.
- Configuration — every
.envvariable, and what happens if you loseAG_SECRET_KEY. - Kits — what each kit does, what it needs, what it measures, and what it refuses to do.
- Security and known limits — the honest list.