6 ms·
I'm definitely not target market for this, but even trying to think open mindedly, I still I don't see people paying for this. I just don't get it. It's not spe
by koolba 9y ago
I'm definitely not target market for this, but even trying to think open mindedly, I still I don't see people paying for this. I just don't get it. It's not specific to Caddy either, I just don't see people paying to install any web server software. The hurdle of coordinating an install that requires any kind licensing vs. something that's baked into the core package repos for my OS makes it a non-starter.
Then there's the instance counting. From the FAQ:
>> What is an "instance"?
> The commercial license grants the right to use Caddy in a commercial context based on how many instances you run or how many employees will be using Caddy ("users") at any given time. An instance is an OS process of Caddy. For example, if you have 2 instances of Caddy in production and 3 web developers using Caddy locally to build your website, that's 5 instances. (A single developer who starts multiple instances of Caddy temporarily in local dev can still just count as 1.) If you also spin up a maximum of 3 containers at a time with Caddy binaries inside it, that's a total of 8 instances. If you distribute Caddy to others, contact us for distributor pricing
I'd suggest getting rid of the local developer license. If anything, you want more people using it locally so that they end up using it in production. I know that the vast majority of people will not try things out if they think they're going to be paying $25/mo per developer. Heck, I'd get rid of non-prod pricing entirely.
Best of luck on this but I just don't see the commercial angle working out for it. And it's not something like a PaaS or DBaaS where you can offer it as a SaaS.
- sheetjs 9y agoThere really is no good way to monetize the existing open source product outside of support contracts. Developers will know that building from source is an option. The approach that nginx and other projects use involves an open source core that solves one problem well and a series of proprietary extensions that solve related problems. It's not clear if the caddy extensions are worth paying for, and it's definitely not clear if those solutions are better than nginx offerings
- mholt 9y agoThe main problem with that is it can be hard to distinguish local development from internal service that is constantly being developed. The line between production and Dev can be complicated or blurry. So to keep things simple it's just straight instance counting. We lowered the price to account for that.
- notyourday 9y agoCaddy's developers don't understand that Oracle licensing model does not work in 2017.
- jamespo 9y agohttps://finance.yahoo.com/quote/ORCL/chart?p=ORCL https://finance.yahoo.com/quote/ORCL/chart?p=ORCL
- notyourday 9y agoCaddy has no head start and no contract lock.
- nodesocket 9y agoCaddy is a solid piece of software, the let's encrypt integration alone is amazing. The majority of comments here on HN seem to be negative about the pricing and commercial structure, which to me is a bit absurd. This is after all a forum for entrepreneurs right? More power to the Caddy team for trying to monetize. When you work hard, create a great product, you have every right to monetize. Quite honestly I am growing weary of the entitled, everything should be free, universal income, frugal, mentality on HN.
- koolba 9y agoMy negativity isn’t about the the commercial pursuit itself, it’s about their prospects. The market that they’re going after simply doesn’t pay for web servers so it’s a very uphill battle. That and they’re pricing model, in particular charging for local dev, would inhibit things even more. I’m about as capitalistic as they come. I don’t think everything should be free. I’m perfectly fine with people charging for their goods and services. And in particular I have no qualms with charging for software, hell I do it myself! I’m simply saying the business, at least the way they’re approaching it right now, is not viable regardless of the technical advantages of the Caddy over the competition.
- stephenr 9y ago> the let's encrypt integration alone is amazing Really? How so? There are literally dozens of packages that will register and renew certs with LE using the ACME protocol, and last time I checked none of them will cause your web server to refuse to start, with a valid certificate, because LE is down. I find the whole concept to be quite conflicting. Their potential market is a Venn diagram of organisations who: want to use LetsEncrypt but can't install certbot; can justify spending $25 a month per instance for a web server licence; can't compile a go binary.
- nodesocket 9y ago> There are literally dozens of packages that will register and renew certs with LE using the ACME protocol, and last time I checked none of them will cause your web server to refuse to start, with a valid certificate, because LE is down. The work Caddy has put in though beyond the tech; business, pricing, support, is what differentiates a cool "project" from a business, that effort should be applauded in my opinion. Launching a project is tough... Adding pricing, support, and creating a business is in another league of difficulty.