Doubts on n8n licensing model & architecture

Questions
1

Describe the problem/error/question

Hello guys,

First and foremost, this is my first post around here, so I did my best to do my “homework” on going over the n8n documentation, pricing, so on. I’ve been using it for a while now on a VPS for my personal automations, but recently I started working on an automation project for a startup. This changes completely the picture of doing something personal to a business one so I want to make sure I’m doing the right thing.

To simplify what we want to achieve, it’s basically an automation to act as accounts receivable collection agent that will interact with debtors via instant message (mainly whatsapp and telegram) and negotiate their debts according to certain policies.

Question #1

Basically, my automation will be called by an external platform and once we have an agreement with the debtor, I send it back to the platform what was agreed - we have around 4.000 debtors nowadays.

I need to make sure n8n can handle this amount of workload, so checking the pricing and licensing, I got these pricing packages. I’m honestly between the PRO and BUSINESS plans but one thing that comes to my mind is the “concurrent executions”.

Right now, I have just one workflow that handles the first interaction with the debtor, inside the same workflow, a parallel workflow line to handle further messages with debtors.

By concurrent execution, I believe that it refers to the amount of different workflows can be called at the same time, but I’ve only one so I don’t think that I should worry about it. At this time, I think I should worry about the number of executions. Thus, I’d like to understand whether if my understanding is correct.

Question #2

For my personal automations, I’m using n8n in Hostinger (VPS) and going over the deployment models, I only saw two in the n8n documentation: n8n cloud or self-hosted (which I believe that this also counts as a VPS).

In terms of VPS, do you guys think that the automation I’m building for this startup, could be a fit?

n8n-pricing
n8n-pricing1331×1044 308 KB

Thanks a lot and sorry for dropping such a long text.

Best Regards,

Information on your n8n setup

  • n8n version: 2.13.4
  • Database (default: SQLite): Supabase
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): -
  • Operating system:
2

Hi @Felipe
concurrent executions == simultaneous runs of any workflow in your cloud instance, not just separate workflows. As only production executions count means live runs, not test case flows or runs.

If you actually need a VPS, then for your use case, it’s better as your usage is high in terms of executions

I think you should read this:

3

Welcome to the n8n community @Felipe
Adding to what Anshul mentioned, pay attention to wait nodes, webhooks, or asynchronous conversations that remain open for longer periods.
In my opinion, with emphasis, use postgresql and consider queue mode as the load grows.
Start with everything organized and structured.
Check out this documentation:
Sustainable Use License | n8n Docs

Configuring queue mode | n8n Docs