#What it is
Frank is a standalone multi-tenant authentication server, embeddable in a Go backend or hosted on its own, with a Clerk-compatible API surface as the target.
#Three tiers of user
The model that makes it different from most auth servers, and the part that survived into Authsome:
- Internal users: your own staff, running the platform. Full administrative access.
- External users: the developers and admins at a customer organization, managing their own authentication configuration.
- End users: the customer's own users, who never see any of the above.
Most auth systems model two of these and fake the third, which produces an admin panel where your staff and your customers' staff share a permission model that fits neither.
#Why Authsome exists anyway
Frank works, and running it taught me that most teams do not want a second service to operate for authentication. They want it inside the process they already deploy, with their own database and their own migrations. Authsome is that, with the method-as-plugin structure Frank did not have.