4
8 Comments

Navigating Unexpected Costs: A Startup's Tale with Auth0

Hello fellow founders and startup enthusiasts

Today, I'd like to share a surprising and somewhat costly experience we had at Notion Widgets (www.notion-widgets.com), which I believe could provide some valuable insights for fellow entrepreneurs.

The Unexpected Bill

Like many startups, we were ecstatic to see our user base growing. With an average of 150-300 new users registering on our system daily, we felt we were on the right track. To streamline the registration process and ensure security, we partnered with Auth0, a popular identity platform.

Then, one day, we were taken aback by an unexpected charge on our credit card: a whopping $450 from Auth0! 🤯

The Misunderstanding

Our initial understanding of Auth0's billing system was that we would be charged only for "active" users—those who frequently logged into our application. To our surprise, we learned that Auth0's billing counts every new registration, regardless of their subsequent activity or lack thereof.

Given the surge in registrations we witnessed in August, this translated into the exorbitant bill we received.

Seeking Compassion, Facing Reality

As a startup, every dollar matters. Hoping for understanding, we reached out to Auth0 to explain our situation and the genuine misunderstanding we had about their billing system. We hoped they might consider our startup status and offer some leniency. However, they remained firm on their stance, and we found ourselves in the tough position of having to foot the bill.

Pivoting with Purpose

We believe in being proactive. While the situation with Auth0 was unfortunate, it spurred us into action. We decided to distance ourselves from their service and embarked on developing our own user registration and login solution. This endeavor took two weeks, coupled with intensive testing.

However, not everything went smoothly. Our customers weren't entirely pleased with the sudden change, reminding us of the delicate balance between operational costs and user experience.

Lessons Learned

After this rollercoaster of events, here are a few takeaways I'd like to share:

  1. Always Dive Deep into Pricing Terms: Before signing up for any service, ensure you fully understand their billing practices. This can save you from unexpected expenses later on.
  2. Customer Experience is Paramount: Even if internal changes are for the company's benefit, it's essential to ensure minimal disruption for your users.
  3. Stay Resilient: Every challenge presents an opportunity to learn and grow. For us, it pushed us to develop our own solution, giving us even more control over our platform.

In conclusion, our journey with Auth0 was an eye-opening experience. While it came with its set of challenges, it also taught us invaluable lessons about vigilance, adaptability, and always prioritizing our users.

To every founder out there, may our tale serve as a reminder to always be prepared for the unexpected and to face every challenge head-on.

on October 28, 2023
  1. 1

    If you only need login and registration, you can easily integrate multiple social login options on your App without paying any extra fees.

    1. 1

      Thank you for your advice. This was exactly my first consideration, however, with Auth0 I supported the login with email and password. I need to continue this here to not lose paying customers.

  2. 1

    Good to know. I am in the process of building a very simple app and was looking at Auth0. What did you switch to?

    1. 1

      Since my app is based on Nextjs I have implemented NextAuth on my end. So I was able to cover email and social login. If I would have depended only on social login, I would have directly set only on social login. I don't know how it looks like for you, or what your app should support.

  3. 1

    Taking the time to understand the pricing terms and how they impact you as you grow is really good advice and reminder. I'm currently also using Auth0 -- going to go double check now 😅

    Out of curiosity, if you had fully understood Auth0's pricing terms, would you have chosen differently? Would you have chosen to invest in building out your own solution right off the bat, or still use Auth0 and migrate to a home grown solution later on?

    1. 1

      Today I wouldn't waste a second and would develop my app without Auth0 unless I needed their experience. What is meant by this: If you are looking for a solution to only sign up or register users, I would not go this way anymore. If you need enterprise functionality, Auth0 would be an alternative instead of developing it yourself. They bring a lot of experience to the table, which you have to pay for. If this is possible with your income, you can go this way. I would recommend you to make a pro and con list and see what speaks for Auth0 or against it.

  4. 1

    Thanks for sharing, Dan. It's sad to hear that.

    Having said that, it just confirms my belief that by outsourcing some core aspects of your product to third party providers, you might save cost at the beginning, but it becomes very costly in the long run. Not only that, it also locks you in their ecosystem. It happened with Heroku, Auth0, and will continue to happen in the future.

    1. 2

      I couldn't agree more. From my point of view, you should never give out a core functionality. Once the dependency is there, it takes a lot of effort to get it out of your application. Thanks for your confirmation of my thoughts.

  5. 1

    This comment was deleted 3 years ago