# NEAR Auth

## Docs

- [Apply for production access](https://docs.auth.near.org/home/apply.md): Get your app whitelisted for NEAR Auth on mainnet with dedicated production credentials.
- [Authenticate your users](https://docs.auth.near.org/home/guides/authenticate-users.md): Log users in with a Web2 identity, check their session on page load, and log them out — with the React and Browser SDKs.
- [Choose your SDK](https://docs.auth.near.org/home/guides/choose-your-sdk.md): Pick the right NEAR Auth SDK and provider for your stack — React, browser, or mobile.
- [Sign transactions & delegate actions](https://docs.auth.near.org/home/guides/sign-transactions.md): Request MPC signatures for NEAR transactions and gasless delegate actions after a user logs in with NEAR Auth.
- [Quickstart](https://docs.auth.near.org/home/quickstart.md): Go from zero to a signed NEAR transaction on mainnet — install, log in, and sign in a handful of lines.
- [What is NEAR Auth](https://docs.auth.near.org/home/what-is.md): NEAR Auth lets Web2 users sign NEAR transactions with the accounts they already have — no seed phrases, no wallet extensions.
- [NEAR Auth](https://docs.auth.near.org/index.md): Sign NEAR transactions with a Web2 login — no seed phrases, no wallet extensions.
- [Attestation contract](https://docs.auth.near.org/protocol/advanced/attestation.md): Decentralized, quorum-based public-key management that lets guards source their signing keys without trusting a single admin.
- [Custom backend integration](https://docs.auth.near.org/protocol/advanced/custom-backend.md): Run your own off-chain service that participates in the NEAR Auth flow — validating identities and issuing the JWTs a custom guard verifies on-chain.
- [Custom issuer service](https://docs.auth.near.org/protocol/advanced/custom-issuer.md): Run an intermediary JWT issuer that re-signs tokens from Firebase or any OIDC provider so the CustomIssuer Guard can verify them on-chain.
- [Custom Issuer Guard](https://docs.auth.near.org/protocol/advanced/custom-issuer-guard.md): The on-chain guard that verifies JWTs from a custom OIDC issuer using RS256 keys managed by a DAO-governed attestation contract.
- [Auth0 integration](https://docs.auth.near.org/protocol/concepts/auth0.md): How NEAR Auth uses Auth0 as its default identity provider to authenticate users and authorize every transaction.
- [JWT verification](https://docs.auth.near.org/protocol/concepts/jwt.md): How NEAR Auth structures JWTs and verifies their signatures and claims entirely on-chain.
- [MPC signing](https://docs.auth.near.org/protocol/concepts/mpc.md): How NEAR Auth derives per-user keys and produces signatures through a distributed Multi-Party Computation network — no single party ever holds a full private key.
- [Relayer & meta-transactions](https://docs.auth.near.org/protocol/concepts/relayer.md): How a relayer sponsors gas by submitting MPC-signed delegate actions as NEP-366 meta-transactions.
- [Auth0 Guard](https://docs.auth.near.org/protocol/contracts/auth0-guard.md): The NEAR Auth guard contract that verifies Auth0 JWTs on-chain — RS256 signature, issuer, expiry, audience, and the fatxn transaction binding.
- [NEAR Auth contract](https://docs.auth.near.org/protocol/contracts/fast-auth.md): The entry-point contract that routes verification to guards and orchestrates MPC signing on NEAR.
- [JWT Guard Router](https://docs.auth.near.org/protocol/contracts/jwt-guard-router.md): The on-chain registry that maps guard names to guard contracts and routes NEAR Auth verification to the right one.
- [Contracts overview](https://docs.auth.near.org/protocol/contracts/overview.md): The modular on-chain system behind NEAR Auth — entry point, router, guards, and attestation working together to verify JWTs and drive MPC signing.
- [How it works](https://docs.auth.near.org/protocol/how-it-works.md): Follow a NEAR Auth signature end to end — from an Auth0 login to an MPC-produced signature verified on-chain.
- [Protocol overview](https://docs.auth.near.org/protocol/overview.md): The three layers behind NEAR Auth — smart contracts, an MPC signing network, and optional off-chain services.
- [Mainnet contracts](https://docs.auth.near.org/resources/mainnet.md): Deployed NEAR Auth contract addresses and network configuration for NEAR mainnet.
- [Network configuration](https://docs.auth.near.org/resources/networks.md): Every per-network value an integrator sets — NEAR RPC, contract ids, and Auth0 — for mainnet and testnet.
- [Resources](https://docs.auth.near.org/resources/overview.md): Deployed contract addresses and network configuration for NEAR Auth.
- [Testnet contracts](https://docs.auth.near.org/resources/testnet.md): Deployed NEAR Auth contract addresses, network config, and credentials for NEAR testnet.
- [Browser SDK](https://docs.auth.near.org/sdks/browser-sdk.md): Full reference for @fast-auth-near/browser-sdk — the framework-agnostic FastAuthClient, FastAuthSigner, and FastAuthSignature classes.
- [Core Types](https://docs.auth.near.org/sdks/core.md): The shared TypeScript interfaces every NEAR Auth SDK and provider is built on — including IFastAuthProvider, SignatureRequest, and User.
- [JavaScript Provider](https://docs.auth.near.org/sdks/javascript-provider.md): Full reference for the JavascriptProvider — Auth0 login and signature requests for web apps, using popup or redirect flows.
- [SDKs overview](https://docs.auth.near.org/sdks/overview.md): The NEAR Auth library landscape — SDKs, platform providers, and shared core, and how they compose.
- [React Native Provider](https://docs.auth.near.org/sdks/react-native-provider.md): Native mobile Auth0 login and NEAR signature requests for React Native, backed by react-native-auth0.
- [React SDK](https://docs.auth.near.org/sdks/react-sdk.md): Full reference for the NEAR Auth React SDK — the FastAuthProvider, hooks, and the relayer-backed client and signer.