verapli
Sign inJoin free
Menu

Guides · auth · Everyday developer services

Auth0 tenant and application

Sign up for Auth0, create a tenant in a chosen region, create a Regular Web Application, set callback URLs, and copy domain, client ID and secret.

Researched · not yet run liveLast researched 25 October 2026 · Okta (Auth0) · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Who owns what

An Auth0 account can own several tenants (one per environment is recommended); applications live in a tenant.

  • Auth0 account personal owned by the person
  • Tenant project · under Auth0 accountName and region are permanent choices.

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Sign up for Auth0

    The person signs up at auth0.com. verapli never creates the account.

    • Guided by hand
    • Human step: You press submit

    Where: https://auth0.com/signup

  2. Create the tenant

    Choose a unique tenant name (permanent; becomes the domain) and the region (AU, CA, EU, JP, UK or US), which decides where user data is hosted. Use separate tenants for development and production.

    • verapli co-pilot
    • Human step: You press submit
    • After: Sign up for Auth0

    Where: https://manage.auth0.com/

  3. Create a Regular Web Application

    In Applications, Applications, create a Regular Web Application and on its Settings tab set Allowed Callback URLs (e.g. <APP_BASE_URL>/auth/callback), Allowed Logout URLs and Allowed Web Origins.

    • verapli co-pilot
    • Human step: You press submit
    • After: Create the tenant

    Where: https://manage.auth0.com/

  4. Copy domain, client ID and client secret

    From the application's Settings tab copy Domain, Client ID and Client Secret. Generate AUTH0_SECRET locally with openssl rand -hex 32.

    • verapli co-pilot
    • After: Create a Regular Web Application

    verapli captures AUTH0_CLIENT_SECRET here by plain code: encrypted in your browser, never shown to AI.

    Where: https://manage.auth0.com/

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Can cost moneyThe rules say

Tenant name cannot be changed and a deleted name cannot be reused; the region decides where data is hosted. Choose both carefully. [1]

Worth knowingThe rules say

The Free plan allows a custom domain, but only after credit card verification. [3]

What you end up with

Env varSecretFormatWhat it is
AUTH0_DOMAINnot secretTenant domain, e.g. <tenant>.<locality>.auth0.com, or a custom domain.
AUTH0_CLIENT_IDnot secretApplication client ID.
AUTH0_CLIENT_SECRETsecretApplication client secret.
AUTH0_SECRETsecret64-hex-character secret the SDK uses to encrypt the session; generated locally, not by Auth0.
APP_BASE_URLnot secretBase URL of the app (http://localhost:3000 in development).

Pricing

  • Free tier: Up to 25,000 MAUs, unlimited social connections, 1 custom domain (card verification), 5 organizations; no card to sign up.
  • Costs: B2C Essentials from $35/month (500 MAUs); B2B Essentials from $150/month.

Source [3]

For agents

The same entry as JSON: /api/v1/entries/auth0/tenant · requirements /api/v1/requirements/auth0/tenant · terms /api/v1/terms/auth0/tenant.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Auth0 tenant and application, and how long will it take?"
  → tools/call requirements { "provider_id": "auth0/tenant" }

Sources

  1. Create tenants Asked to create a tenant after sign-up; unique tenant name (lowercase letters, numbers, hyphens, 3-63 chars) cannot be changed and deleted names cannot be reused; region locality AU, CA, EU, JP, UK or US decides domain and data hosting; sub-locality assigned automatically; separate tenants recommended per environment; custom domain recommended for production. · accessed 25 October 2026 · official
  2. Auth0 Next.js quickstart Regular Web Application; Applications, Applications, Settings tab holds Domain, Client ID, Client Secret and Allowed Callback/Logout URLs/Web Origins; env vars AUTH0_DOMAIN, AUTH0_CLIENT_ID, AUTH0_CLIENT_SECRET, AUTH0_SECRET (openssl rand -hex 32, 64 hex chars), APP_BASE_URL. · accessed 25 October 2026 · official
  3. Auth0 pricing Free plan up to 25,000 MAUs, unlimited social connections, 1 custom domain (card verification required), 5 organizations, no card to sign up; B2C Essentials from $35/month, B2B Essentials from $150/month. · accessed 25 October 2026 · official
  4. Stripe Projects provider catalogue Auth0/Okta is listed in the Stripe Projects catalogue as auth0/client (Auth). · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. Okta (Auth0) is not affiliated with verapli.