AXME
Move off AWS Step Functions: no 256KB limit, no JSON ASL, no AWS lock-in
Step-by-step guide to migrating from AWS Step Functions to AXME Cloud.
Step Functions users hit ASL verbosity, 256KB payload limits, AWS-only deployment, and human approval that needs task tokens, callback URLs, and a custom UI per gate. AXME offers SDK-first, cloud-agnostic intents with native HITL.
MIGRATE
Step Functions → AXME concept map
Concept mapping for migration planning.
| Capability | Step Functions | AXME |
|---|---|---|
Durable execution Resume after crash or deploy. | Build your own | ✓Native intent lifecycle |
Native HITL Human approvals without glue. | Custom per gate | ✓8 task types built in |
Fleet governance Observe and stop agents. | Cobble observability | ✓Mesh control plane |
Open protocol No vendor lock-in. | Varies | ✓AXP open source |
LLM-friendly Non-deterministic code OK. | Often blocked | ✓Yes |
Time to production Prototype to durable ship. | Months | ✓Days |
TRADE-OFFS
What you gain — and what you give up.
Honest evaluation before cutover.
State Machine
→ Intent with lifecycle stages.
Task state
→ Tool call / agent step.
Choice/Parallel
→ Intent branches + multi-agent.
MIGRATION PATH
Recommended phases.
Parallel running before full cutover.
1. Inventory
List state machines and HITL gaps.
2. New on AXME
Route net-new workflows to AXME.
3. Strangler
Replace high-churn flows first.
4. Retire ASL
Decommission migrated machines.
ASL JSON vs AXME Python
Step Functions
{"StartAt":"Approve","States":{...}}AXME
await axme.wait_for_human(task="approve")
Migration FAQ
- Is AXME available outside AWS?
- Yes — deploy AXME Cloud in your cloud of choice.
- Payload limits?
- No 256KB cap — store large payloads via references.
Related resources
Ship your first durable agent — in under 10 minutes.
Free tier. No credit card. Self-host or hosted — your choice.