Self-hosted n8n automation
Your automations, on your own infrastructure.
No data leaves your building. No per-task fees. No vendor who can change the terms on you next quarter. I migrate teams off Zapier and Make onto self-hosted n8n, and build the workflows that run the business.
45+ production automations built · 30+ live n8n workflows · Streck Ventures LLC, Missouri
The case for moving
The migration pays for itself, and you can check the arithmetic yourself.
This is the whole pitch. There is no part of it you have to take on trust.
Zapier or Make, today
$89+/mo
and it grows as you succeed
- Billed per task — the bill scales with your volume
- Task limits you hit at the worst possible moment
- Your data passes through someone else’s servers
- Pricing and terms are theirs to change
Self-hosted n8n, after
~$20/mo
a small VPS, and that is the whole bill
- Unlimited executions — no per-task fee, ever
- Runs on your infrastructure, or a server you own
- Nothing leaves your network unless you send it
- You own the stack outright. No lock-in
A typical migration runs $1,200–2,000 and covers server setup, workflow migration, testing, documentation and handover. Against an $89/month Zapier bill dropping to about $20, it pays for itself and then keeps paying. After that, the savings are yours.
Who this is for
Some teams want self-hosting. Others have no choice.
A good fit
- Healthcare, legal, finance and government contractors — compliance blocks cloud automation tools outright, so self-hosting is the only route
- Teams already paying $100+/month to Zapier or Make, watching the bill climb
- Companies with an ops person who can describe the process that needs automating
- Agencies that need white-label automation delivered reliably
Not a fit — and I will say so
- Budgets under $300. The hours do not work
- “Build me an AI that does everything” with no defined process
- Anything needing 24/7 on-call availability
- Work I cannot deliver properly at my current capacity
Services
Five ways to work together.
Fixed scope, fixed price, stated up front. If a job does not fit one of these, say what you need and I will quote it.
Flagship
Zapier / Make → self-hosted n8n migration
$1,200–2,000
Server setup, every workflow migrated and tested, documentation, and a handover so your team can run it without me.
Start here
Automation audit
$500–750
Your current processes mapped, the top three opportunities ranked by hours saved, scoped with prices. Credited against a build if you proceed within 30 days.
Single build
One workflow, done properly
$800–1,500
One workflow, self-hosted, documented, with real error handling. A sensible first project together.
Full build
Multi-workflow system
$2,500–4,500
Lead capture to CRM to notifications, or whatever your equivalent is. Self-hosted setup, error handling, documentation, and 30 days of fixes.
Ongoing
Monthly retainer
$1,200–2,000/mo
Maintenance, monitoring, and a set number of new workflows each month. Offered only when I genuinely have the capacity to serve it.
Not sure yet
Tell me the problem
Free
Describe what is being done by hand. I will tell you honestly whether it is worth automating, and whether I am the right person for it.
Selected work
Production systems, not demos.
Every one of these runs on a schedule, handles its own failures, and has been in production long enough to have broken and been fixed.
Call transcripts parsed into the CRM
Teams record their calls, but what gets said rarely ends up anywhere useful. I build n8n pipelines that pull each transcript, run a structured analysis over it, and write the result to a custom object next to the account record — with a weekly digest to the team channel. Daily schedule, deduplication, retries, and alerting when a step fails.
Competitor battlecards, refreshed automatically
Competitive research redone by hand every quarter is stale within weeks. I build two scheduled workflows: one regenerates battlecards across 30+ competitors on a fixed set of dimensions every week, the other watches pricing pages, hashes content to detect real changes, and emails the team only when something actually moved. No manual effort after setup.
MCP servers connecting six business systems
Model Context Protocol servers in Node.js for Salesforce, Gong, Monday, Zendesk, Zoom and Slack, plus a hosted platform on native OAuth2 — so assistants query live business systems directly instead of through copy-paste. Infrastructure work, and the piece most automation contractors cannot do.
How I build
Most automation breaks quietly. That is the part you are paying for.
Failure is part of the design
Rate limits, fan-in races, partial failures, silent drops, duplicate runs. A workflow that works on a good day is a demo. Retries, deduplication, dead-letter handling and alerting are what make it something you can depend on at 3am.
You get the keys
Everything is documented and handed over. The server is yours, the workflows are yours, the credentials are yours. If you never speak to me again it keeps running, and any competent engineer can pick it up.
Background: 45+ production automations and 30+ live n8n workflows built in an AI enablement role at a construction SaaS company, plus a support and CRM SaaS product I built and ran in production from first commit to paying infrastructure. That is where the self-hosting experience actually comes from.
Get in touch
Tell me what is being done by hand.
Include your current tool and roughly what you pay for it, if you have one. I will reply with whether it is worth migrating, a rough number, and what I would need from you — or I will tell you it is not worth doing.
Or email directly: devonstreckfuss@gmail.com