explaingit

teamhanko/hanko

★ 8,925GoAudience · developerComplexity · 3/5LicenseSetup · moderate

TLDR

An open-source login and account management system you can host yourself or use as a managed cloud service. Supports passkeys, passwords, email codes, Google and Apple logins, and enterprise SSO, a self-hostable alternative to Auth0 or Clerk.

Mindmap

mindmap
  root((Hanko))
    Auth methods
      Passkeys
      Passwords
      Email OTP
      Social logins
    Enterprise
      SAML SSO
      Multi-factor auth
    Integration
      Go backend API
      Hanko Elements UI
      JavaScript SDK
    Deployment
      Self-hosted
      Managed cloud
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Add passkey and password login to a web app without building auth from scratch or paying for a managed service.

USE CASE 2

Run Hanko on your own server to keep full control over user data and avoid vendor lock-in.

USE CASE 3

Add Google or Apple social login to your app using Hanko's pre-built web components.

USE CASE 4

Integrate enterprise SAML single sign-on for B2B customers using the Hanko backend API.

Tech stack

GoTypeScriptJavaScriptDocker

Getting it running

Difficulty · moderate Time to first run · 1h+

Requires Docker to run locally, backend is AGPL-3.0 so modifications must be open-sourced if distributed.

Backend is AGPL-3.0, you must open-source modifications if you distribute it. Frontend web components are MIT, use freely with no restrictions.

In plain English

Hanko is an open-source tool for handling user login and account management in web applications. It is an alternative to paid services like Auth0 or Clerk, meaning developers can either run it themselves on their own servers or use the managed cloud version the Hanko team hosts. Either way, the goal is to make adding authentication to an app less painful than building it from scratch. The project supports a wide range of ways for users to prove who they are: traditional passwords, one-time email codes, passkeys (the newer phone-or-fingerprint login method), social logins via Google or Apple or GitHub, and enterprise single sign-on through a standard called SAML. Multi-factor authentication is also supported. The feature table in the README marks most of these as already complete, with a few items like mobile SDKs and an organization and permissions system still in progress. For developers integrating Hanko, the main tools are a backend API written in Go and a set of pre-built web components called Hanko Elements. The web components handle the visual login and profile screens and can be styled with CSS so they fit a product's look. A JavaScript SDK is also available for teams that want to build their own login UI while still talking to the Hanko backend rather than a custom-built one. The repository is organized into a backend folder, a frontend folder containing the web components and SDK, and an examples folder with reference implementations for common frontend frameworks. There is also a quickstart application that can be run locally via Docker to see the full login experience working end to end. The backend and server code are licensed under AGPL-3.0, which means products that modify and distribute it must share their changes. The frontend web components and SDK use the more permissive MIT license. Commercial licensing without the AGPL requirement is available by contacting the team.

Copy-paste prompts

Prompt 1
I want to add Hanko authentication to my React app. Show me how to install Hanko Elements and add a login screen with passkey support.
Prompt 2
Walk me through running Hanko locally with Docker so I can test the full login flow including email one-time codes.
Prompt 3
My app uses Hanko for auth. Show me how to verify the Hanko session token in a Node.js API route.
Prompt 4
I want to add Google social login to my Hanko setup. What configuration do I need in the Hanko backend config file?
Prompt 5
Explain the difference between Hanko's AGPL-3.0 backend license and its MIT frontend license and what that means for my SaaS product.
Open on GitHub → Explain another repo

← teamhanko on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.