Raposa vs Temporal
Temporal can wait for a human as part of a durable workflow. Raposa is a focused approval layer with signed channels and a verifiable audit trail. They solve different halves of the problem.
The short version
Temporal is a durable execution engine. A workflow can pause and wait for an external signal — the common way to model a human task — and Temporal guarantees the run survives restarts and resumes exactly where it left off, keeping an event history of what happened. It is excellent infrastructure for long-running, reliable orchestration, and the human step is one pattern among many you build on top.
Raposa is not an orchestrator. It is a dedicated approval layer any workflow calls over HTTP — including from inside a Temporal activity. It provides the human-facing surface Temporal deliberately leaves to you: signed email, Telegram and Slack approvals, named groups with N-of-M sign-off, reminders and escalation, and a hash-chained, tamper-evident audit trail built for auditors rather than operators.
Side by side
Temporal details reflect its public documentation as of September 2026. Temporal is general orchestration infrastructure; "you build it" means the capability is left to the application, not that it is impossible.
| Dimension | Raposa Aval | Temporal |
|---|---|---|
| Category | Focused human approval layer (HTTP API) | Durable workflow / orchestration engine |
| HITL model | One call gates an action and routes it to a person | Workflow waits for an external signal you send |
| Durability of the wait | Managed pause with audited expiry | Durable execution; survives restarts, waits indefinitely |
| Approval channels | Signed email, Telegram, Slack — button decides | You build the UI and notifications |
| Named groups & N-of-M sign-off | Built in, every signer recorded | You build it |
| Audit trail verifiability | Hash-chained, signed, exportable, tamper-evident | Workflow event history — operational, not a signed compliance artifact |
| Reminders, escalation | Built in and audited | You build it with timers and signals |
| Deploy / payment / comms gating | Same one call for any high-stakes step | Any step you model in a workflow |
| Hosting & data location | EU only (Germany), DPA available | Self-hosted cluster, or Temporal Cloud region |
| Operational weight | A hosted API call | Run a cluster or adopt Temporal Cloud |
When to choose which
Choose Temporal when your real need is durable, long-running orchestration — multi-step processes that must survive failures and resume reliably — and a human wait is one node in a larger workflow you are already building. Temporal gives you guarantees a simple API call does not.
Choose Raposa when the problem is the approval itself: getting a decision from a real person through channels they use, with named groups, two-signature sign-off, and a verifiable audit trail hosted in the EU — without standing up orchestration infrastructure. The two combine well: a Temporal activity can call Raposa for the human decision.
Add a human decision to your workflow
Call Raposa from a Temporal activity — or any workflow — with one HTTP request. Start free: 100 approvals a month, full audit export, no card.