Hey IH,
Long time lurker's first post. I am excited to share serverlessip.com, a managed HTTP(for now) reverse proxy that can be used
Developers generally use multiple serverless solutions like AWS Lambda, DigitalOcean apps, Heroku, etc for a project. They dynamically generate a URL and if the service needs to be accessed from a custom domain name, it usually means moving the DNS to them(like route 53). What if you don't want to move your DNS? Free providers like Cloudflare and others provide DDoS protection and many other features.
ServerlessIP was created to solve this problem. When you create a proxy with ServerlessIP, it allocates a dedicated IP(v4). Since it is a reverse proxy, you can point to multiple sources and destination domains using the same proxy. All source domains will automatically be upgraded from HTTP->HTTPS via Let's Encrypt.
http://api.yourdomain.com -> Automatic SSL -> https://api.yourdomain.com -> http://some-random-lambda-url.com
https://yourdomain.com -> Automatic SSL-> https://cloudflare-pages-site.com
Running a SAAS and need to support custom domain feature? Simply create a proxy and add your customers domain as the source and the your customer specific subdomain or path(https://customer-1.saas.com or https://saas.com/customer/1) as the destination. Ask your customer to update the DNS with the IP address. Voila! they can now access your app from their domain. Use the same proxy for multiple customers by adding more sources and destination rules.
We also provide a clean API to integrate with your existing apps.
We are currently in beta. You can request an account at serverlessip.com(on the side pane). Any feedback or thoughts would be appreciated.
@cloudhut tried signing up for beta and the signup page didn't load. Let me know if beta list is still open.
I am so sorry, could you please mail us at support@serverlessip.com. Will add you to the list.
@cloudhut No worries. Just emailed you !
Congrats on the launch! Seems like an interesting and useful service. Do you have any acquisition channels in mind for reaching developers?
One piece of advice I have is to go over and above to demonstrate the stability of your service. It will be a crucial piece of infrastructure to your customers. They will need to know you're stable and will not be the weakest link in their architecture. Consider adding a page about your support and incident response procedures, some more detailed description of how it works and the redundancies in place. And perhaps a status page to show your consistent uptime.
Thank you for the kind words. I just started with IH, next in Reddit and then to ProductHunt. The status page is a great idea, I am a strong believer in dogfooding, the actual API and status page are hosted in different locations and are proxied through the platform, the status page can be now found at https://status.serverlessip.com