Developer Preview · macOS
See what's actually straining your Mac: process pressure, wakeups, memory, energy, and per-agent impact. Manage it from a native app, a CLI, or an AI agent over MCP. Nothing leaves your machine unless you export it.
Three reasons to use Aetower
A flat wall of processes with no story. Aetower groups by entity and ranks everything with a single friction score, so the thing straining your Mac is at the top, not buried on page three.
Per-agent run timelines, CPU and memory impact, and budgets, so you know at a glance whether the coding agent in the background is costing you a fan spin or a flat battery.
The same friction, wakeup, and signing data is reachable from a native macOS app, a CLI, and a local MCP server. Read it and act on it by hand, in a script, or by pointing an AI agent at it.
What it inspects
CPU, threads, friction.
Battery, cost, carbon.
Footprint & leaks.
Unsigned / ad-hoc.
Agents, daemons, cron.
Timelines & MCP.
By default
Runtime history and diagnostics stay on your Mac unless you explicitly export them.
Endpoint Security, telemetry, and automatic MCP registration are all off until you opt in.
The PKG is the supported path; DMG, Homebrew, ZIP, and source are there if you prefer them.