Title: We launched an API for custom hostnames today. A simple HTTP post with a hostname gets a temp hostname with CNAME&#x2F;a record instructions, as soon as DNS is setup we issue SSL and start accepting traffic for that hostname. It&#x27;s the quickest way we know of to provision custom hostnames: <a href="https:&#x2F;&#x2F;fly.io&#x2F;mix&#x2F;custom-hostnames&#x2F;" rel="nofollow">https:&#x2F;&#x2F;fly.io&#x2F;mix&#x2F;custom-hostnames&#x2F;</a><p>When we started building Fly, we figured it was too late to &quot;make SSL easy and the customers will come&quot;. Lets Encrypt changed the world, and we knew many companies rolling their own SSL support with nginx, Traefik, etc, etc. It seemed like a solved problem.<p>It turns out that SSL is still a pain, particularly companies with lots of hostnames pointed at them ... anyone hosting apps&#x2F;content on behalf of their own customers. Distributing certificates, keeping them renewed, and — most of all‚ making https fast is still hard. Devs can solve the basic problem in a week or so with a proxy, but then it sits, and no one feels very comfy with untouched infrastructure. And it&#x27;s usually something distracting devs from more important work that&#x27;s core to their own customers.<p>So this is our way of solving that problem. We can handle any number of hostnames for applications, devs can spend more timeon what makes their apps special. It&#x27;s a relatively &quot;simple&quot; use of what we&#x27;ve built, but solves a really fundamental problem for a many companies. It&#x27;s the most fun thing we&#x27;ve discovered this year.<p>So, if you&#x27;re building an app, and serve stuff on behalf of your users, we can make your life easier:<p><a href="https:&#x2F;&#x2F;fly.io&#x2F;mix&#x2F;custom-hostnames&#x2F;" rel="nofollow">https:&#x2F;&#x2F;fly.io&#x2F;mix&#x2F;custom-hostnames&#x2F;</a>
Upvote: