Ask HN: Does an open source model work for me?
My service is two parts, an app, and a back-end, that works as a sort of montage / archival tool that fills a gap I felt with other apps out there.
When I show others, some people suggest that it would be useful for them too, and they could even foresee spending money on it.
But I don't want to spin it up as some “startup” - I have work and a family to take care of, and so I need to be able to balance “side money coming in” and “side work going out” - I don't think a traditional startup fits in this requirement.
I want to be able to run this service for people, but it's a non-zero cost for servers and storage space, so I'll have to charge for the service, which is fine. People could also download and run it themselves for free, no sweat off my back..
I'm thinking the best option might be to open up the source and let people do what they like, then just offer the main service as a paid for option, and rely on honesty and branding to say mine was the OG.
Does this make sense? Will it add more work onto myself (managing an open source project as well as the “service”)?
Is there anything that I need to be mindful of if I try and operate this way?
My goal really is to help people (put it out there as open source and run a service) and if I can, I'd like to get a little bit of income from it to help look after the family, but not so much that it becomes a second job..
5 comments
[ 2.7 ms ] story [ 20.3 ms ] thread99% of the small-scale (with 1-5 core-developers) open source projects is labor of love[0]. It also shows good on the CV (which might make it worth paying it out of your pocket). But doing it for the money is almost always a lost cause, even we are talking about a nominal fee.
[0]: source of this data: well, I just pulled it out of my bottom. But it doesn't make it incorrect.
I mean they could spin up a server and connect the app to their server but they'll have to pay money for it somehow and figure out how to do all that.
Paying for my service is just the easiest option for people who want the product.
* (possibly OS app)
* (possibly OS backend)
* paying users on your server
> Paying for my service is just the easiest option for people who want the product.
Not easy for you! Setting up payment, means handling personal info (payment methods at least), possibly hooking into 3rd party payment providers, complying with legal requirements, etc.
Maybe you can keep this part really simple (like users pre-pay by bank transfer, you send login info through email). But don't underestimate! The internet is riddled with ads because making small payments easily is.. difficult.
Good luck.