Stack Graph
Every capability your app uses, the provider behind it, its resources and health, per environment. The CLI, the dashboard and AI agents all read the same graph.
The control plane for your application stack
Ahena connects, configures, verifies and diagnoses the services your application depends on, from authentication and payments to email, storage, DNS and AI. One control plane for development, staging, production and your AI coding agents.
Your application talks directly to your providers. Ahena manages the stack, not your traffic.
$ ahena doctor -e production
AHENA DOCTOR Leo · Production
✕ Production CORS allows every origin (*)
→ Run ahena configure cloudflare with your exact origins.
✕ leo.app isn't added to Resend
→ Run ahena configure resend to add it.
RESULT 12 Passed 0 Warnings 2 Failed
$ ahena apply -e production
AHENA PLAN pln_7q2m · Production (production)
~ Configure CORS on leo: https://leo.app [CONFIRMATION_REQUIRED]
+ Add sending domain leo.app to Resend [CONFIRMATION_REQUIRED]
? Apply this plan to Production? Yes
APPLIED pln_7q2m
✓ Cloudflare: Configure CORS on leo (verified)
✓ Resend: Add sending domain leo.app to Resend (verified)Example session. The CLI is in beta: npm install -g @ahena/cli. Early access starts with development and staging environments; production opens later.
Before and after
Connect your provider accounts once. Then:
$ ahena init --recipe saas$ ahena add auth$ ahena add storage$ ahena add email$ ahena add payments$ ahena add ai$ ahena plan -e production$ ahena apply -e production$ ahena doctor -e production
ahena add declares a capability, connects its provider if needed and plans the changes. Production waits for approval.
Connections
Ahena talks to each provider's management API with credentials you connect. Your app keeps talking to them directly.
A few of the providers
Hover, focus or tap any provider to see what Ahena sets up and checks there. Ahena changes a provider only through an approved plan, then reads it back to confirm.
Every integration: what Ahena configures, checks and verifies, and how far each is verified →
Ahena Doctor
Doctor checks the live providers in an environment against what your app declares, and explains every finding. Run it from the CLI, the dashboard, or CI with ahena deploy-check to stop a deploy when production is misconfigured.
$ ahena doctor -e productionAHENA DOCTOR Leo · Production · health 86%✓ Site URL configured✓ Stripe live mode✓ leo.app verified (Resend)✓ Configured redirect URLs present⚠ localhost present in production redirect URLsWhere: Supabase · Production · urls: http://localhost:3000/auth/callbackAhena can fix it: Yes, after you approve a change that can't be undone→ Remove them with ahena configure supabase --remove-redirect <url>.RESULT 14 Passed 1 Warning 0 Failed
What Ahena does
Every capability your app uses, the provider behind it, its resources and health, per environment. The CLI, the dashboard and AI agents all read the same graph.
Checks live providers, configuration and your repository, then explains each finding: why it matters, where, the impact and the fix.
Every change is planned before it happens. Billable, destructive and production changes need their own approval.
After applying, Ahena reads the provider back. A change is done only when the provider shows it. Unknown outcomes are reported, never guessed.
Readable TypeScript in src/ahena/ that calls each provider with its official SDK. It's yours to keep, with no runtime dependency on Ahena.
ahena.lock records the provider state you approved. ahena drift compares it with the live providers and shows what changed outside Ahena, without overwriting it unless you approve.
Claude Code, Codex and other MCP clients can inspect the stack, run Doctor and plan changes. Anything that isn't marked safe waits for you.
Organizations with owner, admin, developer and viewer roles. Every change is recorded in an append-only, hash-chained audit log.
See Ahena build a stack
Real commands and real output formats from the Ahena CLI, on the sample project Leo.
Link the accounts you already use (Supabase, Neon, Vercel, GitHub, Stripe, Resend, Postmark, AWS S3 and SES, OpenAI and 10 more) to each environment. Credentials are encrypted and bound to the environment they belong to, and Doctor flags test keys in production or a production secret reused anywhere else.
ahena connect stripe -e production
development
staging
production
ahena.config.ts lives in your repository and is safe to commit: Ahena refuses to load it if a value looks like a credential. Any value can differ per environment.
Or start from intent: ahena add payments works out what payments mean for your kind of app and declares it for you.
// Ahena's configuration for this app: https://ahena.io/docs/configuration
export default {
organization: "leo",
project: "leo",
auth: { provider: "supabase", siteUrl: { production: "https://leo.app" } },
storage: {
provider: "cloudflare",
bucket: { development: "leo-dev", staging: "leo-staging", production: "leo" },
corsOrigins: { staging: ["https://staging.leo.app"], production: ["https://leo.app"] },
},
email: { provider: "resend", domain: { production: "leo.app" } },
ai: { provider: { development: "ollama", production: "anthropic" } },
};A plan covers one environment and every provider in it, with each change classified: safe, needs confirmation, manual, billable or destructive.
Approving a production plan takes an admin. Anything billable or destructive is approved separately, and declining it leaves it untouched.
$ ahena plan -e stagingAHENA PLAN pln_3fx9 · Staging (staging)Match ahena.config.tsCloudflare+ Create R2 bucket leo-staging [BILLABLE]~ Configure CORS on leo-staging: https://staging.leo.app [CONFIRMATION_REQUIRED]Stripe+ Create product Pro (test mode) [CONFIRMATION_REQUIRED]No destructive changes.Includes changes your provider may bill for. They need their own approval.
Ahena applies the plan provider by provider, then reads each one back. ✓ means it saw the change there, not just that the API said OK.
If a step fails, what succeeded stays in place and the plan says exactly what happened. If Ahena can't tell, it says the outcome is unknown and where to look.
$ ahena apply pln_3fx9? 1 change may cost money or can't be undone. Include it? Yes? Apply this plan to Staging? YesAPPLIED pln_3fx9✓ Cloudflare: Create R2 bucket leo-staging (verified)✓ Cloudflare: Configure CORS on leo-staging (verified)✓ Stripe: Create product Pro (test mode) (verified)Next: ahena generate, then ahena doctor
AI agents
ahena mcp gives Claude Code, Codex and other MCP clients the Stack Graph, Doctor and plans, as you, under your role. It's read-only unless you start it with --allow-write.
The MCP server runs on its own agent session, which Ahena's API refuses for approvals and secrets, so this holds even if the agent has a shell.
Ahena for AI coding agents → Giving AI agents infrastructure access safely →
Adding subscriptions to Leo.
ahena · add_capability paymentsDeclared payments in ahena.config.ts. Stored plan pln_9c1e for Production.
Apply 3 changes to Production?
+ Create product Pro · + Create price pro_monthly · + Create webhook
ApproveDecline✓ Applied and verified in Stripe. Recorded in the audit log.
No runtime lock-in
Ahena configures and checks your providers from the side. It never sits between your application and them.
ahena generate writes TypeScript into src/ahena/ that calls each provider with its own SDK. It imports nothing from Ahena, and it's yours to edit.
If Ahena is unavailable, a correctly configured app keeps working. Planning, applying and Doctor need Ahena; serving your users doesn't.
You connect provider accounts you own and pay them directly. Ahena never marks up usage, and disconnecting never deletes anything at the provider.
Why Ahena stays out of your runtime path → How Ahena handles security →
Who it's for
What's ready
We only put on this page what Ahena does today, and say plainly what isn't finished.
Start free with one project. Paid plans from $19 a month add projects, teammates and actions.