Is AXME available outside AWS?

Yes — deploy AXME Cloud in the cloud you choose; agents call the same SDK.

What about payload limits?

AXME uses reference payloads for large model outputs — no 256KB state object cap.

Can Lambda still run steps?

Yes. Tools and agents invoke Lambdas; AXME owns durable waits and HITL between steps.

See /migrate/from-step-functions/ for ASL → intent mapping and phased cutover.

COMPARE

Step Functions keeps you in AWS. AXME works everywhere.

SDK-first intents vs JSON ASL — payload limits, portability, and native human gates for agents.

Compare AXME Cloud and AWS Step Functions.

Start free Read docs

Comparisons on this page describe typical product capabilities and common deployment patterns. They are not legal advice or guarantees of fitness for your environment. Validate claims with your security, compliance, and legal teams before production decisions.

AWS Step Functions is the default choice inside AWS for state machines. AXME is for teams that need SDK-first authoring, larger payloads, cloud portability, and agent-native human gates — without JSON ASL.

When AWS Step Functions is the right choice

Stay on Step Functions when workflows are already encoded in ASL, tightly coupled to AWS services (Lambda, SNS, DynamoDB), and your organization standardizes on AWS-only deployment with existing runbooks.

When AXME is the right choice

Choose AXME for cloud-agnostic agent workflows, Python/TypeScript SDKs, payloads above 256KB, native HITL, and the same intent model across AWS, GCP, Azure, or on-prem agents.

Compare authoring ergonomics, payload limits, portability, and agent fit — not just state machine features. Step Functions task tokens for humans are flexible but verbose; AXME models humans as first-class intent waits.

COMPARE

AXME vs AWS Step Functions

Feature-by-feature for architecture and procurement reviews.

Capability	AWS Step Functions	AXME
Authoring experience How engineers define workflows.	JSON Amazon States Language (ASL) in console or IaC	✓Python / TypeScript SDK — code-first intents
Payload limits Large documents, model outputs, attachments.	256KB per state — workarounds via S3 pointers	✓Reference payloads — no 256KB state cap
Portability Multi-cloud and on-prem agents.	AWS regions and accounts — vendor-bound	✓Cloud-agnostic AXME Cloud deployment
Human-in-the-loop Approval tasks in agent workflows.	Task tokens and callback URLs — more wiring	✓Native wait_for_human patterns
AI agent fit LLM steps, tool use, multi-agent handoff.	Generic state machine — agent semantics are DIY	✓Intent model built for agent-era workflows
Observability & audit Cross-service forensics.	CloudWatch + execution history — AWS-scoped	✓Intent audit + Mesh fleet view

KEY DIFFERENCES

What changes in practice.

The items evaluation committees ask about first.

JSON ASL vs AXME SDK

Step Functions

{
  "StartAt": "Approve",
  "States": {
    "Approve": {
      "Type": "Task",
      "Resource": "arn:aws:states:::lambda:invoke.waitForTaskToken",
      ...
    }
  }
}

AXME

intent = await axme.submit(approval_flow)
await intent.wait_for_human(
  task="manager_signoff", assignee=manager_arn
)
await intent.complete()

Escape vendor lock-in

Step Functions ties orchestration to AWS regions and ASL. AXME runs wherever your agents and services deploy — one intent model for hybrid and multi-cloud.

MIGRATION

A phased path off AWS Step Functions

Parallel running before you retire the old system.

1. Inventory

List state machines with human tasks and payload-heavy steps.

2. New on AXME

Route net-new agent workflows to intents first.

3. Strangler

Replace high-churn flows; keep stable ASL machines temporarily.

4. Retire ASL

Decommission migrated machines after audit parity.

Learn more →

AWS Step Functions vs AXME — common questions

Is AXME available outside AWS?: Yes — deploy AXME Cloud in the cloud you choose; agents call the same SDK.
What about payload limits?: AXME uses reference payloads for large model outputs — no 256KB state object cap.
Can Lambda still run steps?: Yes. Tools and agents invoke Lambdas; AXME owns durable waits and HITL between steps.
How do we migrate?: See /migrate/from-step-functions/ for ASL → intent mapping and phased cutover.

Related capabilities

Migrate from Step Functions

Phased guide.

Human-in-the-loop

Approval patterns.

Durable execution

Intent lifecycle.

Cross-service orchestration

Use case.

Next steps

Migrate from Step Functions Durable execution Human-in-the-loop Pricing

Ship your first durable agent — in under 10 minutes.

Free tier. No credit card. Self-host or hosted — your choice.

Start free now Read the docs