3 ms·

I like the idea. My startup started with managed hosting. We use to provide subdomains of customer.company.com domain for each customer to quickly onboard users

I like the idea. My startup started with managed hosting. We use to provide subdomains of customer.company.com domain for each customer to quickly onboard users. Later, when the customer was ready to move to their own domain, we had to ask them to setup A records or provide DNS credentials. The tech stack wasn't too hard for us but hand holding each customer to get the custom domain working was the pain point. * Will AutoSSL also provide a way for the customer to login and provide them instructions on how they can setup the domain on their side? * Some of our customers had CAA records preventing LE from working. This is about informing the customer that this record exists and what the possible alternatives are. * This was mentioned elsewhere but AutoSSL is a cPanel feature. So, I would consider rebranding. * What are the proxying limitations? Does it support Websockets? How much load can it handle?

Sandeepg33k 7y ago
Thanks! > Will AutoSSL also provide a way for the customer to login and provide them instructions on how they can set up the domain on their side? Yes, I expose two APIs - add and delete. When your customer adds a domain, you can hit our API to whitelist it. The API responds back with CNAME instructions. Your app just needs to pick it up and display it to the users. > What are the proxying limitations? Does it support Websockets? How much load can it handle? I have 5 servers right now that handle TLS and fetch content from the origin. I just did a load testing with about 20K requests per minute, and it did fine. Will do more tests as I move forward. But before doing anything just wanted to know if anyone is actually going to use the product. :D