Announcing Caddy Commercial Licenses

Post by fps » Wed, Sep 13, 2017, 2:26 PM UTC

mholt wrote: post #33

stavros wrote: post #19

I've been trying to get Caddy more widely deployed at work, and this move is going to alienate commercial customers (at least us) even more than Caddy already does. Not only do they not have repositories, essentially doubling the effort to keep machines up to date (we have to have one process to upgrade everything else , and one process to upgrade just Caddy ), but now we can't even download precompiled binaries to d…

> Not only do they not have repositories, essentially doubling the effort to keep machines up to date (we have to have one process to upgrade everything else, and one process to upgrade just Caddy) Cory's working on this, actually. If we can get it working, we should be able to offer official Caddy packages to all our customers, customized just how they need it to be, so your 'apt upgrade' could upgrade Caddy as well…

Post by mholt » Wed, Sep 13, 2017, 2:28 PM UTC

nevi-me wrote: post #43

mholt wrote: post #11

Earlier quoted context omitted.

You're right, you can build from source under the Apache license. Keeping the project truly open source is really important to us, because the community is such a great part of using Caddy. Commercial licenses would only cost hundreds of thousands of dollars per year if your organization has at least 160 instances in use. Keep in mind that modifying the source is required to plug in any plugins, which people tend not…

I pay $149 a month for a server, I was using Nginx + nghttp2 (for gRPC), until last month when I switched to Caddy (LE benefits). I'm not familiar with Go, so I can't modify source to get the plugins I like. I read the announcement page, and can't find what the cost is, but it doesn't matter. My work doesn't count as non-x, because I want to someday make an extra income from it. I've found Caddy to be a cool and inte…

Post by mholt » Wed, Sep 13, 2017, 2:29 PM UTC

StavrosK wrote: post #30

mholt wrote: post #28

Earlier quoted context omitted.

Thanks for your feedback. I'd like to know more. > The fact that the headers aren't seen by most non-technical users is moot. Why's that? (And even among your technical visitors, how many of them actually inspect the response headers?) > I find this practice pretty obnoxious to the point of looking at NGINX Plus for commercial use instead. It's good to know that price isn't the bottleneck, then. Does it make any diff…

> And even among your technical visitors, how many of them actually inspect the response headers? I find that a bit disingenuous. You can't both include annoying headers and argue that they aren't annoying anyone because nobody will see them. If nobody will see them, why add them in the first place?

Post by fortythirteen » Wed, Sep 13, 2017, 2:31 PM UTC

dchest wrote: post #2

Beginning today, all official Caddy binaries come with an End User License Agreement (EULA) that designates them either for Personal (non-commercial) or Commercial use. To be clear, this EULA applies only to Caddy binaries you download; it does not apply to the source code. Caddy is still open source, and the source code is under the same Apache 2.0 license. Thanks for keeping it open source. I'm very interested in h…

Post by rlonstein » Wed, Sep 13, 2017, 2:36 PM UTC

lol768 wrote: post #23

> As of version 0.10.9, Caddy emits an HTTP response header, Caddy-Sponsors, which is similar to the Server header that Caddy already has, except that this one credits our sponsors who make it possible to keep Caddy free for personal use. This header cannot be removed by the Caddyfile, and its presence is required by the non-commercial EULA. This requirement is waived by the commercial license, so the header is not p…

        (a) decompile, disassemble, or otherwise reverse engineer the Software or attempt to reconstruct or discover any source code, underlying ideas, algorithms, file formats or programming interfaces of the Software by any means whatsoever (except and only to the extent that applicable law prohibits or restricts reverse engineering restrictions);

        (b) distribute, sell, sublicense, rent, lease or use the Software for time sharing, hosting, service provider or like purposes, except as expressly permitted under this Agreement;

        (c) redistribute the Software or Modifications other than by including the Software or a portion thereof within your own product or service, which must have substantially different functionality than the Software or Modifications and must not allow any third party to use the Software or Modifications, or any portions thereof, without a proper license to account for its use;

        (d) redistribute the Software as part of an "appliance", "consumer device", or "virtual server";

        (e) redistribute the Software on or to any machine which is not directly under your control or management;

        (f) remove any product identification, proprietary, copyright, or other notices contained in the Software;

        (g) modify any part of the Software, create a derivative work of any part of the Software (except as permitted in Section 4), or incorporate the Software, except to the extent expressly authorized in writing by the Company;

        (h) publicly disseminate performance information or analysis (including, without limitation, benchmarks) from any source relating to the Software;

        (i) utilize any equipment, device, software, or other means designed to circumvent or remove any form of copy protection in place by the Company in connection with the Software;

        (j) use the Software to develop a product which is similar to or competitive with any of the Company's product or service offerings;

        (k) share, distribute, or publish authorization codes, URLs, keys, or any other data provided by the Company that is intended exclusively for your account and not others, otherwise the Company reserves the right to terminate your Subscription without notice;
        (l) violate the Terms of Service as posted on the Company's website;
        {{- if eq .Type "personal"}}

        (m) use or distribute the Software commercially, including to, for, or within a company or for business purposes;

        (n) use or distribute the Software as any part of a formal or informal profitable venture, or as part of a product or service being sold either directly or indirectly;

        (o) block, hide, obscure, modify, or remove the promotional header field named "Caddy-Sponsors" (and any case variants) from HTTP responses;
        {{- end}}