Design, deployment and handover for self-hosted n8n or n8n Cloud, including database, backups, monitoring and operations documentation. From THB 70,000.
Request an n8n assessmentOfficial references checked:
iReadCustomer n8n installation starts at THB 70,000–105,000 for a production foundation, based on our published THB 7,000 man-day rate. A launch package with staging, initial workflows and a restore test starts at THB 126,000. Queue-mode deployments for higher workloads start at THB 252,000.
These ranges cover implementation services. VAT where applicable, cloud infrastructure, n8n plans or licenses, API usage and other providers are excluded. Every assumption is shown before you approve the Statement of Work (SOW).
Architecture choice
We choose the deployment from data sensitivity, workload, recovery needs and the team that will operate it. The simplest architecture that meets the acceptance criteria is usually the best one.
| Option | Best fit | What is delivered | Trade-off |
|---|---|---|---|
| n8n Cloud | Teams that want to launch quickly without operating servers | Workspace, credentials, workflows, error handling and access configuration on n8n’s service | The customer pays n8n directly and features depend on the selected plan |
| Self-hosted production | Organizations that need hosting, data-region or private-network control | Container/Docker, PostgreSQL, reverse proxy/TLS, encryption key, backups, logs and health checks | The customer owns the infrastructure cost and long-term operating responsibility |
| Queue mode | Higher concurrency, heavier jobs or workloads that need additional workers | n8n main and workers, PostgreSQL and Redis, worker health/readiness and a scaling plan | More components and operating cost, so we use it only when workload evidence justifies it |
Production scope
The final scope is confirmed in the SOW. Every production option addresses security, recovery, observability and handover—not merely starting a container.
Deploy to n8n Cloud or customer-controlled infrastructure with environments matched to risk.
Keep credentials out of workflows and source repositories.
Back up the assets required for a real recovery and document ownership.
Give operators a clear signal when a workflow or the platform fails.
Prepare business integrations for bad input and upstream outages.
Avoid locking the customer into contractor-owned accounts or undocumented knowledge.
Transparent pricing
The ranges are planning bands based on THB 7,000 per man-day. The final quote depends on integration count, data complexity and availability requirements.
One self-hosted production environment or a properly governed n8n Cloud workspace
THB 70,000–105,000
10–15 man-days
Organizations that need staging/production and their first priority workflows
THB 126,000–210,000
18–30 man-days
Higher concurrency, heavier jobs or specific operating requirements
From THB 252,000
From 36 man-days
A range becomes a fixed quote only after access, integrations, data classification, expected concurrency and acceptance criteria are confirmed in the SOW.
Delivery process
Identify workflows, data owners, source/target systems, volume, retention and the impact of downtime.
Choose Cloud, self-hosted or queue mode and document scope, pricing assumptions, acceptance criteria, RPO/RTO and owners.
Deploy, integrate and test failure paths, security, backups and monitoring; obtain user acceptance in staging when included.
Release through a checklist, transfer accounts and runbooks, and confirm the purchased support window or SLA.
n8n processes workflows; the organization still owns lawful basis, purpose and retention decisions. We implement technical controls against the approved data map and policy, but the service does not replace legal advice.
Your team should understand the architecture, be able to deploy or restore it, and control the important accounts.
The architecture statements on this page were checked against n8n’s official documentation on the stated date and must be checked again when versions or requirements change.
Design workflows, AI agents and integrations around business processes.
Model three workflow sizes, API, hosting, monitoring, maintenance and human-review TCO.
Move from readiness and pilot to production with acceptance tests and handover.
See the THB 7,000 man-day rate and estimation examples.
Estimate payback before choosing the first workflows.
Send your integration list and requirements for a reviewable scope.
Straight answers for teams comparing n8n Cloud, self-hosting and queue mode.
Production Foundation is THB 70,000–105,000, Automation Launch is THB 126,000–210,000, and Scale/Queue Mode starts at THB 252,000. These bands use the published THB 7,000 man-day rate and exclude cloud, n8n plans/licenses, APIs, VAT where applicable and work outside the SOW.
Use n8n Cloud when speed and low infrastructure overhead matter most. Self-host when you need control of hosting, networks, data region or internal-system connectivity. Base the choice on a data map, security policy and operating ownership—not server price alone.
No. Queue mode is for higher concurrency, heavier work or scaling across workers. n8n’s documentation describes Redis as the message broker and recommends PostgreSQL rather than SQLite for queue mode. We do not add Redis when a single instance meets the requirement more safely and simply.
No tool installation guarantees PDPA compliance. We can implement technical controls such as data minimization, retention, access control, secret handling and policy-aligned hosting. The customer must confirm lawful basis, purpose and organizational requirements with its legal owner or DPO.
Yes. Cloud, domain and external-service accounts should be controlled by the customer. We hand over workflows, architecture, configuration inventory and runbooks defined in the SOW. Live secrets are not placed in a general repository or handover document.
Production packages include backup design and health monitoring within scope; Launch and Scale include a restore drill. RPO, RTO, support window and SLA are stated in the SOW. A 24/7 on-call service or uptime guarantee is not automatically included.
Man-days describe effort, not a guaranteed calendar duration. Foundation is 10–15 man-days, Launch is 18–30, and Scale starts at 36. The calendar depends on system access, security approval and third-party API readiness.
Send us the systems to connect, expected workload and data requirements. We will respond with architecture options, scope and pricing assumptions—not only “it depends.”
Request scope and pricingOr reach us directly
