3 ms·
Disclosure: I work for FusionAuth. Auth0 has done a lot of great work educating devs on the value of a standalone auth server, but the Okta acquisition has cau
by mooreds 4y ago
Disclosure: I work for FusionAuth.
Auth0 has done a lot of great work educating devs on the value of a standalone auth server, but the Okta acquisition has caused some sales tactics that ... aren't great.
In my mind, you have four options for auth, whether it is for customers or employees[0]:
* no auth (brochure website)
* roll your own (please don't)
* use a library or framework (if you have one app)
* standalone auth server (if you have more than one application or more complex needs)
If you are looking at a standalone auth server option, there are a few dimensions to consider:
* license
* self-host vs saas
* pricing
* features
* support
* funding taken
Lots of options out there and more every day (hence this tweet[1] which is haha only serious)
Our VP of sales wrote an overview of the customer auth market as he sees it[2].
I have opinions, but of course where I stand is affected by where I sit[3]. But I think that devs should definitely evaluate options.
0: https://fusionauth.io/learn/expert-advice/ciam/ciam-vs-iam https://fusionauth.io/learn/expert-advice/ciam/ciam-vs-iam has more
1: https://twitter.com/thdxr/status/1651369228371361792 https://twitter.com/thdxr/status/1651369228371361792
2: https://fusionauth.io/blog/2023/03/15/winning-customer-auth-market https://fusionauth.io/blog/2023/03/15/winning-customer-auth-...
3: Miles' Law: https://www.jstor.org/stable/975497?seq=1#page_scan_tab_contents https://www.jstor.org/stable/975497?seq=1#page_scan_tab_cont...
Edit, fixed url reference.