Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

overview article of series on keycloak for startups #201

Merged
merged 3 commits into from
Oct 18, 2024
Merged

overview article of series on keycloak for startups #201

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
425b364
overview article of series on keycloak for startups
xgp Oct 17, 2024
7340e84
add some links
pnzrr Oct 17, 2024
40c0ec1
fix link
pnzrr Oct 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions blog/2024-10-18-keycloak-for-startups-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
---
slug: keycloak-for-startups-overview
title: Why your startup should use Keycloak for SSO and User Management
description: Startups are striving for excellence in user experience and security, while simultaneously focusing on their core competencies. That means picking the best tools that expedite their time to market, with as few compromises as possible. Learn why Keycloak excels where commercial solutions fail.
authors: phasetwo
tags: [keycloak, phase_two, startup]
---

In the ever-evolving landscape of Enterprise SaaS, navigating the complexities of identity and access management (IAM) can be a daunting task. As a startup striving for excellence in user experience and security, choosing the right IAM solution is paramount. Enter Keycloak, a powerful open-source IAM tool that not only meets but exceeds the demands of modern startups.

<!--truncate-->

There are a glut of commercial startups that solve some of the core challenges of authentication and authorization. But most of them rely on obscuring their true nature as a _commodity_ as a way of _marketing_ their products as _somehow differentiated_.

The purpose of this series is to dive into the key issues that separate an open source solution like Keycloak from commercial entities like [Auth0](./2024-05-01-alternatives-auth0.md), [Okta](./2024-06-03-alternatives-okta.md), or [WorkOs](./2024-07-22-keycloak-vs-workos.md). This should give a startup engineer or manager ample background to understand the decision, and to cut through the marketing gibberish.

This series will address the following key issues in 4 parts:

1. Every commercial offering is an implementation of the same standards
2. The ability to control your data is essential, now and in the future
3. Extensibility and customization will always be necessary
4. There is no justification for variable cost for individual features

Please stay tuned as we release a new section each week! If you would like to try out Keycloak, [sign-up](/dashboard/) for Phase Two's free tier and test it out now.
Loading