I recently came across a Reddit post that struck a chord with me. The author, rohit-joshi, shared their experience of trying to self-host n8n, a popular automation tool, but ultimately gave up due to the numerous challenges they faced.
From deploying it locally to using Oracle Cloud, Google Cloud, and Amazon EC2, they encountered issues with webhooks, backing up, and more. It was a frustrating and time-consuming process, especially for non-tech individuals like themselves.
The author’s realization was a valuable one: the time spent on self-hosting could be better utilized building automations instead. This got me thinking – when do we know it’s time to seek help and abandon the self-hosting dream?
For many of us, the allure of self-hosting lies in the control and flexibility it offers. However, as rohit-joshi’s experience shows, it can also lead to unnecessary headaches and wasted time. So, how do we know when to cut our losses and opt for a more convenient solution?
Perhaps the answer lies in evaluating our priorities. Are we trying to save money, or is our time more valuable? Are we comfortable with the technical aspects of self-hosting, or would we rather focus on building and creating?
In the end, rohit-joshi chose to invest in a cheap n8n hosting service, and it’s likely that many of us will follow suit. After all, as the saying goes, ‘time is money.’ By recognizing our limitations and seeking help when needed, we can focus on what truly matters – building and growing our automations.
What’s your take on self-hosting? Have you had a similar experience, or do you swear by the DIY approach? Share your thoughts in the comments below!