AHENA

Solutions · Provider configuration

Configure external services through one control plane

Provider configuration management means treating the settings of the services your app depends on (webhooks, redirect URLs, domains, DNS records, buckets, environment variables) as declared, reviewed and verified configuration, not as clicks in a dozen dashboards.

Get started freePlan, apply and verify

Why dashboards don't scale

Each provider has its own dashboard, vocabulary and API. Doing it by hand means:

  • No single view of what a project needs from each provider, per environment.
  • Changes with no preview of their effect, cost or risk.
  • No proof that a change actually took effect: an accepted request isn't the same as the setting being there.
  • Setup that's hard to repeat for a new environment or a new project.

The lifecycle

  1. Declare
  2. Inspect
  3. Plan
  4. Approve
  5. Apply
  6. Verify

  1. Declare

    Capabilities and their providers live in ahena.config.ts, per environment, committed to git.

  2. Inspect

    Ahena reads each provider's current state through its management API (ahena inspect, ahena doctor).

  3. Plan

    ahena plan lists every change needed to match the declaration, across providers, each classified safe, needs confirmation, billable, destructive or manual.

  4. Approve

    Changes that aren't safe need a person; production, billable and destructive changes are approved in the signed-in dashboard. A plan bound to provider state that has since changed is refused.

  5. Apply

    ahena apply makes only the approved changes, idempotently, so a retry never duplicates anything.

  6. Verify

    Ahena reads the provider back and reports a change as verified only when it sees it. Steps only you can do are listed, never applied.

Good to know

  • Not every provider supports every change: each integration page lists what Ahena inspects, configures and verifies there, and what it refuses.
  • Some steps are manual by design (for example DNS at an unconnected registrar, or leaving an email provider's sandbox). Ahena lists them with the exact values.

Questions

What is provider configuration management?

It's managing the settings of the external services an app depends on (webhooks, auth redirect URLs, domains, DNS, storage buckets, environment variables and so on) as declared configuration that is planned, reviewed, applied and verified, rather than changed by hand in each provider's dashboard.