Guides
How Ahena works, and why
Longer explanations of the ideas behind Ahena: where it sits, how it proves a change happened, and how it keeps people in charge of the changes that matter. Each one links to the reference documentation.
- Architecture
Control plane vs runtime proxy: why Ahena stays out of your request path
Why Ahena configures your providers from beside your app instead of proxying its traffic, and what keeps running when Ahena is unavailable.
- Reliability
Why a 2xx response isn't verification
An accepted API call isn't proof the change exists. How Ahena reads providers back, tells VERIFIED from APPLIED_UNVERIFIED, and retries safely.
- Operations
Detecting configuration drift: lock, diff and drift
How ahena.lock records what your stack is, how ahena drift finds changes made in provider dashboards, and what Continuous Doctor monitors.
- AI agents
Giving AI agents infrastructure access safely
How Ahena's MCP server lets coding agents inspect and plan infrastructure changes, why approvals happen in your browser, and where the limits are.
- Providers
Switching providers is a migration, not a config edit
Why changing the provider behind a capability means moving data and code, and exactly what ahena switch changes, checks and leaves for you.
- Change management
Plan, approve, apply, verify: how Ahena changes your providers
The change lifecycle in Ahena: plans per environment, the SAFE to MANUAL classifications, who approves what in production, and how applies are checked.
Looking for a specific command or setting?
The documentation covers every CLI command, provider and configuration key.