certera's comments

Why not run ES on the bare metal servers?

Tell us more about your startup. There are always people here interested in what others are doing.

Ya, but what kind of battery?

Are you looking to start a business? SaaS, consultancy, etc.?

Shameless plug for Certera for these more complex scenarios: https://docs.certera.io

I found that the certs behind a load balancer were enough of a problem that a solution was needed.

I found this to be a problem too and created Certera (shameless plug). It helps simplify a lot of things and fixes some of the pain points of the typical ACME clients.

https://docs.certera.io

I completely agree. I went this route with my recent project and it was very refreshing.

Ah, apologies, I should have been able to figure that out. As it stands, it currently only stores on the machine where the app runs.

I have put thought into storing it into something like an HSM as I think that would only raise the confidence, trust and security of Certera. I have that written down as something to pursue in future versions!

The certera web app will run on Windows and Linux. It can also be made to work for mac, but it's not yet compiled for that.

Hi HN!

Certera is a central validation server for Let's Encrypt certificates. It's a cross platform, self-hosted web application. With Certera, you can centralize all of your LE certificates and keys, monitor certificates and receive notifications for cert changes and expirations. It will also help you stay within LE quota limits. Check out the docs for more details and screenshots. It's currently in beta as I'm looking for folks to start using and provide some feedback.

I created this because I had been using various ACME clients and occasionally a change here and there could cause things to break. Or, a cert would be on a system that I didn't know about and the cert would expire without anyone knowing about it. The biggest driver was making it simpler to use LE certs behind load balancers since Certera separates acquiring certificates and applying them. The idea is that you use Certera to acquire certificates, then use the API provided to retrieve the certs and keys to apply them. Currently, it only works with HTTP-01 validation (and redirects). I'm planning on adding DNS-01 validation and some hooks to make certificate automation much better when it comes to client certificates (i.e. rotating SSO certificates or certificates used for securing endpoints).

https://certera.io (landing page) https://docs.certera.io (docs) https://github.com/certera-io/certera (code)

I struggled a lot with the licensing and settled on something that's not "open source"; it's source available. It is free for personal use, nonprofits and small organizations (< $1M in revenue). It's free for all during the beta. 10% of all revenue will be shared back to projects used to build Certera, the breakdown is in the docs.

Some principles I've tried to follow while building this: - Perpetual license only. I'm kind of burned out with subscriptions. - The least amount of Javascript I could get away with. There are no frameworks. All in all, less than 10 lines of plain vanilla JS.

Thanks for reading and let me know what you think!

Why do you want more users? Are you wanting to build your own recognition in the UX space?

I hope I don't sound snarky. I just want to better understand your thoughts and motives.

What's your intention here? Just want to get more users, looking for help, trying to make money, etc.

Saw this from the early adopter thread. Looks really well build.

How much time dedicated over the decade+?

What are your thoughts on how well these kinds of tools generate html? Brings me back to Dreamweaver.

If it dies, there can be a point where the maintainer can re-license under more open terms, no? Until that point, the work and contributions are ensured to help sustain the creator.

I'm planning on releasing my project under similar terms. I'm not particularly interested in community contributions, but rather for there to be trust in ensuring privacy and security. Sometimes, there isn't a one-size-fits-all with the available OSI licenses and I appreciate what op has done to do his best to find what works well for him and the community.

I'm not sure sure it will go "badly". I believe there's a fundamental issue with a class of software applications that the current OSI licenses don't do much for. Let me clarify that statement with some examples. If you're a developer of an "open source" library or database engine, you have great OSI licenses available to use. The consumers of your work will either open source their work or purchase a license (i.e. dual-licensing). If, however, you're creating a CMS or some standalone tool (like GIMP, for example), you're left to go down the road of open core (typically). So, the alternative here is to choose a license that's conducive of being able to monetize without depending on donations or support contracts.

I think developers should pick a license that makes sense for them, not necessarily for the benefit of others. What is important though, is that some thought is taken and to try it out. You can always go more permissive later.

I'm working on something that I want to monetize, but the OSI licenses aren't helpful for the kind of application I'm working on. I'm leaning towards a similar licensing structure and have been spending a great deal of time thinking about this and I hope to have more discussions on this very topic as it's extremely helpful for everyone.

edit: typos

I love how you licensed it. I'm seeing a trend in how developers are being thoughtful about the licensing and how it will help monetize their efforts later. Excited to see how this goes.

I really enjoyed this article. It's still as applicable today as when it was written. Not everything needs to be a SaaS.

I agree. I'm developing something, and while a subscription is attractive to me, I feel it's not correctly aligned to what users deserve.

I'm burned out by all of these subscriptions and trying to go back to my "roots".