Login buttons you can add.
Each provider works two ways: with our managed client, so there is nothing to register, or with your own client, where you register one redirect URI with the provider and keep the secret in your app. Adding a provider is one module; ask for one you miss.
Login buttons you can add.
Amazon
Sign in with an Amazon account (Login with Amazon). Amazon returns no ID token: your service exchanges the code and reads the profile from the Amazon API. Use the MyLogin.world client with nothing to register, or your own security profile.
Apple
Sign in with Apple. Apple signs a nonce-bound ID token, so the sign-in cannot be replayed. Apple requires a paid developer account and a client secret signed per team, so the credentials are always your own — there is no managed option. Users may hide their real address behind an Apple private relay.
Discord
Sign in with a Discord account. Discord returns no ID token: your service exchanges the code and reads the profile from the Discord API. Use the MyLogin.world client with nothing to register, or your own Discord application.
GitHub
Sign in with a GitHub account. GitHub returns no ID token: your service exchanges the code and reads the profile, plus the verified primary email, from the GitHub API. Use the MyLogin.world client with nothing to register, or your own OAuth app.
GitLab
Sign in with GitLab — gitlab.com or your own self-hosted instance. GitLab signs a nonce-bound ID token your service verifies. Use the MyLogin.world client for gitlab.com with nothing to register, or your own application.
Sign in with a Google account. Google signs an ID token bound to the nonce your service generates, so the sign-in cannot be replayed — your service verifies it. Use the MyLogin.world client with nothing to register, or your own Google Cloud OAuth client.
Microsoft
Sign in with a Microsoft work, school or personal account. Microsoft signs a nonce-bound ID token your service verifies. Microsoft requires your own app registration, so the credentials are always yours — there is no managed option.
OpenID Connect
Connect any standards-compliant OpenID Connect identity provider — Authentik, Keycloak, Authelia, Okta, Auth0, Zitadel and others. Your service discovers the endpoints from its own issuer and verifies the ID token against the published keys; MyLogin.world only supplies the redirect URI.
ORCID
Sign in with an ORCID iD — the persistent identifier used by researchers. ORCID signs a nonce-bound ID token whose subject is the ORCID iD itself. ORCID issues credentials per organisation, so they are always your own — there is no managed option. Most ORCID records keep the email address private, so sign-ins usually arrive without one.
Slack
Sign in with Slack. Slack signs a nonce-bound ID token containing the member’s verified work email, which your service verifies. Use the MyLogin.world client with nothing to register, or your own Slack app.
Twitch
Sign in with a Twitch account. Twitch signs a nonce-bound ID token your service verifies. Use the MyLogin.world client with nothing to register, or your own Twitch application.
Passkeys
Face ID, Touch ID, Windows Hello, or a security key. The ceremony runs on your service address; your app stores the public keys and verifies the signature.
Provider names and logos belong to their owners and do not imply endorsement. Where a provider limits eligibility, the card says so.
Give your app real login buttons.
All features are totally free. Want to help us out? Supporter is $5 a year, less than a frappuccino.