Up to 70% off kits30% off services
n8n Production Readiness Check
Fifteen yes-or-no questions about the n8n your business depends on: error alerts, hosting and backups, credentials and access, workflow design, and who owns it all. Five minutes, a score, and a fix for every gap. Works for n8n Cloud and self-hosted. Answers stay in your browser.
1.Errors & alerts
2.Hosting & backups
3.Credentials & access
4.Workflow design
5.Ownership & cost
Want someone to check the real instance?30% OFF
Our $349$499 n8n Workflow Audit reviews every active workflow, its errors and credentials, and the server it runs on, and gives you a written fix plan in about 5 business days, credited toward the hardening or build.
Why n8n works in testing and breaks in production
Most n8n trouble isn't a bad workflow. It's a good workflow with nothing around it: no alert when it fails, no backup when the server goes, and no owner when the builder leaves. Five habits cover most of it.
- Make failures loud. One shared error workflow, set on every production workflow, that posts the workflow, the failed step and a link to the run. Add a check that fails runs which processed nothing.
- Back up the key with the database. n8n encrypts credentials with its encryption key. A database backup without the key means reconnecting every credential by hand.
- Assume every run can happen twice. Webhooks are re-sent and people re-run executions. Look records up by a unique ID before creating them.
- Give credentials to the company. Service accounts survive people leaving. Personal logins don't.
- Know your volume. A schedule every minute is about 43,200 executions a month. Price your real workload with our n8n pricing calculator, and see the n8n pricing guide for what self-hosting really costs.
Frequently asked questions
What it covers, Cloud vs self-hosted, scoring and what to do next.
That the business can depend on it without someone watching. Failed runs alert a person, the database and encryption key are backed up and restorable, credentials belong to the company rather than to one person, workflows cannot create duplicates when they run twice, and someone owns updates and knows what every active workflow does.
Mostly, yes. Error workflows, canaries, credentials, webhook checks, duplicate protection and ownership matter on any n8n. n8n runs the server, database and updates for you on Cloud, so for the hosting questions answer about what you control: exports of your workflows and a copy of anything you would need to rebuild.
Each question has a weight: 3 for gaps that lose data, orders or money, 2 for gaps that cause recurring failures nobody sees, 1 for gaps that slow you down. A Yes earns the full weight; Not sure and No earn nothing. Not sure counts against you on purpose: if nobody knows, nobody is checking.
No. The check runs in your browser. Answers are not stored or sent anywhere, so copy or download your results before closing the tab.
Start with the Critical items: error alerts, backups with the encryption key, and duplicate protection. Each result says what to do. If you would rather have someone check the real instance, our $499 n8n Workflow Audit reviews every active workflow, its credentials and the server it runs on, and gives you a written fix plan, credited toward any hardening or build.