head to head · open source

Logto vs samlify

Logto has 14,599 GitHub stars, 1,212 forks, 183 open issues and last shipped today. samlify has 661 stars, 233 forks, 53 open issues and last shipped 1 months ago. Logto leads on adoption by 2,109% (14,599 vs 661 stars). Logto is written in TypeScript under MPL-2.0; samlify is written in TypeScript under MIT. Logto has attracted 8% as many forks as stars, samlify 35%. Logto was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

Logto ★ 15K samlify ★ 661 category Security & Privacy

← all 20902 open source comparisons

Side by side

Logto samlify
GitHub stars ★ 15K ★ 661
License MPL-2.0 MIT
Written in TypeScript TypeScript
Last push 2026-09-20 2026-08-11
Forks ⑂ 1.2K ⑂ 233
Self-hosting Yes Yes
Data ownership Your server Your server

pick Logto if

  • You weight community size — 15K stars and counting
  • You want the MPL-2.0 license terms
  • Your stack matches TypeScript
  • You value the larger contributor base for long-term maintenance

full Logto profile →

pick samlify if

  • You want the samlify feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches TypeScript
  • You evaluated both and samlify fits your workflow better

full samlify profile →

About Logto

Logto is an open source authentication and authorization infrastructure for SaaS and AI applications. It is written in TypeScript, licensed under MPL 2.0, and positioned as an open alternative to Auth0. The project sits in the identity and access management ecosystem, where it provides a central service for login, consent, tokens, user directories, and access control.

read the full Logto overview →

About samlify

Node.js SAML 2.0 library for Single Sign On, written in TypeScript under the MIT licence, for developers adding SAML SSO to Node.js applications as either a Service Provider or an Identity Provider.

read the full samlify overview →

More in Security & Privacy

PayloadsAllTheThings ★ 81K Puter ★ 44K Mattermost ★ 39K Keycloak ★ 37K Tailscale ★ 37K HashiCorp Vault ★ 36K

Related comparisons

supabase vs better-auth keycloak vs jumpserver keycloak vs better-auth keycloak vs authelia keycloak vs authentik jumpserver vs better-auth jumpserver vs authelia better-auth vs authelia payloadsallthethings vs vault vaultwarden vs vault payloadsallthethings vs unkey payloadsallthethings vs phase payloadsallthethings vs keyshade puter vs vault mattermost vs vault keycloak vs vault payloadsallthethings vs anthropic-cybersecurity-skills payloadsallthethings vs projectdiscovery payloadsallthethings vs pentagi payloadsallthethings vs pentestgpt payloadsallthethings vs osintgram payloadsallthethings vs vuls payloadsallthethings vs osv-scanner payloadsallthethings vs nettacker

More Identity & Access Management (IAM) projects

Compare either of these against the rest of the Identity & Access Management (IAM) field.

Logto vs Keycloak Logto vs JumpServer Logto vs Better Auth Logto vs authelia Logto vs Authentik Logto vs casbin Logto vs Sa-Token Logto vs hydra Logto vs SuperTokens Logto vs Zitadel Logto vs oauth2-proxy Logto vs casdoor

Frequently asked questions

Is Logto or samlify more popular?

Logto has 14,599 GitHub stars and samlify has 661. Logto has the larger community by that measure.

Are Logto and samlify free?

Both are open source. Logto is licensed under MPL-2.0 and samlify under MIT. Neither carries a licence fee.

What is the difference between Logto and samlify?

Logto is written in TypeScript and samlify in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, Logto or samlify?

Choose Logto if you want the larger community (14,599 stars) or its MPL-2.0 licence terms. Choose samlify if its feature set, stack or MIT licence fits better. Both are self-hostable.