App Store template
Logto icon

Logto

Logto is an open-source identity platform for building sign-in, user management, OIDC/OAuth, SAML, multi-tenancy, and authorization into modern applications.

Launch in your Sealos workspace.

Logto template preview
Template previewFull screenshot
Template deployments
12 on Sealos
Deployment
Your own instance
Category
Tools

About this template

Overview

Logto is an open-source identity platform for modern applications. It provides sign-in and sign-up experiences, user management, OIDC/OAuth 2.0, SAML, multi-tenancy, and authorization from a self-hosted control plane.

From the documentation

Logto exposes two URLs:

How to deploy Logto

  1. Choose Deploy now to start Logto in your Sealos workspace.
  2. Sign in to Sealos and review the template configuration in your workspace.
  3. Launch the template, then inspect the application status and resource cards in Canvas.

Resources to plan for

Start with the resources defined by the Logto template. Review CPU, memory, persistent storage, and network allocations for every service in Canvas. Capacity needs depend on your data and workload; monitor usage as they grow.

Template configuration and setup

Access after deployment

Use the application URL or connection details shown in Canvas. Follow the deployment guide for first-time account setup or client configuration, and keep generated credentials available for that step.

Hosting and billing

Sealos monthly plans include compute, memory, storage, and traffic. Size your plan for all deployed services. Software licenses and external AI or API services may have separate terms and charges. Confirm the applicable plan and optional charges in Cost Center.

Compare Sealos resource plans
Read full documentationCollapse documentation

For current cloud charges, refer to Sealos plan pricing. Upstream documentation may reference earlier billing models.

Deploy and Host Logto on Sealos

Logto is an open-source identity platform for modern applications. It provides sign-in and sign-up experiences, user management, OIDC/OAuth 2.0, SAML, multi-tenancy, and authorization from a self-hosted control plane.

What You Get

  • Logto 1.40.1 running from the fixed svhd/logto:1.40.1 image.
  • A dedicated PostgreSQL database created and initialized by the template.
  • Two public HTTPS endpoints: one for application authentication traffic and one for the Admin Console.
  • Automatic database creation, seed, and alteration deployment during first startup.

Requirements

  • A Sealos account.
  • No external database is required; this template provisions PostgreSQL for you.

Deploy on Sealos

  1. Open the Logto template on Sealos.
  2. Click Deploy Now and keep the generated app name and domain, or customize them before deployment.
  3. Wait until the Logto app and PostgreSQL database are both running.
  4. Open the Admin Console URL shown in the Sealos app details.

First Registration and Login

Logto exposes two URLs:

  • Admin Console: https://${{ defaults.app_host }}-admin.${{ SEALOS_CLOUD_DOMAIN }}
  • Core/Auth endpoint: https://${{ defaults.app_host }}.${{ SEALOS_CLOUD_DOMAIN }}

On the first launch, open the Admin Console URL. The welcome page lets you click Create account to create the initial administrator account with a username and password. The open-source edition allows this initial account creation only once. After the administrator account is created, return to the Admin Console and use Sign in.

Use the Core/Auth endpoint as the issuer and redirect target base when connecting your own applications to Logto through OIDC/OAuth.

Post-Deployment Checklist

  • Create the first administrator account from the Admin Console.
  • Configure your application redirect URIs in Logto.
  • Keep both the Core/Auth endpoint and Admin Console endpoint on HTTPS.
  • Review Logto's official documentation before enabling production identity flows.

References

From launch to everyday operations

Why deploy
on Sealos

A shorter path from an app you want to an app you can run. Sealos brings deployment and ongoing operations into one place.

  1. One-click deployment

    Start with a ready-made template. Review its configuration and launch from the Sealos console.

  2. Managed Kubernetes

    Run on managed infrastructure with built-in workload scheduling and recovery.

  3. Automatic HTTPS

    Give your application a public HTTPS endpoint with certificates managed for you.

  4. Persistent storage

    Keep application data on persistent volumes across container restarts.

  5. Room to grow

    Adjust CPU, memory, and replicas from the console as your workload changes.

One template. Connected resources.

You Get the Whole Stack

Sealos provisions the resources defined by your template and brings them together in your workspace.

  • App Service

    Container workloads with configurable CPU, memory, and replicas.

  • Public HTTPS URL

    An address for your app, with managed TLS certificates.

  • Database

    A database provisioned alongside your app when the template calls for one.

  • Persistent Volume

    Storage for the files and data your application needs to keep.

  • Environment Variables

    Application settings and secrets configured in one place.

  • Logs & Metrics

    Inspect container logs and resource usage from the console.

Resources and their configuration vary by template. Review the deployment form for this app’s exact setup.

Explore more production-ready templates.

More