Can you compare naden and make for us their pros and cons? Which one is better? For which work specifically and for whom? Is self-hosting none worth for beginners?
Naden is more technical and low‑code, making complex builds easier if you have the technical fluency, while Make.com is truly no‑code and simpler for straightforward projects. I recommend Make.com for beginners nine times out of ten because it’s easier to use, and most users succeed faster with it. Self‑hosting Naden is not worth it for beginners due to its steep learning curve. If you want to build a personal brand, focus on outbound marketing like cold email and Upwork rather than relying solely on video content.
It makes sense. I focus on getting up and running quickly, moving fast, and breaking things—that's why I always recommend Make.com. If you're more technical, I get the appeal of NADN, but I ask myself whether I actually need that complexity to make money. The answer is no; people have been making money with simpler tools for as long as the internet has existed, so tool complexity isn't the bottleneck.
He has a video that explains his thoughts on NAD versus NAND. He suggests searching “make versus NAND Nick” to find a blog post and a detailed video where he goes into detail. He notes that the “make” approach is better for beginners.
This is great. I'm going to do that. Why don't I quickly make a note? I'm going to do it on my phone because I don't want you to see my entire note thing and I have some pretty private things in there right now. But I'm going to say add self-hosting video to Q because there's a lot of demand for this right now and I would rank much higher than most other people on it.
Yes, the best option is to pay the default fee for a carefree experience with all the hassles. I'd love to see a video on this, as I was almost tempted to go self-hosting and learn the platform. I've tons of experience breakinging down barriers and obstacles of self-hosting and common apps affected by it, and how much more effort and time is needed to manage and maintain. Suffice to say, the reason I typically recommend cloud hosting everything is that you don't have to deal with deployment, DevOps, or additional environment variables and similar self-hosting concerns. As an automation specialist, believe it or not, your main point of value is not in your technical knowledge; it's in knowing just enough of the technicals to apply them to real business processes. Then you spend the rest of your time becoming a business person, a business expert. That's where the leverage lies with the alpha people who get really into self-hosting—they often lose the cart for the horse, spending so much time figuring out every little technical detail, spinning up Docker containers, getting environment variables right, and doing EngineX pass-through for webhook URLs. It's incredible how much time that takes. My recommendation is to focus on the things you actually get paid for—delivering value to your clients—not on designing the most optimal, technically and academically perfect solution.