←back to thread

282 points bundie | 2 comments | | HN request time: 0.239s | source
Show context
exiguus ◴[] No.44382638[source]
If i get it correctly, it solves the problem, to store data on MVP/Prototype Auth providers like Superbase, Auth0 or Firebase.

How does it compare to something mature like keycloak?

And what is the difference to just self-host superbase?

replies(1): >>44383160 #
Spivak ◴[] No.44383160[source]
The killer feature is that it's embeddable into your app. You don't have to host anything besides your app and your app's database.

I can't understand why people who aren't Google scale do it any other way. When you're at the point where you need a separate auth service I'd call that good problems to have.

replies(3): >>44383741 #>>44385837 #>>44389066 #
1. koakuma-chan ◴[] No.44383741[source]
> The killer feature is that it's embeddable into your app. You don't have to host anything besides your app and your app's database.

That's why they're gonna monetize by building a cloud service?

replies(1): >>44383930 #
2. Spivak ◴[] No.44383930[source]
I mean right now it's JS's devise. There's always time in the future for them to ruin it.