Documentation menu

Documentation

Ahena is the control plane for the services your application depends on. You connect the provider accounts your app already uses (Supabase, Cloudflare, Resend, Stripe, Firebase, OpenAI, Anthropic, Ollama), per environment. Ahena then:

  • understands the app's stack: which provider fills each capability in each environment (Stack Graph);
  • plans provider configuration from what the app declares in ahena.config.ts;
  • applies the changes you approve and verifies them by reading the provider back (plans, approvals);
  • diagnoses problems (Doctor) and detects changes made outside Ahena (drift);
  • generates readable integration code that calls providers directly with their official SDKs (generated code);
  • keeps development, staging and production separate, and protects production more (environments);
  • gives AI coding agents scoped, approval-gated access to all of the above (MCP);
  • records every change in a tamper-evident audit log (security).
DECLARE → CONNECT → PLAN → APPROVE → APPLY → VERIFY → MONITOR → REPAIR

The runtime boundary

Ahena calls providers' management APIs: create a webhook, set CORS on a bucket, verify an email domain, read the current configuration. Your application's own traffic (sign-ins, queries, emails, payments, uploads, AI requests) goes straight from your app to the provider. If Ahena is unavailable, a correctly configured app keeps working. See Control plane, not a runtime proxy.

What Ahena isn't

  • Not a proxy or API gateway. Application traffic never passes through Ahena.
  • Not a general-purpose secrets vault. Ahena securely keeps the credentials your stack needs: the provider credentials it manages providers with, plus application secrets it creates (webhook signing secrets) or that you keep with an environment. Your application never fetches secrets from Ahena; today you set runtime values on your host yourself.
  • Not a host, a runtime or a reseller. You keep your own provider accounts and pay providers directly.

Ways to use it

Surface Status What it's for
Dashboard (app.ahena.io) Available Organizations, projects, environments, connections, Doctor, the Stack Graph, plans, approvals, activity
CLI (ahena) Beta: npm install -g @ahena/cli Everything above from a repository, plus ahena.config.ts, plan and apply, generated code, drift, CI checks
MCP server (ahena mcp) Beta (part of the CLI) Lets AI coding agents inspect the stack, run Doctor and propose changes you approve

See Installation, then the Quick start.

Status labels

Pages say Planned for things that are designed but not built yet. Anything not labelled is in the product today. Ahena never documents a capability before it exists.

Browse the documentation