Planting a Flag: My Quest to Build the Ultimate Auth & Billing Solution in Go

This is one of those posts that’s part declaration, part personal reminder, and part manifestation. I’m putting this out into the universe because I’m embarking on an ambitious journey: I plan to write the world's best authentication and billing tools, and I'm going to build them in Go.

Why Go? Because I want these tools to be blazingly fast, incredibly secure, and highly efficient, attributes that Go excels at providing.

Let's talk about the "why" behind this. In the current landscape, while there are many players, I see a persistent gap. For authentication, fantastic services like Auth0, Clerk, Kinde, and libraries like Lucia exist. For billing, we have platforms like Lago and others. They all offer valuable features, but I believe there's a need for something more.

What's missing, in my view, is a solution that is easy to use, exceptionally fast, fully self-hostable (giving you complete control over your data and infrastructure), and seamlessly integrated. That’s the core problem I want to solve.

My vision is to create a unified system where developers can:

• Effortlessly set up and integrate: Think minimal configuration and straightforward SDKs.
• Offer comprehensive authentication options: This means robust support for traditional email/password, alongside social logins via Gmail, GitHub, and other popular OAuth providers.
• Implement flexible and powerful billing: The system will handle various payment gateways like Stripe and PayPal, and yes, even embrace cryptocurrency payments. Billing models will be versatile, catering to monthly subscriptions, hourly rates, usage-based charges, and more.

The ultimate goal? You, the developer, can focus entirely on building your amazing application. When it comes to figuring out how users log in or how you get paid, you simply connect to this system, and the auth and automated billing flows just work. Smoothly, reliably, and securely.

This is more than just a side project. It's a conviction that we can do auth and billing better, make it more developer-friendly, more performant, and more empowering by offering a truly self-hosted, comprehensive option.

So, consider this post my public commitment. It’s a reminder to myself of the mountain I intend to climb and a manifestation of the solution I aim to bring to life. There's a long road ahead, filled with challenges, learning, and a whole lot of Go code. But the vision is clear.

Stay tuned.