QUORUMRequest hosted pilot
For n8n agencies and operations teams

Catch n8n workflows
that fail quietly.

Quorum helps you catch broken business automations before clients or stakeholders do—so you can protect operations, trust, and recurring revenue.

View on GitHub
Open sourceSelf-hostedNo telemetry
quorum.local / workflows● Live

Healthy → incident → recovered Real workflow state sequence

01 / THE BLIND SPOT

The execution list cannot show a run that never started.

In-workflow error handling only sees executions that exist. It cannot detect a missed schedule, a deactivated workflow, or an unavailable instance that never created a run.

Inside the workflow
  • Execution errors
  • Failed nodes
  • Thrown exceptions
Only sees runs that exist
Outside the workflow
  • Missing runs MONITORED
  • Silent absence MONITORED
  • Green but empty MONITORED
  • Recovery status MONITORED
Quorum observes the expected behavior
02 / DETECTION

See the failure modes
the workflow cannot.

Focused reliability signals for the gaps between execution status and expected behavior.

01

Missing runs

Detect workflows that never started when expected.

15:00No execution received
02

Green but empty

Flag successful executions that report zero or out-of-range output volume.

200 OK0 reported outputs
03

Stateful incidents

Open one incident, preserve the history, and resolve it when the workflow recovers.

#0148Recovered · 16 min

Product boundaryHeartbeat and volume evidence can be self-reported. They do not independently prove downstream delivery.

03 / BUSINESS VALUE

Reliability your clients
can actually feel.

Quorum turns a technical monitoring gap into an operating advantage for teams responsible for business-critical automation.

01

Protect the relationship

Find silent automation failures before a client or internal stakeholder reports the damage.

02

Defend recurring revenue

Bring monitoring evidence to reviews and show that maintenance is proactive, not reactive.

03

Reduce expensive checking

Give the team one incident history instead of repeatedly inspecting execution lists by hand.

The commercial case is simple: detect earlier, respond with evidence, and make reliability part of the service you sell—not a promise you hope to keep.

04 / HOW IT WORKS

External by design.

Quorum sits outside the execution path. Your workflows report evidence; Quorum evaluates whether reality matches expectation.

01

Connect

Register an n8n workflow using polling or push heartbeats.

POST /heartbeat
02

Define

Set the expected schedule and acceptable outcome.

every 15 min
03

Monitor

Quorum watches from outside, opens incidents, and resolves them on recovery.

state: recovered
04 / PRODUCT PROOF

One workflow. One incident.
Full recovery history.

QuorumProduction
WORKFLOWS / LEAD ROUTING

Lead routing

Every 15 minutes · polling

Recovered
✓Healthy09:00
×Missed execution09:15
!Incident open09:17
✓Recovered09:31
INCIDENT #0148

Expected execution window passed without a reported run.

recovered_by: execution_8f2a
HealthyMissed executionIncident openRecovered
05 / OPEN SOURCE

Built to run in
your environment.

Self-host Quorum with Docker, keep your workflow data under your control, and run without telemetry.

Explore the repository
quorum / deploy
$ docker compose up -d

✓ Network quorum_default created
✓ Container quorum started

quorum  ready on :3000
  • Docker-based
  • SQLite-backed
  • Self-hosted
  • No telemetry
LIMITED DESIGN-PARTNER PILOT

Make reliability part of your offer.

For n8n agencies and operations teams responsible for critical automations. Get direct onboarding, help defining monitoring expectations, and a close feedback loop while Quorum is in beta.

Apply for the hosted pilot Limited availability · Direct onboarding · Beta product

Know when the workflow
stops doing its job.

View on GitHub Request hosted pilot