Fair-code
Self-hosted
Keep the service, dashboard, and execution data in your own environment.
- All five detectors
- No hosted account
- You control deployment and updates
pisama for n8n
Your n8n workflows fail quietly.
This catches them.
Pisama reads real workflow executions and surfaces the failures that slip through: timeouts, swallowed errors, runaway loops, and exploding payloads. Connect your n8n and see the evidence behind each detection.
Choose your setup
Start where the workflow lives
Run Pisama yourself, start with hosted detection at no cost, or give your team AI-assisted fixes when a detection needs action.
Change plans when the work changes
Cloud
Free
Get hosted detection and a dashboard for one connected n8n instance.
- One n8n connection
- All five detectors
- Detection stays free
Pro cloud
Fix and approve
Give a team room to connect more workflows, generate fixes, and apply approved changes with a rollback point.
- Five n8n connections
- Monthly AI fix allocation
- Apply and roll back approved fixes
| Includes | Self-host | Free cloud | Pro cloud |
|---|---|---|---|
| Deployment | Self-hosted | Pisama cloud | Pisama cloud |
| n8n connections | You manage them | 1 | 5 |
| Failure detection | All five detectors | All five detectors | All five detectors |
| AI fix suggestions | With a cloud key | Not included | Monthly allocation |
| Apply approved fixes | With a cloud key | Not included | Snapshots and rollback |
Five detectors, two lanes
Structural analysis of the workflow, runtime analysis of the execution
The structural lane reads the workflow graph itself, with precision tuned against thousands of real community workflows. The runtime lane reads what actually happened in an execution: real timings, real errors, real payload sizes, validated on a smaller corpus of real executions.
Timeout
A node genuinely ran past its threshold in a real execution, likely timing out the caller.
Node error
A node threw during the run, including failures hidden by continue-on-fail settings.
Resource explosion
Output payloads or item counts ballooned mid-run, the pattern behind memory and quota blowups.
Unbounded cycle
A workflow graph cycle with no exit and no iteration bound. Intentional batch loops are recognized and left alone.
Excess complexity
Control flow tangled enough to be a reliability risk, calibrated on thousands of real community workflows.
Three ways in
Works with n8n Cloud and self-hosted, no workflow rewrites
Community node or webhook
Install the n8n-nodes-pisama node, or point any HTTP node or error workflow at the ingest endpoint.
API polling, zero setup
Give the server your n8n API key and it polls recent executions on its own. No workflow edits at all.
Self-host in one command
docker compose up starts the detection server and this dashboard on your own machine.