AXME
Moving from Temporal to AXME: what changes, what stays, and how to do it safely
A practical migration guide for teams moving from Temporal to AXME Cloud.
Teams leave Temporal when determinism blocks LLM workflows, human approval mid-flight needs a custom signal handler plus notification service plus UI, or worker operations slow iteration. Migration needs parallel running — not a big-bang rewrite.
MIGRATE
Temporal → AXME concept map
Concept mapping for migration planning.
| Capability | Temporal | 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.
You gain
LLM-friendly execution, eight native HITL types, no worker fleet, AXP multi-participant intents.
You give up
Mature workflow replay for strict non-LLM determinism — evaluate per workflow.
KEEP IN MIND
Plan for these differences.
HITL gap
Temporal: signal + token + UI per approval. AXME: wait_for_human with timeout and escalation built in.
Cluster ops
Temporal: self-hosted or cloud cluster. AXME: managed API, no determinism sandbox.
MIGRATION PATH
Recommended phases.
Parallel running before full cutover.
1. Map workflows
Workflow → Intent, Activity → Tool call.
2. Pilot one flow
New agents on AXME; Temporal unchanged.
3. Parallel run
Shadow intents; compare audit output.
4. Cutover
Route traffic; retire workers gradually.
5. Decommission
Archive Temporal namespaces.
Human approval mid-workflow
Temporal
# signal handler + task token # notification service + approval UI # ~200 lines per gate
AXME
await axme.wait_for_human( task="approval", assignee="cfo@co.com", timeout="48h", escalate_to=backup )
Migration FAQ
- Can I call OpenAI inside AXME?
- Yes — AXME tracks state at the intent level, not deterministic replay of workflow code.
- Do I need workers?
- No separate worker fleet — AXME Cloud runs intent lifecycle.
- What about Temporal's HITL patterns?
- See /blog/what-temporal-cant-do/ — AXME ships approval types without per-workflow UI glue.
- How long does migration take?
- Pilot flows often ship in 1–2 weeks; full cutover depends on workflow count.
Related resources
Ship your first durable agent — in under 10 minutes.
Free tier. No credit card. Self-host or hosted — your choice.