Unable to Contact Sales for Enterprise Plan

Get Help
,
1

Hi,

We’re interested in discussing an Enterprise plan with Auth0, but we’ve been unable to reach the Sales team for the past two weeks despite multiple attempts.

Is there an alternative way to contact Sales, or could someone help route this request internally?

Thank you.

3

Hi @TigraITB

Welcome to the Auth0 Community!

How have you tried to reach our sales team? Have you submitted a form via this link and you have not received any replies from us or did you try a different contact method?

Additionally, if you have any questions I might be able to answer regarding the Enterprise plan, let me know!

Kind Regards,
Nik

4

Hi Nik,

Thank you for your response.

Yes, I submitted a request through that form, but unfortunately I have not received any response yet.

Our main question is regarding mTLS authentication. We are currently using the free tier, but we provide our service to several business customers and would like to understand what options are available for accessing the mTLS feature. Is it only available through an Enterprise plan, or are there other alternatives that would allow us to use mTLS?

Thank you for your help.

Kind regards,
TigraITB

5

Thanks for letting me know. I will investigate the matter further and see what I can do on my end about it.

To answer your question directly: Yes, native mTLS support within Auth0 is an Enterprise-level feature. Because mTLS requires highly specialized network routing and edge-level certificate validation, it is not available on the Free, Essentials, or Professional self-service tiers. However, if an Enterprise plan is not currently viable, you can implement a standard architectural workaround using an API Gateway.

Standard authentication happens at the application layer. When a client sends a Client ID and Client Secret, the Auth0 application reads that payload and validates it.

mTLS, however, happens at the network/transport layer. The client must present a valid X.509 certificate during the initial TLS handshake, before the request ever reaches the Auth0 application logic.

  • To support this natively, Auth0 must provision dedicated infrastructure and specific endpoints (like mtls.your-custom-domain.com ) that are configured to terminate the TLS connection and extract the client certificate.
  • Because this relies heavily on Custom Domains (a paid feature) and dedicated edge configurations, Auth0 bundles mTLS alongside other high-security compliance features (like FAPI - Financial-grade API support) in the Enterprise tier.

Depending on your current growth stage and budget, you have two primary paths forward:

Option 1: The Native Auth0 Path (Enterprise Plan)
If you require Auth0 to natively enforce mTLS at the /oauth/token endpoint (where your B2B customers request their access tokens) and you want Auth0 to issue Certificate-Bound Access Tokens , you will need to upgrade to an Enterprise plan.

You would need to reach out to the Auth0 Sales team to discuss an Enterprise contract tailored to your B2B use case. I have stated above, I will see what can be done if you have not received a reply yet. Additionally, have you checked if the email is not in any spam folder or blocked by your email provider if you are using a work one?

Option 2: The API Gateway Workaround
If you cannot move to an Enterprise plan but your B2B customers strictly require mTLS to talk to your APIs, you can decouple the mTLS requirement from Auth0:

  1. Token Issuance (Auth0): Your B2B customers continue to get their Access Tokens from Auth0 using standard, highly secure M2M methods available on lower tiers (like private_key_jwt or standard Client Credentials).
  2. mTLS Enforcement (Your Edge): You place an API Gateway (like AWS API Gateway, NGINX, Kong, or Cloudflare) in front of your backend services.
  3. The Handshake: You configure your API Gateway to require mTLS. When the B2B customer calls your API, they must present their client certificate to your Gateway and pass the Auth0 JWT in the Authorization header.
  4. Validation: Your Gateway validates the mTLS certificate, validates the Auth0 JWT signature, and only then allows the request through to your backend.

Let me know if you have any other questions in the meantime!

Kind Regards,
Nik