Add “Sign in with logi” like you'd add Apple or Google — your users get a real approval app (iOS & Android, already live), and your AI coding agent wires the whole thing in from our docs. Tap-to-approve, passkey-backed. You barely touch the code.
We sent a request to your logi app
Welcome back, Alex
Most dev-auth platforms hand you libraries and a hosted web page; a branded push-approval app is a paid add-on or something you build. logi includes the consumer approval app in the standard flow.
Not an SMS code, not a hosted webpage — a native iOS & Android app that shows what they're approving and where. Already on the stores.
Point Claude, Cursor, or Codex at our docs. For supported stacks it drafts the OIDC integration — client, button, redirects, env — and you review the diff. No mobile code for the standard flow.
Out-of-band, bound to the browser session and backed by passkeys (FIDO2) — approvals are designed to resist phishing. Full threat model in the security docs.
Apple and Google buttons don't surface push-approval or account recovery to your app. Dev-auth platforms mostly leave the approval app to you or a paid tier. logi bundles the sign-in and the approval app together.
| Capability | Sign in with Apple / Google | Dev-auth SDKs Auth0 · Clerk · Stytch |
logi |
|---|---|---|---|
| Approval app included for your users | — | paid / limited¹ | ✓ included |
| Tap-to-approve push login | — | paid tier¹ | ✓ |
| Passkey / phishing-resistant sign-in | ✓ | ✓ | ✓ |
| Mobile approval app you build & maintain | none | yours | none |
| Guardian recovery for your app | —² | — | planned |
¹ Auth0 ships its Guardian app on paid MFA tiers; Clerk and Stytch rely on passkeys / OTP rather than a push app. ² Apple and Google offer recovery contacts for their own accounts, not exposed to your app over social login. Accurate as of 2026 — verify before launch.
Tell Claude, Cursor, or Codex: add Sign in with logi. It reads our integration docs and drafts the wiring for supported stacks — you review the diff. Start in sandbox instantly, self-serve.
Rather do it by hand? Point your auth library at the issuer with your client ID and redirect URI — OIDC discovery handles the endpoints. Snippets for Rails, Next.js, Flutter, Swift, Kotlin.
They enroll the logi app once, then approve sign-ins with Face ID. You never shipped a line of mobile code for the standard flow. That's the integration.
// Your agent adds this from our docs — or paste it yourself
providers: [
{
id: "logi",
name: "Sign in with logi",
type: "oidc",
issuer: "https://api.1pass.dev",
clientId: process.env.LOGI_CLIENT_ID,
clientSecret: process.env.LOGI_CLIENT_SECRET,
}
]
// → users approve on their phone. You wrote no mobile code.Start in sandbox, self-serve. Bring your own domain when you're ready for production.