The fastest and easiest way to get HTTPS in your local development environment, lcl.host gives you browser trusted HTTPS certificates for your web apps in development. The CLI tool handles all setup & system configuration in seconds, and guides you through application setup instructions based on your language and framework. Supports JavaScript, Next.js, Python, Django, Ruby, Ruby on Rails and Go apps, with more to come.

Hey Hunters! All of us here at Anchor are absolutely stoked to be releasing lcl.host, a new developer tool, to all of you absolutely free! 🚀 lcl.host is the absolute fastest ⚡️ and easiest 😌 way to get HTTPS setup in your development environment 🖥️. Once the Anchor CLI toolchain is installed simply run `anchor lcl` from the root of your application/project/service and we take care of the rest. It is truly that easy, give it a try for yourself. In a terminal run `brew install anchordotdev/tap/anchor` and `anchor lcl` from the root of your project. The toolchain automatically handles the following for you: ✅ Configures your local certificate stores to trust Anchor-provided certificates from your account, and your account only. ✅ Detects the application name and language/server type, then provisions the application's service and resources through Anchor's API. ✅ Provisions a certificate for your app (or service), and writes the certificate and key pair to files in your application directory. You can then use this certificate to manually enable HTTPS/TLS in your development environment. ✅ Adds WebPKI-quality certificates to your filesystem that are specific to your app or service. ✅ Finally, the Anchor Setup Guide shows you a few easy steps to set up and use ACME for future certificate provisioning. So you don’t have to ❌ configure DNS ❌ edit /etc/hosts ❌ run complicated openssl commands ❌ worry about expiring certificates ❌ manage local truststores This is my dev environment, which doesn’t have any sensitive data in it, should I really run HTTPS locally? While dev/prod parity should be enough to want to run HTTPS locally (i.e. you want your browser to run in a truly secure context, always) there are a number of reasons that you might be required to run HTTPS while in development! Mixed Content ⚠️ CORS Errors ⛔️ HTTP/2👩‍💻 Secure Cookies 🍪 OAuth and secure 3rd Party endpoints 🎁 Localhost Apps and Marketplaces 💹 Requirement for tools 🔨 📣 We really appreciate any feedback you have for us. What do you want to see next from the team? 🎉 To celebrate our launch we’ll be giving a special, hand-crafted, gift to a limited number of early adopters!

@victoria_wu Easy as pie ;-)

@stolt45 Nicely done, good job, and can't beat the price! Wish you all the success!

@stolt45 can we connect on likedin

@stolt45 Congrats on the launch, Chris.

@mogabr Thanks, Gabe.

I'll definitely need this in the future. it will help me test webhooks with Stripe and other providers so I can avoid using the Stripe CLI during development!

@kingromstar Thanks, Rami. lcl.host doesn't currently support ingress to your dev environment. But sounds like that'd be something you need?

This is great! There is always a point where this becomes an issue 😅 awesome to have a simple and fast solution. Thanks for this!

@jopie Thanks, Joep 😀 Let us know if you have any feedback or need a hand with anything.

Local HTTPS is horrible to set up. Now I get to ignore it and I'm never going back.

If you work local first & want to be local secure, this = ❤️

Early access and omg where have you been these last few years? No more needing to manage certs for dev stuff. LFG!

Local HTTPS is horrible to set up. Now I get to ignore it and I'm never going back.

If you work local first & want to be local secure, this = ❤️

Early access and omg where have you been these last few years? No more needing to manage certs for dev stuff. LFG!

lcl.host

Get HTTPS in your local dev environment

Get HTTPS in your local dev environment

lcl.host

Get HTTPS in your local dev environment

Get HTTPS in your local dev environment

Similar Products

Do you use lcl.host?

Do you use lcl.host?

You might also like