Loading page
Loading page

Security · Auth0 alternative
Add sign-up, login, social sign-in and roles to your app with an auth server that uses your own database.
Authorizer is an open-source authentication and authorization server. Your app sends users to it to sign up and sign in, and it gives back tokens your app can trust. It handles the dull but critical parts: password storage, sessions, email verification, password reset and multi-factor login.
It also supports social logins, magic links, and OAuth2 and OIDC, so other apps can use it as an identity provider. Roles let you control what each user may do. Webhooks tell your systems when users sign up or log in.
Authorizer is for developers building their own apps who do not want to write auth from scratch. It suits startups and side projects that want features like social login and magic links but prefer to keep user data in their own database.
Hosted auth services often charge by monthly active users, so cost climbs as you grow. They also hold your user table. A self-hosted Authorizer stores users in your own Postgres database, and you can move or query that data whenever you want.
The trade-off: auth is security critical. Keep ADMIN_SECRET and JWT_SECRET private and strong. You look after updates, especially security fixes, and backups of the database. This template uses version 1.4.4, while the project has moved to v2 with a different config style, so plan any upgrade with care.
Containers: lakhansamani/authorizer:1.4.4, postgres:15-alpine, redis:7-alpine
Step 1
Choose the Starter plan. It costs $20 a month and runs up to 3 apps.
Step 2
Open App templates in the dashboard, choose Authorizer, and click Deploy. We set up the containers, secrets and domain.
Step 3
Wait a few minutes for the first deploy, then open your new URL and finish the Authorizer setup screen.