Authentication

Managed authentication for your apps

Deploy managed Logto instances with one click. OIDC-compliant auth, social login, admin console, and JWT tokens -- all on your own server.

Get Started Documentation

Integrate in minutes with the Logto SDK

import LogtoClient from '@logto/browser';
const logto = new LogtoClient({
endpoint: 'https://my-auth.sh0.app',
appId: 'your-app-id',
});
// Sign in with one line
await logto.signIn('https://myapp.com/callback');
// Get the authenticated user
const user = await logto.getIdTokenClaims();

Everything you need for authentication

Logto handles the complexity of auth so you can focus on your product.

Email/Password + Social Login

Built-in email/password authentication. Add Google, GitHub, Discord, and other social connectors with a few clicks in the Logto admin console.

JWT Tokens

Standards-compliant OIDC tokens. Access tokens, refresh tokens, and ID tokens. Works with any framework or library that supports JWT verification.

Admin Console

Full-featured Logto admin console for managing users, applications, connectors, and sign-in experience. No code needed for configuration.

Connects to Your PostgreSQL

Each auth instance connects to a PostgreSQL database server managed by sh0. Your user data stays on your server, never on a third party.

Auto-SSL Domain

Each auth instance gets its own subdomain with automatic HTTPS. Configure custom domains for a branded sign-in experience.

Multi-Factor Authentication

Enable TOTP-based MFA for your users directly from the admin console. Backup codes included for account recovery.

How It Works

01

Create Auth Instance

Click "Create Auth Server" in the sh0 dashboard. Choose a name and the PostgreSQL server to connect to.

02

Configure Sign-In

Access the Logto admin console. Set up sign-in methods, social connectors, branding, and user roles.

03

Integrate Your App

Install the Logto SDK for your framework. Add the sign-in button and callback handler. Done.

04

Secure Your Routes

Verify JWT tokens in your API or use PostgREST with RLS. Users are authenticated end-to-end.

Authentication Flow

User Sign-In
Logto (OIDC)
JWT Token
Your App / API
PostgreSQL (RLS)

Standard OIDC flow. Tokens verified at every layer.

Third-Party Auth Services

  • x User data stored on someone else's servers
  • x Per-MAU pricing that scales unpredictably
  • x Vendor lock-in with proprietary SDKs
  • x Limited customization of sign-in experience
  • x Compliance complexity with data residency
  • x Outages affect all your users

sh0 + Logto

  • Data stays on your PostgreSQL server
  • Flat pricing, unlimited users
  • Open-source, OIDC-compliant, portable
  • Full control over branding and UX
  • Your server, your jurisdiction
  • Isolated instance, no shared failures

Frequently Asked Questions

What is Logto? +
Logto is an open-source, OIDC-compliant authentication platform. sh0 deploys and manages Logto instances for you, connected to your own PostgreSQL database.
Can I use it with PostgREST? +
Yes. Logto issues standard JWTs that PostgREST can verify. Combined with PostgreSQL RLS policies, you get end-to-end auth from sign-in to database query.
Which social login providers are supported? +
Google, GitHub, Apple, Discord, Facebook, Microsoft, and many more. Logto supports any OAuth 2.0 / OIDC provider via custom connectors.
Where is my user data stored? +
On your PostgreSQL server. sh0 connects Logto to a database you control. No data leaves your infrastructure.
Can I migrate from Auth0 / Firebase Auth? +
Yes. Logto supports user import. Export your users from your current provider and import them into your Logto instance.
How much resources does it use? +
A Logto instance uses approximately 256 MB of memory. It runs as a lightweight container alongside your other services.

Stop paying per user for auth

Deploy Logto on your own server. Full auth, full control, flat pricing.

Get Started Read the Docs