Hosting n8n. Twoja instancja, Twoje workflow.

1. n8n works differently from a typical website, and that changes your hosting choice

n8n is a workflow automation platform that connects different services and APIs without code. In the vendor's cloud, you pay based on the number of workflow executions each month. With extensive automation involving many steps and triggers, the subscription cost can quickly add up.

On Saplo, n8n is set up as a ready-to-use Docker application (the official n8nio/n8n image) with one-click installation, its own authentication active from the first sign-in, and no workflow execution counter. You pay for the Box, not for the number of times your automation runs.

The app manifest requires at least 1 GB of RAM and 4 GB of disk space because the n8n image and its dependencies are relatively heavy. In practice, this means Box M (2 GB RAM) is a safe minimum, rather than Box S, whose 1 GB is intended for the entire Box resource pool.

2. What resources does n8n really need?

For simple automations, such as a few workflows with infrequent triggers, Box M is comfortably sufficient because n8n runs relatively stably within its stated 1 GB RAM minimum after startup, leaving headroom for the system and other Box processes.

For heavier use, such as many workflows running in parallel, processing larger files, and integrating with multiple APIs at once, consider Box L (6 GB RAM) so n8n does not compete for memory with other apps running on the same Box.

SSH access with sudo (available from Box M) lets you manually troubleshoot n8n logs, install community nodes, and configure webhooks that require custom reverse proxy settings, which cannot be done from the n8n panel alone.

3. n8n compared with competitors: self-hosted on a bare VPS

Competitor A offers ready-made VPS templates for specific use cases, including the n8n workflow automation platform (VPS offer description, public pricing, status as of 2026-10-10). This means customers get a VPS with n8n as a starting point, but all ongoing server administration, including updates, backups, and security, remains the customer's responsibility.

On a bare VPS from another provider, setting up n8n requires installing Docker yourself, configuring a reverse proxy with SSL, and setting environment variables such as N8N_EDITOR_BASE_URL and WEBHOOK_URL before webhooks work correctly with external services. For anyone without DevOps experience, this is a real barrier.

On Saplo, these variables are set automatically when you install the app from the catalog, so n8n webhooks work correctly as soon as you deploy the app and connect your domain, with no manual environment variable configuration required.

4. Why choose your own n8n instead of the vendor's cloud?

n8n's cloud service uses a subscription model with a workflow execution limit on each plan. With extensive automation, such as processing orders or synchronizing multiple systems, you may need to move to a higher, more expensive plan simply because of the number of runs, not the actual complexity of the automation.

Your own n8n instance on Saplo has no execution counter, keeps data flowing through infrastructure you control (important for automations that process customer personal data), and costs the same regardless of how intensively you use the automation each month. For a team planning to expand its automation over the coming months, predictable costs can matter as much as the workflows themselves. You can add new scenarios without constantly checking whether a new step will increase the bill, making future costs easier to plan than with variable cloud pricing.

5. Who it is for

For a small business automating simple processes, such as notifications or form-to-CRM sync, Box M with n8n is a cheaper and simpler alternative to a paid n8n cloud plan billed per workflow execution.

For an agency or technical team building automations for multiple clients at once, Box L lets you run n8n alongside other apps, such as a Baserow database or Chatwoot, creating a complete toolkit with no execution counter.

6. Typical automation scenarios with your own n8n

Sync a contact form with your CRM: each new lead from the form is automatically added as a contact, with no manual data entry by your team.

Send notifications about new WooCommerce or PrestaShop orders to your team's Slack or Discord channel. For stores with real traffic, this removes the need to check the order dashboard manually.

Automatic invoice generation after an order is paid, connecting your store to your accounting system via API, with no manual entry of order data into invoices by your accounting team.

Monitoring the availability of other apps on the same Box, for example via a Uptime Kuma webhook, and sending an alert when one stops responding before your end customer notices.

Aggregate data from multiple sources, such as a form, store, or calendar, in one place, such as a spreadsheet or Baserow database, without a team member manually copying data between systems.

7. Why n8n and automation only make sense at scale

For a single, simple automation, such as one Slack notification, the overhead of running your own n8n can outweigh the benefits if the alternative is a simple, free webhook without a full automation platform.

With several interconnected processes, such as a store, CRM, accounting, and notifications, your own n8n starts to pay off because one platform replaces multiple separate integrations that you would otherwise have to build and maintain independently.

