shred45

I want to get feedback on a project I've been working on to reduce the boilerplate involved in "productizing" a site. Over the past few years I've built a number of small tools or sites that I wanted to try to monetize, and each time I found that, despite their excellent APIs and documentation, integrating with auth and payment providers can take several days (or weekends in my case). This can have a big chilling effect and certainly distracts me from improving the actual product.

There is prior art in this space, in particular the fantastic OAuth2-Proxy [1] which is a self-hosted solution for handling authentication boilerplate. OAuth2-Proxy forwards user identity to your service using request headers. This is a great tool, but is self-hosted and difficult to pair with PaaS platforms. Furthermore, I was interested in a similar solution for billing which would handle all the related redirects and webhooks.

With this in mind, I developed NoScription which improves on OAuth2-Proxy in two ways. First, it is hosted for you using Cloudflare Workers, meaning that it supports PaaS, is highly scalable, and introduces minimal network latency. Second, it integrates easily with Stripe using Stripe Connect, allowing you to restrict pages to paid visitors and see their subscription status in request headers.

I currently support Auth0 for authentication and Stripe for billing. In both cases the user brings their own accounts, maintains ownership of their user and customer data, and manages most of the configuration through these providers.

Thanks for checking it out, and let me know if you have any questions! https://noscription.com

[1] https://github.com/oauth2-proxy/oauth2-proxy