An agency that builds automations for clients ends up running servers for them, which is not the business it set out to be in. The first client's n8n lives on a VPS; the second shares it "for now"; by the fifth, one client's runaway workflow slows the others, a credential from one is visible to whoever administers the box, and the agency's engineer spends Friday evening on updates. This guide is how agencies and freelancers use managed instances instead: one isolated instance per client, run by RinooSol, with the agency keeping what it is paid for, the building.
The shape
- One instance per client. Each client gets a private n8n instance: its own container, database schema, credentials and subdomain. Nothing is shared between clients, and a loud client's load does not touch a quiet one's.
- The agency builds; the operator runs. The agency's engineers build and maintain the workflows and own the client relationship. RinooSol runs the instances: updates, backups, SSL, monitoring and the night something breaks.
- Billing in pounds, per instance. Each instance is a plan on the pricing page, monthly or yearly, paid by local card or transfer. The agency bills its client however it likes; the hosting line is a known number in pounds.
Why isolation is the point
Clients ask three questions eventually: can other clients see our data, can your engineer see our credentials, and what happens to our workflows if we leave you. On a shared server the honest answers are uncomfortable. On a per-client instance they are simple: no, because the container and schema are theirs; only with your permission, because credentials are encrypted with a key that belongs to the instance; and they export in n8n's own format and run anywhere. The security page is written to be sent to a client who asks.
Access without sharing passwords
The agency's engineers are users on the client's instance with their own logins, added and removed as people join and leave. The client can have an owner login too, so the instance is theirs in fact as well as in principle. Nobody shares an admin password across clients, and nobody has root on a box that holds other people's data.
WhatsApp per client
A client whose system uses WhatsApp gets its own WhatsApp API instance next to its n8n, connected to the client's own number. Numbers and sessions are never pooled across clients, which is both what Meta's rules expect and what keeps one client's restriction from touching another. The Evolution versus official comparison is the conversation to have with each client about which route fits them.
Handing a client over, or taking one on
Because every instance is standard, moving is boring, which is the point:
- A client who leaves takes an export of workflows and credentials, or keeps the instance and pays for it directly; the plan moves to their account.
- A client who arrives from n8n Cloud or a shared server follows the migration guide: export, import, check, switch.
- An agency that grows adds instances; nothing has to be re-architected at ten clients or at fifty.
What the agency keeps
The workflows, the client relationship, the margin on the build and the maintenance retainer. What it gives away is the server work and the 2 am message, which were never billable anyway. The freelancers page describes the same arrangement for one person; the VPS versus managed guide is honest about what the shared box costs in hours.
Partner terms
Agencies that bring clients onto RinooSol instances can join the partner program, which pays a commission on each client's plans; the partner terms describe attribution and payout. It is a referral arrangement, not a reseller one: the client's instance is the client's, whoever introduced them.
Starting
The quickest way to see the shape is to put one client, or your own agency's workflows, on a plan and work in it for a month. For an agency with existing clients to move, a free consultation is where we plan the migrations in order.