The process crosses several systems
Documents, leads, reports or customer data move between tools by hand. n8n can handle the transfer and keep a record of each run.
Home / n8n development
n8n workflows on your server
I build, deploy and document n8n automations. Failures alert your team. The server, billing and credentials stay in your accounts.
Use cases
When n8n is a good fit
A failed run needs a clear owner
I add failure paths and alerts, so your team knows what stopped and where to continue.
Delivery
Included in the build
Deployment
n8n on your Hetzner server, deployed through Coolify. You hold the root access and pay the provider directly.
Workflows in version control
Exported as JSON to a Git repository, so every change has a history and a rollback.
Error alerts
Failure paths route to email or Telegram with enough context to act on.
Written handover
Documentation of what each workflow does, what it touches, and how to change it safely.
Example
Relevant work
Telegram Mini App on an n8n backend
A React app inside Telegram with n8n handling the backend workflow. The team uses the interface; n8n processes and stores each action on the client's server.
React · Telegram Mini App SDK · self-hosted n8n · Hetzner + Coolify · Cloudflare Pages
Pricing
What n8n work costs
A scoped workflow starts at €900 and takes 1–3 weeks. A workflow with a dashboard or bot costs €2,500–6,000 and takes 4–8 weeks.
FAQ
FAQ
Should I self-host n8n or use n8n Cloud?
Self-hosting gives you more control over cost, data and access. n8n Cloud removes infrastructure work. I will recommend the option that fits your volume and operating needs.
Can my team edit the workflows afterwards?
Yes. That's the point of self-hosting on your own instance. You get admin access, and the documentation explains which parts are safe to change without breaking something downstream.
What does hosting cost me per month?
A Hetzner server that comfortably runs n8n for a small business is in the low tens of euros per month. You pay Hetzner directly — I don't resell hosting.
Do you work with existing n8n setups?
Yes — migrations off n8n Cloud, cleaning up inherited workflows, and adding error handling to automations someone else built.
Related
Other things I build
Contact
Describe the process
Tell me what your team still does by hand, where the information comes from and what should happen next.