Every combination uses the same Auth0 login flow and the same on-chain contracts — the SDK shapes the developer API, and the provider adapts the login to your platform.
Choose your SDK
The SDK gives you theFastAuthClient for logging users in and the FastAuthSigner for requesting signatures. Pick the one that matches your frontend framework.
| SDK | Package | Use case |
|---|---|---|
| Browser SDK | @fast-auth-near/browser-sdk | Vanilla JavaScript, TypeScript, Vue, Svelte, Angular, or any web framework |
| React SDK | @fast-auth-near/react-sdk | React applications that want hooks and context providers |
Browser SDK
The Browser SDK provides a framework-agnostic, class-basedFastAuthClient that works in any JavaScript app. Reach for it when:
- You’re building with vanilla JavaScript, TypeScript, Vue, Svelte, or Angular.
- You want full control over the authentication and signing flow.
- You prefer an imperative, class-based API over hooks.
FastAuthClient yourself, call login(), and pull a FastAuthSigner out of it with getSigner().
React SDK
The React SDK wraps the Browser SDK with React-idiomatic ergonomics: aFastAuthProvider you mount at the root of your app, plus hooks like useFastAuth(), useIsLoggedIn(), usePublicKey(), and useSigner(). Reach for it when:
- You’re building a React application.
- You want declarative, hook-based state for the client, login status, and signer.
- You’d rather not wire up the client lifecycle by hand.
signAndSendTransaction(...) and signAndSendDelegateAction(...) on top of the core signing methods.
Choose your provider
Providers are platform-specific adapters that run the actual login with Auth0. They abstract away the differences between web browsers and native mobile so the SDK stays the same. Pick the one that matches where your app runs.| Provider | Package | Platform |
|---|---|---|
| JavaScript provider | @fast-auth-near/javascript-provider | Web browsers |
| React Native provider | @fast-auth-near/react-native-provider | iOS and Android apps |
JavaScript provider
JavascriptProvider is designed for web browsers and works with either the Browser SDK or the React SDK. It handles the Auth0 OAuth flow — via popup or redirect — and token management on the web.
React Native provider
ReactNativeProvider is designed for iOS and Android apps. It uses native authentication flows and secure credential storage, backed by react-native-auth0.
How SDKs and providers combine
Your dApp talks to an SDK (FastAuthClient / FastAuthSigner), which delegates the login to a provider (the Auth0 adapter for your platform). The provider talks to Auth0; the SDK talks to the NEAR Auth contracts.
| Your app | SDK | Provider |
|---|---|---|
| React on the web | @fast-auth-near/react-sdk | @fast-auth-near/javascript-provider |
| Any other web framework | @fast-auth-near/browser-sdk | @fast-auth-near/javascript-provider |
| React Native mobile | @fast-auth-near/react-sdk | @fast-auth-near/react-native-provider |
The SDK and provider are chosen independently: the SDK follows your framework (React vs. everything else), and the provider follows your platform (web vs. mobile).
Reference each library
React SDK
FastAuthProvider, hooks, and the relayer-aware signer for React apps.Browser SDK
The framework-agnostic
FastAuthClient and FastAuthSigner classes.JavaScript provider
JavascriptProvider — the Auth0 adapter for web browsers.React Native provider
ReactNativeProvider — the Auth0 adapter for iOS and Android.Start the quickstart
Once you’ve picked a pair, wire it up and sign your first transaction in under 5 minutes.