Lockspire

Lockspire lets partner apps request access to your APIs with OAuth 2.0 and sign in with OpenID Connect (OIDC), all from your existing Phoenix app. Your app keeps its accounts, login, branding, and product rules; Lockspire handles the protocol and tokens.

Is Lockspire a fit?

Lockspire fits teams that want to connect partner apps without moving user accounts or login into a separate service. Before relying on a feature or deployment shape, check the supported capabilities and limits. That page is the support contract; this README does not repeat its capability list.

Install in your Phoenix app

Follow the canonical install and onboarding guide. It covers the generated host files, migrations, mix lockspire.verify, and the host checks still needed after installation. If the OAuth/OIDC concepts or host responsibilities are new to you, start with OAuth/OIDC for Phoenix adopters.

Choose your next task

• Register a first client: SaaS adoption recipe
• Protect Phoenix API routes: route protection guide
• Set up device login: device flow host guide
• Review the admin pages: admin guide
• Use the local example: adoption demo, which uses synthetic Billingo data
• Maintain a release: maintainer and release guide

Work on the Lockspire repository

For repository ownership, local checks, and contributor workflow, see CONTRIBUTING.md. It applies to this repository and is not part of the Hex package documentation.