Your workflows. Connected to your client work.

No. The thing we have configured is a self-hosted deployment, n8n is running on a server of your control, be it a VPS that we mutually agree on or existing infrastructure.

n8n cloud is a distinct product that n8n themselves operate, and has its own pricing, limits and support. This is not a migration of your Cloud account, should you already have one. It is another arrangement and another owner: you.

The practical advantage is the control. You determine the version, the resources and the location of the data. The trade-off is that somebody must keep it, which is the purpose of the hosting agreement.

That depends on what you sign up for, and it's worth being clear about upfront.

One thing is to set up a deployment. Another is to run it month after month. Maintenance of servers, n8n version updates, backups, and maintenance in the event of a broken workflow, all that is different, and your contract talks about what of it is included and by whom.

Certain customers will purchase the whole package. Others would prefer us to construct it, write it down, and give them the keys to have it operated by their staff. Both are fine. What we do not want is to have you think that something is covered and it is not.

Yes, usually, but should be checked, not presumed.

At setup we look at what you already have running: what tools you need to connect, which tools have a node or API path in n8n, what credentials do they require, and do you have the access permissions to do so. We view the available workflows in the same way.

The majority of arrangements will adjust without a significant amount of resistance. Sometimes a tool lacks a clean integration, or there is an API tier constraining the possibilities and that defines the design. It is better to discover it during setup than three weeks into a live workflow.

Not via the portal. Client portal access is to view, examine and act; it does not give editor privileges to n8n.

In case clients require to build or edit, that is another setting. It needs proper deployment configuration, proper license and a few considerations on what you want them to be touching. It can be embedded within a client-facing surface as well but it is a scoped piece of work not a toggle.

Workflow creation with the help of AI belongs to the same category. It can be done. It must not be turned on afterwards but an arrangement must be made to make it operational.

Whatever your order says, that's why we keep the scope written down.

Hosting and server resources, access arrangements, and the level of support are all defined in the order. And n8n licensing and any charges of API or AI use, and they are only covered where it is clearly indicated.

The rationale behind the warning: API and AI prices grow with usage. A daily twice a day workflow is not expensive. The workflow which is executed every few minutes on a dozen clients is another number. We would rather make expectations in writing than issue you with a surprising bill.

No, and it is good policy to rectify that assumption early.

Self-hosting implies the existence of n8n on your server. That does not imply that data will not move out. Any process that utilizes an external application, a service API or an AI service, is transmitting data to that service, under the conditions of that service.

The rest we can control: where the records are stored, what each connection is allowed to send, how long things are kept, and whether the setup is to your compliance needs. Those are negotiated with your particular deployment; it does not offer the same answers to all.

Either works. In case you already have a provider, you are pleased with, we will deploy there. Otherwise, we will suggest configurations depending on the amount of CPU, memory, storage- and what you desire to spend that your workflows require. That is up to you, we only ensure that the specs suit the job.

Often, yes. We review them when setting them up: what they do, what they can connect to, and whether they will run in the target n8n version. Some transfer cleanly. Others must be changed to accommodate credentials or node alterations. We will inform you which is which before anything goes live.