nowfound

Alternatives

Products that do what I rewrote my 2012 self-signed cert generator in Go – cert-depot.com does

Back in 2012 I built https://cert-depot.com as a weekend project. Node.js + Express + jQuery, shelling out to OpenSSL for certificate generation. It worked but I eventually let it rot. https://news.ycombinator.com/item?id=4766743 Rewrote it from scratch in Go. The entire thing is a single binary with no external dependencies: 1. Certificate generation uses Go's crypto/x509 (no OpenSSL) 2. Certificates are generated in memory and streamed directly — nothing is stored on the server 3. RSA 2048/4096 and ECDSA P-256/P-384 4. Subject Alternative Names…

  1. 1IM
  2. 2MV
  3. 3
    TinyCert237

    Free SSL certificates for your startup.

    2014

  4. 4

    A pain-free service to add SSL to your site, for non-geeks

    2018

  5. 5

    Create and share beautiful certificates in 1 click for free

    2022

  6. 6GS

    2014 · indutny.github.io

  7. 7CS
  8. 8MS
  9. 9AR

    From the cryptic terminal commands to the innumerable ways to shoot yourself in the foot, I always struggled to use TLS certificates. I love how much easier (and cheaper) Let's Encrypt made it to get certificates, but there are still plenty of things to struggle with. That's why we built Relay: a free, browser-based tool that streamlines the ACME workflow, especially for tricky setups like homelabs. Relay acts as a secure intermediary between your ACME client and public certificate authorities like Let's Encrypt. Some ways Relay provides a better experience: - really fast, streamlined…

    2025 · anchor.dev

  10. 10IB

    I built a DNS resolver that lets me use https://frontend.numa instead of localhost:5173 — auto-generated TLS certs, WebSocket passthrough, path routing. No mkcert, no nginx, no /etc/hosts.

    Apr 2026 · github.com

  11. 11CA
  12. 12CC
  13. 13TC
  14. 14

    Create your NFT art online without any coding

    2022

  15. 15IO

    Hi HN, I'm Mohammed, a technical founder who loves shipping and giving back to the community. I'm open-sourcing the full-stack engine that powers my B2B product, apflow.co. What it is: A production B2B starter with a Go backend and Next.js frontend. Both are fully Dockerized with separate containers. No Vercel. No Supabase. Deploy the whole thing on a $6 VPS, or split frontend and backend across different providers. You own the infrastructure. The problem I was solving: Every SaaS starter I evaluated had the same issue: they locked me into someone else's platform. Vercel for hosting.…

    Dec 2025 · github.com

  16. 16

    Design & deliver verifiable certificates

    2022

  17. 17LS

    TLDR, Let's Seal gives the finger to Adobe and every doc signing tool (docusign, google, etc) who pay to play with the Adobe Approved Trust List and then charge you for something that should be free. Currently even the person checking if a document/contract is sealed or code is authentic has to also be inside the same Adobe walled garden too. Verification, the part that should be free is the part everyone charges for. Thats the shape Let's Encrypt fixed for TLS, and I wanted the same thing for documents and files. The core idea therefore needed to go a bit beyond e signatures and i…

    Jul 2026 · github.com

  18. 18SC
  19. 19FA
  20. 20CM
  21. 21LS
  22. 22SM

    Hi, HN! I recently published SelfCertForge, an open source desktop app for creating and managing self-signed certificates on macOS and Windows: https://github.com/rbonestell/SelfCertForge/ I know, I know... this isn't an earth-shattering invention. This came from a place of years of personal annoyance. I’ve been maintaining scripts that wrapped OpenSSL for local certificate workflows: create a long-lived root cert, add it to the trust store, then generate and sign child certificates for local services. The scripts work but the workflow was clunky. Used infrequently…

    May 2026 · github.com

  23. 23WF

    If you're developing locally and need to use HTTPS for whatever, then this tool is hopefully useful to you. I made it because there's a lot of bad info online about generating self-signed certificates. For instance, a lot of guides don't use the SAN list extension or show you how to create a proper certificate chain. Firefox doesn't allow a CA certificate to be used as an end certificate. Getting a working certificate can get pretty confusing, especially for newcomers to certificates or webdev. Having a website for this also means the process of getting a certificate is the same, no matter…

    2024 · dexter.xn--dpping-wxa.eu

  24. 24

    CSR generation API for developers. One curl, no OpenSSL.

    22d ago · csr.plus

Ranked by how close each launch is in meaning, then by votes. Refine with a description →