Skip to main content
Going live on mainnet requires whitelisting: NEAR Auth issues you dedicated production Auth0 credentials and grants access to the mainnet contracts. This page explains what you get and walks you through the approval process.
Building locally? You can develop against testnet using the values in Resources → Testnet, then come back here when you’re ready to ship on mainnet.

​
What whitelisting grants you

On mainnet, each production app gets its own Auth0 domain, clientId, and signingAudience, plus access to the mainnet NEAR Auth contract at fast-auth.near. This is what the whitelisting process below grants you.
ItemWhat you receive
Auth0 credentialsDedicated production domain, clientId, and signingAudience
Contract accessAccess to the mainnet NEAR Auth contract at fast-auth.near
Deployment guidanceSupport for taking your integration to production

​
Apply for production access

Submit the production access form

Open the application form to request mainnet whitelisting for your app.

​
How the approval process works

Submit your application

Fill out the production access form with details about your app and how you plan to use NEAR Auth. See what to prepare below so you can fill it out in one pass.

Review

The NEAR Auth team reviews your submission and may reach out for additional information about your use case or expected volume.

Approval

Once approved, you receive everything you need to go live:
  • Production Auth0 credentials — your dedicated domain, clientId, and signingAudience (the JWT aud).
  • Access to the mainnet NEAR Auth contract at fast-auth.near.
  • Guidance for production deployment.
Drop your production credentials into your provider config with network: "mainnet" — the rest of your integration stays the same.

​
What to prepare

Have this information ready before you open the form so you can submit in a single pass:
  • Application name and description — what your app does and who it’s for.
  • Expected user volume — a rough estimate of how many users or transactions you anticipate.
  • Use case details — how you intend to use NEAR Auth (login, transaction signing, gasless flows, and so on).
  • Contact information — how the NEAR Auth team can reach you during review.

​
Go live on mainnet

Once you’re whitelisted, point your provider at mainnet using your production credentials.
main.ts
import { JavascriptProvider } from "@fast-auth-near/javascript-provider";

const provider = new JavascriptProvider({
  network: "mainnet",
  clientId: "<your-auth0-client-id>",
  // domain and signingAudience default from the mainnet network,
  // override them only if your production credentials differ.
});
Use the mainnet contract account ids when you construct the client:
client.ts
import { FastAuthClient } from "@fast-auth-near/browser-sdk";

const client = new FastAuthClient(provider, connection, {
  fastAuthContractId: "fast-auth.near",
  mpcContractId: "v1.signer",
});
Production requires your own approved credentials. Only the dedicated clientId, domain, and signing audience you receive from whitelisting will authenticate against the mainnet NEAR Auth contract.

​
Next steps

Networks

Compare testnet and mainnet configuration side by side.

Mainnet resources

Production contract addresses, RPC, and explorer links.

Testnet resources

Shared testnet credentials to keep building right now.

Authenticate users

Wire up login and logout with your provider.