I can only speak for myself (I made UXWizz): I feel like interest has always been there for different platforms, most are still too simple or too complex and hard to set up and use.
In my case, I am simply focused on the self-hosting niche, trying to make the best self-hosting experience. I have an advantage here, because most other tools earn their money from their cloud version, so they don't really want you to self-host, thus usually provide different "open-source" versions and rarely provide support for it.
Also, because "cloud-focused" analytics are built for scale, they are actually not optimal for tracking smaller amounts of traffic (most websites don't have millions of visitors per month), so they use more resources for running scale-proof stacks.
I'm working on releasing a product and I am trying to figure out between: self-hosted and SAAS model.
My question is: I want to release it as self-hosted, but I think the risk of giving the customer the source code is too high... they can just release it as open-source or sell it at a lower price, so my business is dead? how do you do it?
Is it worth trying to obfuscate code or compile it as a binary so they cannot access the code?
Also, with it being self-hosted, how are you chargin a monthly fee? If you are chargin for a monthly fee, can't the customer just remove the product licence validity check? e.g. they remove verification that they have purchased a licence?
You can't beat piracy. Look at video-games. Just make it easier to install and set-up when purchasing than when pirating. Also, the automatic updater only works with a valid license key and support is also only provided with a valid key.
OK, firstly thank you so much for the reply! I have also sent you a DM on X to try and get your input, but you already replied here so cheers!
So I was focused on the wrong thing… focusing on rem ing the possibility of fraud/theft/piracy etc… but what you are saying is focus on charging for product updates I.e. new releases which require a valid key + direct support.
Thanks for helping me get this straight in my head.
I feel that selling as a self-hosted model will allow me to operate as a solo founder without the overhead of legal complications with GDPR/Security certifications/ owning the liability of having my customers data… if it is self-hosted they can do what the fuck they want with their own customer data and I don’t need to own that liability… this was my thinking… but then obviously I made the error of focusing too much on trying to avoid theft.
Thanks again.
I have followed you on X, would be great to connect there.
Wishing you lots of continued success! Appreciate your time and advice.
Matt
In my case, I am simply focused on the self-hosting niche, trying to make the best self-hosting experience. I have an advantage here, because most other tools earn their money from their cloud version, so they don't really want you to self-host, thus usually provide different "open-source" versions and rarely provide support for it.
Also, because "cloud-focused" analytics are built for scale, they are actually not optimal for tracking smaller amounts of traffic (most websites don't have millions of visitors per month), so they use more resources for running scale-proof stacks.