Hwee-Boon Yar
@h_boon
Write software Swift(iOS+macOS) + TypeScript
Remote since forever
hboon.com/about
If "I" works, "we" works too, unless you explicitly want to brand yourself as the face of the company for a long time. This could be for the company or this could be to build your personal brand.
I'm really excited to do 100% of it myself. I plan on doing so going forward as well.
Depends on whether you hire contractors/part-timers or full time staff. If it's the former, they might not even want to be directly associated in name/public with your company. If this is your predominant mode, then "I" works well (and of course "we" too, as mentioned in the first line).
For 1, 2, 3:
This follows above. But, if you credit individuals, you could also consider crediting specific people (other than you) who did that work. Being able to build their brand also makes it easier to get people to work with you.
IMO, unless you want to grow into an agency/consultancy in the short term, using your own name is fine and good. You can always change the name later. By then you would have enough traction and re-branding is not as difficult.
Coolify has a self-hosted version though. How are you positioning your solution? I saw your landing page. Are you just selling a hosted version of Coolify with you managing it at a slightly lower price?
Coolify still requires configuring your servers + resources + understanding of Coolify (e.g. proxies, redirects, ssh keys, backups, etc.)
Indiehost would be even more of an abstraction (sign in with cloud provider + connect git repo and it does the rest)
Of course, the abstraction has its drawbacks (less control), so would be targeting simpler use-cases
🤣 in real world exchanges, I usually go by "Boon" because it's also pronounced like the English word. So feel free to go by that :)
Hello!
Hello there!
Hi Hwee-Boon! I’m at the gym trying to pronounce your name, wish I could leave voice note to check in with you! 😅
🤣 in real world exchanges, I usually go by "Boon" because it's also pronounced like the English word. So feel free to go by that :)
Hello!
I used to use Heroku and have switched to Render for my newer projects. It's basically a newer and cheaper version of Heroku.
I was just researching recently because there's a fair chance I might ship a few more projects and see which sticks; so wanted to know what is a more cost effective option to have many, low traffic sites. Even Render starts to get expensive as you run more of them (I still have projects hanging around from more than a year ago).
If you are using Ruby on Rails, It's worth checking out Hatchbox.io. It looks really attractive price-wise. I can't use it unfortunately because I'm using node/bun. I'll check out coolify.io/ at some point since that seems to be closer to Hatchbox.io but not tied to RoR.
I built this little comparison calculator for the services I looked at for SEO, but you can see if it helps you at least get an idea of the difference in models of PaaS vs VM vs VM+hatchbox pingnow.net/hosting-comparison
As an indie founder/developer, my rule of thumb is if I don't have (enough) customers, I am not spending enough time marketing.