Can an AI receptionist run on self-hosted n8n?

The call logic Humbrook builds runs inside n8n, and the instance belongs to the client, not to Humbrook. That instance is either self-hosted on a server the client controls, or an n8n Cloud account opened in the client's name. Either way, it is an account the client can open and look inside on the day the build is handed over.

Vapi carries the voice and Twilio carries the phone number, and both follow the same rule: an account the client opens, in the client's name, billed directly to the client at those vendors' own rates. Humbrook builds inside all three accounts and then hands them over.

Nothing is rented back. There is no Humbrook server sitting between the client's number and the client's calendar, no per-seat licence, and no account that stops answering because the relationship with Humbrook ends. On the day the client wants to change something -- a script, a routing rule, which calendar a booking lands on -- the workflow is visible and editable inside their own n8n, by them or by anyone else they choose to hire.

Owning the instance is not free of upkeep, and a page that only argues the upside here would be a brochure, not an answer. An instance the client owns is an instance the client is responsible for keeping current: security patches, n8n version upgrades, and the server itself if it is self-hosted. Humbrook can keep touching it after handover, on request, but that is a separate arrangement, not something the build includes by default. For an owner who does not want a server to think about, an n8n Cloud account in the client's name is the lighter of the two paths: n8n handles the hosting and the updates, and the workflow is still entirely the client's, still visible, still theirs to move elsewhere if they choose.