Self-hosted · Elastic License 2.0 · Early access
Your infrastructure, administered.
A platform that backs up, scans, cleans and watches your estate through pluggable kits. Runs on your own servers, free for good. The cloud adds one thing: seeing all of it from wherever you are.
One PostgreSQL, one compose file, no calls home.
What the name says
One name, six things the platform does through its kits.
AHEGAO — the Adminguide Helper that Enforces, Guards, Automates and Observes. The application work lives in the kits; the platform does these six things once, and the same way for every kit.
Your estate in one place: networks, hosts, storages, people, on-call.
Says what is wrong and what to do — and does the tedious part itself.
Rights, limits and the licence.
Secrets, isolation, refusals that reveal nothing.
Jobs, schedules, agents in segments you cannot reach.
Metrics, dashboards, export to Zabbix and Prometheus.
Kits
Kits
A kit is a separate service with its own schema and its own screen. The core contains no mention of any particular kit — you add one by adding a line to the compose file.
Logical backups that are proven by restoring them, not hoped for.
Finds what is on your network and draws the map.
Automates work with Sonatype Nexus OSS and watches it: image clean-up, compaction, metrics.
Mirrors of your repositories, archived into a storage.
Chores with a deadline and an owner; every kit's screen has a button to write one down.
Watches Proxmox clusters and nodes, and acts on what it sees.
MySQL and MariaDB on the same backup model as PostgreSQL.
Replica-set-aware dumps; point in time is a fact, not a flag.
Directories over SFTP or locally, verified by reading back.
Run a script over SSH and take the result home.
Runs playbooks on a schedule.
Free level
Free means free — within named limits.
The free level is the absence of a licence key — no registration, no internet, no calls home. It is the product, not a demo, and it has ceilings: they are numbers, they are listed below, and the software refuses at exactly those numbers.
See every limit ↓·How the free level is drawn →A second person at the screen is what a key is for. Agents, export tokens and kits are not people and are not counted.
Buckets are where home labs and small shops keep their copies, so the free level reaches them.
Each kit declares its free-level ceilings in its manifest. They are in the table below, as the code has them — not as a sales page has them.
The free level, in numbers
Every limit, before you install anything.
This table is generated from the code that enforces the limits — the core's table and each kit's manifest — and a build fails if it drifts. Paid levels exist in the design and not yet in the product; where a column says so, that is the whole truth.
| Self-hosted, free | Cloud, freeIn development | Paid levels | |
|---|---|---|---|
| Platformv0.4.0 | |||
| People at the screen | 1 | 1 | In development |
| Agents | One per kit | One per kit | In development |
| Maps | 1 | 1 | In development |
| Sites — locations inside one installation | Not capped | Not capped | In development |
| On-call rotas and escalation lines | — | — | In development |
| Storages, S3 buckets included | Included | Included | In development |
| Installations watched from one cabinet | Not applicable — nothing is connected anywhere | 1 | In development |
| PostgreSQL Kitv0.4.0 | |||
| Included | Backup, Verification by restoring | Backup, Verification by restoring | In development |
| Targets | Not capped | Not capped | In development |
| Network Map Kitv0.3.0 | |||
| Included | Export | Export | In development |
| Hosts | Not capped | Not capped | In development |
| Networks | Not capped | Not capped | In development |
| Schedules | 4 | 4 | In development |
| Scan tasks | 4 | 4 | In development |
| With a key | — | — | Scanning through agents · In development |
| Nexus OSS Kitv0.3.0 | |||
| Included | Clean-up, Schedules | Clean-up, Schedules | In development |
| Image copy tasks | 1 | 1 | In development |
| Rules | 1 | 1 | In development |
| Schedules | 2 | 2 | In development |
| Registries | 1 | 1 | In development |
| Git Kitv0.1.0 | |||
| Included | Mirrors, Sources, Schedules, Archiving into a storage | Mirrors, Sources, Schedules, Archiving into a storage | In development |
| Projects | 10 | 10 | In development |
| Sources | 1 | 1 | In development |
| Upkeep Kitv0.1.0 | |||
| Included | Chores | Chores | In development |
| Open chores | 20 | 20 | In development |
| Proxmox Kitv0.2.0 | |||
| Included | Monitoring, Control, Advice, History | Monitoring, Control, Advice, History | In development |
| Clusters | 1 | 1 | In development |
| Nodes | 2 | 2 | In development |
| Rules | 3 | 3 | In development |
| MySQL Kitv0.1.0In the tree — publishing one by one | |||
| Included | Backup, Verification by restoring | Backup, Verification by restoring | In development |
| Targets | Not capped | Not capped | In development |
| MongoDB Kitv0.1.0In the tree — publishing one by one | |||
| Included | Backup, Verification by restoring | Backup, Verification by restoring | In development |
| Targets | Not capped | Not capped | In development |
| File Backup Kitv0.1.0In the tree — publishing one by one | |||
| Included | Copying, Verification by restoring | Copying, Verification by restoring | In development |
| Sources | Not capped | Not capped | In development |
| Script Kitv0.1.0In the tree — publishing one by one | |||
| Included | Running scripts | Running scripts | In development |
| Hosts | 2 | 2 | In development |
| Ansible Kitv0.1.0In the tree — publishing one by one | |||
| Included | Playbook runs | Playbook runs | In development |
| Job templates | 1 | 1 | In development |
| With a key | — | — | Schedules, Inventory from the platform's resources · In development |
The cloud is in development, and its column is what the free level there will be: the same ceilings, one installation connected, kits free while they work through your agents. A kit that runs on our servers is a line in the daily rate.
“With a key” names what a kit refuses without one. The keys themselves are in development; the refusals are already in the code. How the free level is drawn →
Early access
See every installation from one place.
Connect your AHEGAO Kit installation to the cloud and watch it from home — or watch five customers' installations from one screen. Get a message in Telegram when a backup fails, open the phone, see what.
Names and states of your resources, the graphs your kits already collect, the outcome of jobs.
Your secrets, your copies, the contents of your databases, full error texts, a way into your network.
Where you choose to hand us more — our keys, our storage, our verification — we say what we get at every step. And it costs more, not less.
Pricing
No plans. Add what you need.
Self-hosted has a free level with the limits above, and keys for what lies beyond them. In the cloud you pay a daily rate for what you add — installations, people, agents, kit limits — and the balance runs down. Change anything, and the rate changes from that second.
1 installation · 1 person · cloud kits free through your agents
3 installations · 3 people · more agents
10 installations · a team · kit limits raised
Presets are just a filled-in configurator — change anything.
Early access: no card, stablecoins only, and prices can change with 30 days' notice. Offline keys for enterprise — closed networks with no way out — are a separate, yearly line.
Honesty is a feature.
This page loads nothing from third parties. The documentation neither.
Elastic License 2.0: read, change, run in production — for free and for good. Not OSI open source; three things are forbidden, and they are named.
A backup that was never restored is a hope. The kits verify by restoring, and a silent metric is a signal, not a blank.