Workflows on n8n that you host and own

The self-hosted version is free to run for your own business under n8n’s Sustainable Use Licence. You pay for the server and for our time. n8n’s cloud plans charge by workflow run, and a run counts once however many steps it has.

If the flows touch customer or financial data, usually yes. Your logins and run history stay on a server in your name, and there is no per-run charge. The catch is that someone must update and back it up, which a care plan covers. If you want nothing to look after, n8n’s cloud is a fair choice and we’ll build on that.

Zapier is the quickest for a simple link between two popular apps. Make suits visual builders. n8n suits flows with branches, code and your own data rules, and it can run on your server. Zapier counts each action as a task and Make spends credits on each action. n8n counts a whole run once.

Yes. n8n has built-in nodes for hundreds of apps, including Zoho CRM, Xero and Google Sheets, and an HTTP node for anything with an API. Each connection is listed in the scope, with what the flow may read and what it may write.

Builds start from $5,000. The price moves with the number of systems linked and the state of your data. You get a written scope and one price before anything is built. See how we price a job. The server is billed to you directly.

It can be, if it is set up for it. n8n stores logins encrypted, and we put the server behind HTTPS and a sign-in. We write down where each piece of data goes before we build. n8n publishes its own security guidance for self-hosting.

Each flow has an error route. A short fault is retried first. If that fails, the item that failed is held and a person is alerted, so nothing is lost quietly. Under a care plan we get the alert too and fix it. Without one, the runbook tells your team what to do.

Yes, if we can open them. We read each flow and check its logins, error handling and run history. Then we tell you in writing whether to repair it or rebuild it, with a price for either, before we change anything.

You do. The server and the accounts are in your name, and you receive the flows as exported files with the runbook. Access to your systems is agreed for each project. If you stop working with us, nothing stops running.

Start with an automation audit if you have a list of jobs and no order. It ranks them by effort and payoff and costs each one. If you already know the one job, skip the audit and ask for a build.