# What Automedha runs today

By Automedha on 2026-08-31.

© 2026 Automedha. All rights reserved.

Automedha’s private beta runs workflow templates on a durable execution plane. Teams provision a template, connect a payment mandate, start a run, and inspect its status and usage.

## Templates are declared workflows

The catalog declares eleven workflow templates. Nine run today; the cold-outreach and newsletter templates are gated behind a delivery policy. A template declares its steps, allowed capabilities, terminal states, and spending boundary before it can run.

Two templates have completed the live proof path. `eval-gate` exercised the full self-serve loop without paid capability usage. `research-to-microsite` completed the same loop with a paid search capability and a recorded usage change.

## Durable execution owns the run

The durable execution layer is the production run authority. It persists workflow state around waits, signals, schedules, approvals, deadlines, and retries. A process restart does not turn an in-flight run into an untracked background task.

## Capabilities are scoped before dispatch

A workflow receives only the capability operations declared for its template. The runtime routes connector calls through a policy boundary and records the terminal reason for each run.

Paid operations use a quote-before-dispatch path. The connected payment mandate defines the available authority, while platform and operation caps constrain what the workflow can request. Usage records preserve the operation outcome and attributed amount for later inspection.

## The self-serve loop works end to end

The verified operating loop is:

1. Choose a template.
2. Provision an isolated deployment for the organization.
3. Connect a payment mandate.
4. Start the workflow.
5. Inspect run status, terminal reason, and attributed usage.

The operator plane can inspect deployments, pause the fleet or an organization, recover queued work, and inspect audit records.

## What comes next

The [roadmap](/roadmap/) lists the upcoming work.

In private beta, you start with a workflow template and a funded, budgeted deployment you can inspect from day one. Request early access.