Login Broker

Free to 100k MAU is generous for hosted social login — most providers start metering way earlier. One script tag + one key across six providers also removes the usual pain of juggling separate OAuth app configs per provider. Does switching providers later (say, adding a seventh) require re-issuing the key, or is it additive?

Really loved the app.

You can a Free version.

good app, keep going

Amazing generosity on the free tier, genuinely useful tool for building products

One script tag covering six providers and free up to 100,000 MAU makes this attractive for side projects. Since it is hosted, what happens to existing sessions and user IDs if a developer later wants to migrate off Login Broker, is there an export of linked provider accounts? Clear docs on data retention and a self-host or export path would make it much easier to trust for production apps.

Any one can not thinks that much ,this has ease the work very quickly

One script tag and one key for six providers is a clear pitch. What happens to the user records if a developer later wants to leave: is there an export of the user list and provider IDs? And what is the plan once an app passes the 100,000 MAU free tier?

Free up to 100k MAU covers most side projects for good. How do you handle a user who signs up with Google and later tries GitHub with the same email: are the two linked into one account, or kept separate?

Love the free tier, would add more guardrails to prevent abuse though

Covering six social providers with one script tag and one API key saves the usual chore of setting up a separate OAuth app for each one. Anyone running a small team on a tight AI budget might like what PZERO does at pzero.studio.

The one-script-tag approach looks like a useful way to keep social login simple for developers. Supporting six providers while keeping the integration lightweight is a strong selling point. How much configuration is needed when adding or switching between providers?

Free to 100,000 MAU is the headline for me — most hosted auth providers start charging way before that, which makes early founders treat login like a cost center from day one. The question I'd ask before committing: does the script tag support popup-based login as well as the full redirect flow? In a single-page app, a popup keeps the user's place, while a redirect loses in-progress state — having both modes would cover most real use cases. Also worth knowing for anyone evaluating: is there an export path for user identities if you ever decide to self-host later?

One API key covering six social providers removes the usual chore of registering OAuth apps and juggling redirect URIs for small teams. Worth documenting how account linking behaves when the same person signs in with Google one day and GitHub the next — that identity-merging edge case is what tends to bite teams later.