Leaving Auth0? Your monthly bill just dropped.

Monthly cost at common MAU tiers

Retail list prices, Auth0 figures taken from auth0.com/pricing and re-checked 14 September 2026. WeldForge pricing is from our pricing page (annual billing).

The table above is Auth0’s B2C line. If you sell to businesses and need enterprise SSO connections, Auth0 prices that separately and much higher: B2B Essentials starts at $150/mo and B2B Professional at $800/mo, both quoted from 500 MAU, with enterprise connections metered. That is the comparison where a per-tenant SAML IdP you run yourself changes the arithmetic, not the consumer one.

Feature-for-feature

What's in the base paid tier on each side. ✓ means "included with the plan you bought." Auth0 figures reflect the base B2C Essentials unless noted.

The short version: WeldForge's $29 tier covers what Auth0 typically gates behind its $800–$1 500/mo tiers, and every WeldForge hosted tier includes capabilities Auth0 reserves for custom-priced Enterprise contracts.

Migrating from Auth0

Most Auth0 deployments we see are 80% OIDC clients, 20% SAML SPs, plus a handful of rules / actions. The transition below takes a typical product team a week of real work.

Step 1 — Export your Auth0 tenant

Auth0 Management API exports users (with password hashes), connections, rules, and tenant settings. For a one-off migration:

curl -X POST https://YOUR-DOMAIN.auth0.com/api/v2/jobs/users-exports \
    -H "Authorization: Bearer $AUTH0_MGMT_TOKEN" \
    -H "Content-Type: application/json" \
    -d '{"format":"json","fields":[{"name":"user_id"},{"name":"email"},{"name":"email_verified"},{"name":"username"},{"name":"user_metadata"},{"name":"app_metadata"},{"name":"identities"}]}'

Step 2 — Create the WeldForge tenant

curl -X POST $HOST/api/admin/tenants \
    -H "x-app-authorization: $TOKEN" \
    -H "Content-Type: application/json" \
    -d '{"slug":"acme","name":"Acme Corporation"}'

Step 3 — Import users

Auth0 exports bcrypt hashes for password-based users. WeldForge accepts bcrypt-compatible hashes directly — users keep their current passwords and do not need to reset them. For users created via social or SAML connections, import with no password and the federation will rebuild on next login.

curl -X POST $HOST/api/admin/users/bulk \
    -H "x-app-authorization: $TOKEN" \
    -H "Content-Type: application/json" \
    --data-binary @auth0-users-export.json

Step 4 — Re-register OIDC clients

Each Auth0 Application becomes a WeldForge OIDC client. The redirect URIs carry across unchanged. Update your application's OIDC issuer URL from https://YOUR-DOMAIN.auth0.com/ to https://sso.weldforge.org/t/<your-slug>/ and the rest of the OIDC wire protocol is identical.

Step 5 — Port any Auth0 Rules / Actions

WeldForge's equivalent is a combination of JSONPath claim transforms and group-to-role bindings. Most Rules fit cleanly; complex logic that needed JavaScript in Auth0 maps to an outbound webhook that your backend responds to.

FAQ

Will my users have to reset their passwords?

No. Auth0 uses bcrypt; WeldForge accepts bcrypt hashes directly on import. Passwords carry across invisibly.

Does WeldForge support Universal Login-style customisation?

Yes — the hosted login and admin portal both support per-tenant branding (logo, colours, fonts). Starter tier includes it; Auth0 historically charged extra for custom-branded login screens.

What about Auth0 Rules and Actions?

Declarative transforms (add a claim, route based on email domain) are expressed as JSONPath rules in WeldForge. Actions that ran arbitrary JavaScript in Auth0 are expressed as outbound webhooks your backend handles — same behaviour, stronger audit trail.

Can I self-host during the migration and move to WeldForge Cloud later?

Yes. The data model is identical across self-host and cloud tiers. A migration is a pg_dump | restore + DNS cut-over.

What happens to refresh tokens in flight?

In-flight Auth0 refresh tokens invalidate on issuer change. Your SPA / mobile apps will see a one-time re-login on cut-over day; every session after that runs against WeldForge cleanly.

Do you have a Hacker News thread or case studies?

Not yet — we're a new entrant. The platform itself has been in production internally since 2024 and passed a full security audit in April 2026. Browse the source.