Clerks go sdk assumes that you will be using it as a API not a fullstack framework -> so if you will be using go as an API clerk is great... if not... holy moly is it annoying -> I had to do some funky hackery with the JS front SDK with a manual reload and backend cookies to get it working... I wouldn't say it is ideal... but it works... The reason I am (for the time being) willing to put up with this is because everything you get with clerk for a pretty low cost (if your app is making money) is well worth it in my opinion.

I did think about potentially rolling my own auth -> But the pros are outweighed by the cons (as of right now)

If I did roll my own -> I might look into running through a library in the Elixir Ecosystem and then do api calls from the main server side rendered app.

Auth0 is incredibly expensive and very very corporate (I would look at workOS if you are at that level)

As for firebase (which does have a admin sdk for go) -> the documentation was incredibly fragmented -> And on server rendered apps did not seem as secure over clerk, as a lot of things had to be implemented manually.