Temporal is the gold standard for durable workflow execution. AEROSS ships the same crash-safe kernel — plus Run Inspector, the governance policies enforcement, approval chains, a lineage mesh, and a live strategy graph.
No. AEROSS runs its own checkpointed execution kernel — a compiled KernelGraph interpreter with frontier-based execution using FOR UPDATE SKIP LOCKED. The durability model is architecturally similar to Temporal's approach but independently implemented, with governance policies, approval chains, and lineage mesh built into the kernel layer.
If you need durable workflow execution and nothing else, Temporal is proven. If you need durable execution plus a governance layer, human-in-the-loop approval chains, end-to-end lineage, a strategy graph, and a UI that operators can actually use — AEROSS ships all of that as one runtime.
No. Temporal workflows are written in code using Go, Java, Python, or TypeScript SDKs. AEROSS workflows can be built via the no-code Workflow Agent or via the adapter and template library — no SDK required. Developer access is available for custom integrations.
Both resume from the last checkpoint. AEROSS additionally routes failures to the decision queue inbox via escalate_failed_frontier, surfaces them in Run Inspector, and makes them actionable via operator controls — cancel, retry, skip, force-complete — with full audit receipt on every intervention.
AEROSS is a complete runtime and does not require Temporal. Teams migrating from Temporal to AEROSS gain the full governance, observability, and strategy layers without needing to maintain a separate durable execution infrastructure.