Hi HN! I'm Ben, co-founder of Anchor (
https://anchor.dev/). Anchor is a hosted service for ACME powered internal X.509 CAs. We recently launched our features & tooling for local development. The goal is to make it easy and toil-free to develop locally with HTTPS, and also provide dev/prod parity for TLS/HTTPS encryption.
You can add Anchor to your development workflow in minutes. Here's how:
- https://blog.anchor.dev/getting-started-with-anchor-for-loca...
- https://blog.anchor.dev/service-to-service-tls-in-developmen...
We started Anchor because private CAs were a constant source of frustration throughout our careers. Avoiding them makes it all the more painful when you're finally forced to use one. The release of ACME and Let's Encrypt was a big step forward in certificate provisioning, but the improvements have been almost entirely in the WebPKI and public CA space. Internal TLS is still as unpleasant & painful to use as it has been for the past 20 years. So we've built Anchor to be a developer-friendly way to setup internal TLS that fully leverages the benefits of ACME:
- no encryption experience or X.509 knowledge required
- automatically generated system and language packages to manage client trust stores
- ACME (RFC 8555) compliant API, broad language/tooling support for cert provisioning
- fully hosted, no services or infra requirements
- works the same in all deployment environments, including development
If you're interested in more specific details and strategy, our blog posts cover all this and more: https://blog.anchor.dev/
We are asking for feedback on our features for local development, and would like to hear your thoughts & questions. Many thanks!
You can add Anchor to your development workflow in minutes. Here's how:
- https://blog.anchor.dev/getting-started-with-anchor-for-loca...
- https://blog.anchor.dev/service-to-service-tls-in-developmen...
We started Anchor because private CAs were a constant source of frustration throughout our careers. Avoiding them makes it all the more painful when you're finally forced to use one. The release of ACME and Let's Encrypt was a big step forward in certificate provisioning, but the improvements have been almost entirely in the WebPKI and public CA space. Internal TLS is still as unpleasant & painful to use as it has been for the past 20 years. So we've built Anchor to be a developer-friendly way to setup internal TLS that fully leverages the benefits of ACME:
- no encryption experience or X.509 knowledge required
- automatically generated system and language packages to manage client trust stores
- ACME (RFC 8555) compliant API, broad language/tooling support for cert provisioning
- fully hosted, no services or infra requirements
- works the same in all deployment environments, including development
If you're interested in more specific details and strategy, our blog posts cover all this and more: https://blog.anchor.dev/
We are asking for feedback on our features for local development, and would like to hear your thoughts & questions. Many thanks!