For companies with a growing number of repetitive manual tasks, n8n is a natural consolidation point for automation, especially when the cost of your team's time on these tasks starts to exceed the cost of hosting n8n itself.

Start with the most painful process to automate, usually the most repetitive manual task, and add workflows gradually instead of trying to automate everything from day one.

8. Cost comparison: self-hosted n8n vs the vendor's cloud over time

The vendor's n8n cloud service uses subscription pricing with a monthly limit on workflow executions. This means costs rise nonlinearly as automation expands: adding another step to an existing workflow or another trigger increases the number of executions, even if the business logic has not changed significantly.

On Saplo, the cost of n8n is included in the Box price, whether a workflow runs ten times a day or ten thousand times a day. As your automation grows, this means infrastructure costs do not rise in proportion to usage.

Looking at costs over a year, self-hosted n8n on Box M or Box L often works out cheaper than a comparable cloud subscription billed in USD for a company running several complex workflows, such as store synchronization, CRM, notifications, and integrations with multiple APIs.

You also need to factor in self-administration costs: updating n8n, monitoring the container, and troubleshooting technical issues. In the cloud model, n8n's vendor handles all of this, whereas on Saplo some of it falls to you, although the Saplo engine makes updates easier through the app catalog.

For businesses with irregular, seasonal usage, such as heavy traffic only during certain months of the year, a fixed Box cost is often easier to budget for than a variable subscription cost that grows with seasonal increases in workflow executions.

The final calculation depends on the specific scale of automation in your business, but the underlying principle is the key factor to consider before choosing between self-hosting and a subscription-based cloud model from n8n's vendor: a fixed Box cost versus the variable cost of workflow executions.

9. The n8n community and the development of n8n as an open-source project

n8n is an actively developed open-source project, with regular releases that add bug fixes, new integrations, and community-built nodes. You can install them in your own instance without waiting for a SaaS provider to decide when to make them available.

On Saplo, you can update n8n to a new version using an update recipe in the app catalog. This makes it easy to keep your instance current without manually tracking releases on GitHub and rebuilding the container after every new engine version.

The n8n community creates and shares custom nodes that extend the platform beyond the integrations built in by default. With a self-hosted instance on Saplo, including SSH access starting from Box M, you can install them yourself, which isn't always possible with a restricted cloud model.

For technical teams, running your own n8n instance also lets you experiment with new, sometimes unstable features before they are fully released. This can be attractive to advanced users, but it requires extra caution when deploying changes to production.

The n8n documentation, independent of Saplo, is extensive and actively developed by the project community. Together with the ready-made, one-click installation on Saplo, it provides a complete environment for learning and developing automations without additional barriers to entry.

10. How to measure the real value of automation built with n8n

Before building an automation, estimate how much team time the process takes manually each month. This gives you a baseline for deciding whether investing time in an n8n workflow is worthwhile compared with continuing to do the work manually.

After implementing an automation, track whether it actually reduces manual errors, such as missed orders or forgotten notifications. This can be harder to measure than the time saved, but it often delivers greater business value than faster processing alone.

For automations that handle customer-facing processes, such as order confirmations, it is worth monitoring whether the workflow remains stable over time. An error in an automation that previously worked manually under human supervision can go unnoticed longer than an error in a manual process.

Measuring the value of automation should therefore include not only time saved, but also the quality and stability of the new process compared with the previous manual solution, before you decide to develop increasingly complex workflows in the same n8n instance.

Over time, as the number of workflows grows, it is also worth monitoring the RAM usage of the n8n instance itself. Many complex automations running simultaneously may require you to move from Box M to Box L before performance actually starts to decline when several workflows run at once. Monitoring this is simpler than it sounds: the Saplo dashboard shows the container's current RAM usage, so you can check the indicator from time to time instead of waiting for a clear slowdown that becomes noticeable only to users of the automation.

11. Summary: n8n as the foundation of business automation

Your own n8n instance on Saplo, with no execution counter and full control over the data flowing through your automation, provides the foundation for increasingly complex business processes without worrying about a growing subscription bill. For a company starting with one simple automation, progressing to a dozen connected workflows supporting your store, CRM, and customer communication is a natural evolution within the same fixed Box cost, rather than a series of decisions to raise your limits on an external cloud platform.