Advait Ruia:
We built something people wanted. We're growing. We've proven that we can scale that adoption. Now this next set of checkboxes is like, "Okay, can you monetize this, and then can you scale that monetization and revenue?"

Eric Anderson:
This is Contributor, a podcast telling the stories behind the best open source projects and the communities that make them. I'm Eric Anderson.
We have today, Adi of SuperTokens. He's the Co-Founder of the company and the open source project. Adi, thanks for coming on the show.

Advait Ruia:
Thank you, Eric for having me. Happy to be here.

Eric Anderson:
Adi, we met just, what was it? A week ago, or couple of weeks ago, and this was three weeks after my baby was born. This is the first show we're recording post paternity. Excited to be back at it.

Advait Ruia:
Congratulations on the paternity leave and on being back.

Eric Anderson:
You're doing some traveling. Is that right?

Advait Ruia:
I'm actually moving. I'm from India, but I'm currently moving to SF, so I'm in the middle of that move. I actually just got my immigration visa and all of that approved a few days ago, so I'm excited for that move.

Eric Anderson:
Well, hopefully most of the bureaucracy is behind you, and you can get onto the fun stuff.

Advait Ruia:
Yeah. Most, but yeah.

Eric Anderson:
Most, good.

Advait Ruia:
Yeah.

Eric Anderson:
SuperTokens is interesting. Maybe we should frame this. I want to give you just a minute to give us the elevator pitch, 30 seconds on what SuperTokens is. Well, let's do that now and then I have some questions about the concept.

Advait Ruia:
Yeah. So, SuperTokens provides open source user authentication. You're a developer, you're building an app, you want users to be able to sign up, you need to build the signup screen, let them reset their passwords, verify their email IDs, and a whole host of other features.
That's, essentially called user authentication. Instead of you having to build that out, you can just implement a solution like ours and you can have it out the box in 10 minutes.

Eric Anderson:
There's a handful of companies and open source projects doing this, which is really surprising. I want to say it's surprising, but it certainly tells us that there's a lot of dissatisfaction with developers, with the status quo.
Auth0, kind of pioneered this market and then folks are still like, "No, I need more. I need something else." You have hit a chord. There are 3,000 people in your Discord. You've got 8,000 GitHub Stars. Things are growing quickly. Tell us what exactly is happening that makes this interesting despite there being so many alternatives.

Advait Ruia:
Yeah, yeah. I mean, so there are a couple of things, I think, about SuperTokens. You're right, there are lots and lots of alternatives. It's a huge market. Authentication is pretty big. So, I can understand why there are a lot of people competing, but at this point even I'm, sometimes surprised.
I think there aren't actually that many on the open source side that are doing well. It's actually just two or three.
On the open source side, if open source is something that's important, if the ability to self-host is important, and everything else that open source brings, you don't actually have that many options.
There's a few other things about SuperTokens that makes it more attractive, is that we integrate very natively into your product. Our front-end UI sits natively to your website as opposed to, for example, with Auth0, it being a redirect to Auth0's domain and then being a redirect back to your website. All of our front-end is native to your website.
Similarly, all the backend auth logic is native to your backend APIs. If you're coding in Node, or Golang, or Python, all of our auth logic resides there. So, any changes you want to make, any custom logic you want to add or inject is all native to your code base as opposed to, again, going to Auth0's web editor and uploading that JavaScript there.
So, I think, like you said, there's clearly demand for authentication providers. The reason we think that is because Auth0 is a great product, but with the benefit of hindsight, you can see that you're giving up control if you're implementing authentication, in multiple ways.
We, essentially try and solve that. We want to be the best of both the build and buy argument. Be very quick to implement off the shelf, but as good as, as if you'd built it yourself.

Eric Anderson:
Is it fair, when you say it's native to your front-end client or your backend endpoint, does that mean it's deployed as a library as opposed to a service, a SaaS product?
When I think of a library, sounds a little difficult to monetize, but awesome, maybe for users and for the open source. Is that a correct way to think about it?

Advait Ruia:
Yes. It's, sort of hybrid. The library is on the front end, there is a library on the backend. It is SDKs, but yes, you're right in the sense that they contain a lot of the logic and code.
To use that, you still need a layer that persists data into the database, and that is the cost service. The front-end will talk to the backend and then the backend still needs to talk to the database. So, that talks to the SuperTokens score, which then persists data in the database. That part is either managed, or self-hosted, or whatever it is.

Eric Anderson:
Awesome. Open source, certainly is valuable and then this native elements are also valuable. Part of the reason, maybe both of them are valuable is that it allows you a lot more control over the user experience, or you can build custom workflows. Is that right? Maybe tell us a bit about that.

Advait Ruia:
Correct. Absolutely. That's definitely it. Then a lot of B2B companies want to deploy on their customer's infrastructure. Again, that's just not possible with a lot of other solutions.
Then there's the stuff that everyone claims, which is DX and documentation and all of that stuff, which everyone says they're the best at. We put a lot of effort into documentation and into getting started quickly. We've built a lot of custom tooling for Docusaurus. That's something that, I think we have the metrics to prove that it's working.

Eric Anderson:
Yeah. Yeah. Certainly. Yeah, you don't get that many users and enthusiasm without pretty good experience.
Adi, I want to jump into your story, and the story of SuperTokens, and what inspired you to get started on this, and how did it happen?

Advait Ruia:
Yeah. I mean, my story's a little bit extended. Obviously, I wasn't exposed to tech, growing up. I wasn't in the tech ecosystem at all. Nobody, where I grew up is in tech, but essentially studied mechanical engineering. Through different things, eventually got exposed to tech. Started working with tech startups when I was a student. Did really well with those companies. Had a brief stint in venture capital as well. Started building my own company.
Authentication was a problem we had to solve. Then we, typical first-time founders over in engineering, a lot of solutions at the time, but one of the things that we really needed to solve was something called session management, which was this subset within the authentication space.
We saw a lot of security vulnerabilities happening there, like Docker, Facebook, GitLab, YouTube, Uber had all had major session vulnerabilities, and we thought of a really interesting way of implementing sessions.
Really, this all started with us writing a blog post on how sessions should be handled. That blog post did really well. We had people from all over the world reach out and then we're like, "Interesting. People are excited about this."
The first startup at that point, it was an experiment. It wasn't really working out. Then we thought this was really interesting. We built it as a product. We got users. We got into Y Combinator. Then that was the real impetus for what SuperTokens is today.
At that point, before that it was still really not user authentication. It was still not open source. It was still ... After we got into Y Combinator, I think this is when the whole project really kicked off and we really got a lot of insights into the overall problem space.

Eric Anderson:
So, you were building a different company at the time you wrote the blog post. Is that correct?

Advait Ruia:
Yeah, basically.

Eric Anderson:
This is just the pattern with infrastructure companies, it seems is that nobody intends to start an infrastructure company. They try and build something else and then realize along the way that they built something of value.
Can you summarize the blog post? Maybe what was so interesting about it? A different approach to doing sessions?

Advait Ruia:
Yeah. Essentially, for sessions it's like, you have these concepts called access token and refresh token. With the access token, you have something either called long-lived access token or a short-lived access token, and jots.
So, there's a couple of concepts there, but essentially there were three or four major flows that everyone was implementing. One of them was, basically just a long-lived JWT, which is basically if somebody else accesses that JWT, you can access that person's account. The attacker can access that person's account without knowing their login details, without knowing their email or password. Right?
There was so much security around login, but so many apps stored the access token in local storage, which means any malicious JavaScript can access it, and there's just a bunch of ways you can attack that.
We said, "The least secure is the most common flow. This is what everyone does." Then people slowly build on top of it. This is the four common flows that you'll see.
What we proposed was, do something called rotating refresh tokens, and that'll allow you to detect session theft. Out the box, we'll solve a lot of the other kinds of attacks, like CSRF, XSS. We'll protect against all of those, which you can do with any flow, but we also implement rotating and refresh tokens, which will allow you to detect session theft.
So, if two devices are using the same session, you can actually detect that and then log out both devices. You can guarantee that, as long as both sessions are being used, you can guarantee that, that attack is not happening.
So, that's what we proposed, and then we built ... There was a lot of edge cases and race conditions that you had to factor in to do that, and we did those. We built libraries to solve for those edge cases.
One of our libraries to solve for those edge cases is actually used by Auth0 in their own implementation, offloading refresh tokens. So, that library has a few hundred thousand weekly downloads. It's on every Auth0 front-end client as well.

Eric Anderson:
Wow. So, you write this blog post. Was that because you were intending to pivot into this infrastructure company, or are you just trying to share learnings?

Advait Ruia:
Yeah. It was a little bit of both, I guess. There was no real clear ... It was just like, "Let's just try." We spent a meaningful amount of time writing that blog post for sure, but there was no, "This is going to be the company and this is the problem we're going to solve for the next 10 years." It was more gradual than that.

Eric Anderson:
Good. Eventually, with the enthusiasm of blog posts, you decided to start the company. When was it clear that this would be open source, and the shape it would take?

Advait Ruia:
I think we dabbled around with that for a while. I'd like to say that three years ago that, today open source is a lot more clearer. Even as recently as three years ago, there wasn't as much information about it.
It was already there. Obviously, you had GitLab and Docker and a few others, but it wasn't as clear. Yeah, I mean, I think we dabbled with it for a while, for a year almost. Then when we really understood all the pain points associated with auth, spoke to at least 100 companies at different scales and stages and all these different things, and we're like, "Open source can actually be part of the solution."
The unique architecture was one part of the insight, the way I told you, the whole native integration. That was one part of it. Then we were like, "Okay, open source also solves some of these problems. So, with these two or three things, we think that this could be a much more compelling product."

Eric Anderson:
Got it. It wasn't so much, "We want to do something in open source," as much as their customers wanted a solution, and open source was the answer?

Advait Ruia:
100%. We just didn't know much about open source before, to have that thought process.

Eric Anderson:
How big is SuperTokens at the time? This is you and a few friends, and you're in India at this point?

Advait Ruia:
Pretty much.

Eric Anderson:
I went and looked at the GitHub Star history, and you had a big jump in adoption, in December of 2020 and then again in March of '22. What happened at those points?

Advait Ruia:
Yeah. December 2020 was when we actually launched. Before that, there was no real ... Though it was an open source, we never announced anything. We never did anything. December 2020 is when we did our first ever Hacker News launch for user authentication, and that did extremely well.
At the time, we were one of the most upvoted YC companies on Hacker News, more so than Firebase, Webflow, Hasura. We were a pretty good company on both sides, the companies that had more upvotes and less upvotes were ... It was a great company.
So, that's what happened in December 2020. We launched in Hacker News. It did really well. Again, the repo was completely empty. It was not usable, like supertokens.io didn't use SuperTokens. It just didn't work. It just didn't work for at least six months after.
There was no ... Very basic features. It just didn't exist. So, it was really, like a shell of a repo with some code and a thesis, and the thesis resonated. We're like, "Okay, now we should build this."

Eric Anderson:
Is this thesis the same one we heard about from the blog post, or had it evolved from then?

Advait Ruia:
Oh, yeah. It definitely evolved. The blog post is very focused on sessions, whereas this at this point was a lot more to do with user authentication and the much broader problem space as opposed to just session management.

Eric Anderson:
All right, so there was a lot of things around authentication that you had tied together in this launch. It may not have worked, but it spoke to people.

Advait Ruia:
Absolutely.

Eric Anderson:
Then eventually, it gets working. You said it was six months until you had a real product. What happens between then and March '22, or maybe what happened in March '22?

Advait Ruia:
Yeah. I would say, a working product for the most basic use cases at that point. It took six months to still only be usable for developers and pre-launch startups. Still nothing that any company would scale or anything that would actually use.
A lot of time after that was just building, just grinding it out, building the things you needed. We didn't support most of the SDKs. You could only use us if you used X and X tech stack, which is very limited.
So, building more SDKs, building more features, actually just making the product mature. That's what happened, of just grinding that out for a year and a half.
Then in March 2022, we got featured by one of the largest YouTubers called Fireship. It's a large YouTuber for developer products. So, they mentioned us as an open source project to keep an eye out on. That video had 600,000 views in the first few days, and obviously a lot of traffic came our way.

Eric Anderson:
Going back a bit to the initial launch, I can imagine some people thinking, "We shouldn't launch our open source until we have a full product. It's really good. Great user experience."
How did you resolve that tension? What made you feel like it was time to launch then versus later?

Advait Ruia:
Just the failed startup. You go through a failed startup and you learn that lesson pretty deeply, which is like, you just want to validate as quickly and as much as possible. I really didn't want to spend time building something that didn't resonate, or that didn't have PMF, or that people didn't want to use, or didn't need.
So, the whole year, that whole 2020 with YC and all was just trying to figure out that this is something that people actually cared about. So, we did that qualitatively and privately, and now we wanted to do that publicly.

Eric Anderson:
Now that the product's in the hands of people, it's growing quickly. What does the target user look like? Who really gets the value proposition here?
You mentioned, B2B companies like the open source aspect. Maybe folks who want a lot of control over the flow, or is it really just everybody? Anybody on Auth0 should take a look at SuperTokens?

Advait Ruia:
Yeah. This is an interesting question because I've discussed this with so many founders, like dev tool founders especially, right? It's like, "What is your ICP?" All of our instinctive responses is, "All devs building apps." Obviously, your ICP is always more focused.
So, I think it's two sets of ICP, right? One is a more broader, general developer, early-stage startup, sort of ICP. There you're just focusing on providing the best experience, the best developer experience, quickest to get started. Then allows you to do a lot of powerful things if you want to be able to do them.
Maybe they're not really looking at those. They don't really ... In their first impression, they may not even notice the native integration. They may not even care about how customizable it is.
That's, sort of like one ICP. Then the other ICP is, your more mature companies, your mid-market, your enterprises. There we see a lot of requirement for complex use cases, and customizations, and adding custom code in the front-end and backend and all of those things.
There, I think the native integration and the entire architecture and philosophy is a lot more valuable. The fact that it's open source adds a lot of trust and credibility. It's great for building trust as an infrastructure company because it's like, "Okay, fine. I can see the code. I can see the quality of the code. I can see this, is this a good team? Is this not a good team? I have an exit door, exit hatch. If anything happens, at least this level of the product is always going to be available to me. If they get acquired, I always have this much accessible," et cetera.
That, little bit applies to both ICPs, but applies much more on the enterprise side.

Eric Anderson:
Anything else, Adi that we should cover with regard to the product?

Advait Ruia:
Yeah. I think it's pretty unique, the overall, the way it works. The architecture is pretty unique and the overall design philosophy of making every function accessible to the developer, like every online function. So, any feature you want to build, you can build it yourself, any customizations you want to make.
Anything that's going wrong with the product, you can debug yourself because so much of it is happening within your app as opposed to needing to ask SuperTokens. Yeah.

Eric Anderson:
Normally, an auth solution will expose just the five, 10 critical commands that you'd want to use, log in, log out, reset password. That's the API. You're telling me that you, kind of expose a much richer API. There's no private methods here?

Advait Ruia:
No. Pretty much, no. Right? If you go through our backend SDK, if you go through our API reference for our backend SDKs, so you'll see the major, like you said, the five, 10 major ones, like create new user and all of those, but then all the functions that they use are also exposed to you.
Maybe if you want to access any of those underlying functions ... Let's say, for example, with password lists, if you're using password lists, the consume code, the create code, all of those functions are also accessible to you, like send email.
Let's say, if create passwordless user was the overlying feature, then you can also access all the different intermediary steps that SuperTokens does to do a passwordless account creation.
You can change any part of that, the way the emails are sent, you want to use your own email or SMS sending service. You want to change the way the code is generated. You want to change the way the code is consumed. Anything, right? You want to add extra logic in the consumption or verification of the code. All of those things, you can do.

Eric Anderson:
Got it. So, you built all these really low-level functions. Then I noticed on your website, you refer to these as recipes, a passwordless recipe, a social, an email login, but then also social plus passwordless, email plus passwordless.
Any combination of these, you pre-built these aggregate sets of functions. Then even after I choose one of those aggregate sets, I can go in and customize any one of those functions?

Advait Ruia:
Exactly. This is really powerful. This is a really powerful philosophy once people understand ... Once they do that, once they have that first use case and they actually do it, they're like, "Oh, yeah. Oh, okay, you actually expose everything to me, and I can do any of this."

Eric Anderson:
Good. Well, maybe we'll circle back to the product. I wanted to ask you something. You're moving now, from India to San Francisco. I imagine there's a lot of would-be founders, especially open source founders who wonder, "Do I need to move to San Francisco to do a company?"
What would you say to them, and what's your experience been? It sounds like you've gone quite a way while in India.

Advait Ruia:
Do you need to, with the word, need highlighted, like an emphasized? No, you don't need to. Should you? Yes. Right? The startup game is a probability of success game, and everything is about probabilities of failure and probabilities of success. If you want to maximize your probabilities of success, you should be here.
I think if you say, "Do you need to be here?" it becomes a debatable argument, but if you say, "Does it increase or maximize your probabilities of success?" I don't think that's debatable, or at least in my experience, it's not.
The one month here is definitely, I can definitely see value already. I mean, look at this, right? We're having this call today because I was in SF, because I met you physically at an event in SF.
This is just one out of the 15 outcomes I've had in the last month of being here physically. I've gone for lunches and dinners with people. I now talk to someone who sold their company for four billion, and I'm constantly in touch with them on how they built their enterprise company.
Multiple, multiple interactions like this all the time. I can see this over six months, one year, two years really compounding. It's only been a month, but as these relationships mature over a period of time, it really does compound.

Eric Anderson:
Totally. That's interesting perspective. Switching gears yet again to more industry trends. There's a lot of news, lately around passkeys. I think Google making their change to make password keys default has, maybe spurred a lot of that news.
What do you see as the future of authentication? Do passkeys play a role? Does that affect SuperTokens, and anything else we should keep an eye on?

Advait Ruia:
Yeah. Yeah. I mean, I think passkeys are great. It's just a much better experience from every perspective for every single person. It's a better user experience. It's better security. It's better for the developer. You don't have to serve passwords. It's definitely beneficial from every point of view.
I mean, fundamentally you're just validating the biometrics of the user, either the face ID or the fingerprint. Validating that, and then you have access without actually sending over a password to the service.
I think it's definitely valuable in terms of, we definitely see this playing a big role, moving forward. I think the time is right for passkeys because most devices today have biometric, which may not have been the case five or 10 years ago. You would have to buy, maybe actual additional hardware to plug into your device to do that. Five, 10 years ago, you didn't ... Today, it's kind of default in almost every device you buy. So, I think it's the right time.
How does it affect SuperTokens? I think this is just going to be one more recipe, as you pointed out, right? It's just going to be one more type of authentication method. People are still going to need to integrate passkeys. They may not want to go into all of the details of how to integrate it.
Then they might want other ... Again, the actual login method is a small subset of the overall authentication and authorization problem. You still have to do a lot of other things around the initial authentication.
I think you still, for again, simple use cases ... If you just wanted simple social sign-in, you could do that today, as well, easily. If you just want a simple passkeys implementation, you can probably do that easily as well, but you probably need, or you will need, or lots of companies need a lot of other things as well.

Eric Anderson:
Anything else on the authentication horizon to keep our eye out for?

Advait Ruia:
I mean, there's always a lot happening with identity. It's such a big space. It's such an interesting space. There's always something happening. My thing has always been interesting, is how is physical and digital identity interact over a longer period of time?
Today, those are two independent systems. Your physical identity is very much government-issued. With passkey, it's going to become device-based. It's completely based on your specific device. How do those, over time, evolve?

Eric Anderson:
How about authorization? I mean, I think, maybe the other trend we're seeing is, there's a handful of companies trying to solve, post-authentication, you're in the app. Now what permissions you have within the app?
Historically, that's all been, kind of custom code, and it gets wonky as you add features to your application. Does SuperTokens get involved in the authorization side of things, and whether or not it does? What do you think of this kind of market for developer tools?

Advait Ruia:
We do some authorization today. We do have the concept of RBAC, which is that you as a developer can assign roles to all of your users, and each role can have permissions. Then you can also assign those permissions directly to a user without assigning them a role. So, we do have some sort of an RBAC system in place.
Again, that's natural because a lot of authorization ... This is the really interesting thing about SuperTokens from a long-term perspective, is the intersection between authentication and authorization happens on the session management layer, which is where you store the roles, and you read the roles, and all of that kind of stuff.
Again, because of our unique architecture of only enabling front-end and backend communication, we also completely handle the session layer. So, there's a lot of really interesting things that we can talk about over there, but essentially, yeah, we do some authorization.
We're not as powerful as a lot of the dedicated authorization providers today, obviously because they're focused on those things. For a lot of complex use cases, it still makes sense to have ... We do integrate. We work well, we work nicely, we collaborate with a few authorization providers.
We have example apps and demo apps that we've worked with them on. If you have complex use cases, we suggest to use one of those, but for a lot of common use cases, SuperTokens RBAC actually works.

Eric Anderson:
Adi, what does 2023 hold for SuperTokens, and anything we should keep an eye out for?

Advait Ruia:
Monetization, and app market, and the final leg of building a successful business, which is, I think we've proven out a lot of ... We've done a lot of the spadework and groundwork. We've built something people wanted. We've got people adopted. We're growing. We've proven that we can scale that adoption.
A lot of the checkboxes, if you will on why startups fail, we've checked. Now this next set of checkboxes is like, "Okay, can you monetize this and then can you scale that monetization and revenue?" I think those are the focus areas now.
We've already started doing that. We're releasing a lot of the mid-market and enterprise features. Between this month and the next three months, a lot of the really interesting mid-market enterprise features will be released, the highest requested from larger companies, which again, we have a lot of interesting inbound from.
A lot of that will be released in the next couple of months. Will be really exciting to see how that plays out. Obviously, our focus is always going to be on building a great developer experience. That's something we'll definitely keep working on. At the moment, these features is something I'm personally, really excited about.

Eric Anderson:
Great. Maybe it's, kind of a dovetail but, how do people get involved? Are you open to outside contributions, and what kind of contributions would be interesting?

Advait Ruia:
Yeah. We're definitely open to outside contributions. I think on our roadmap is, essentially the contributions that would be valuable.
Then there's definitely one area, if anyone's looking, if you're a front-end dev, there's definitely some improvement on the dashboard, on the user's dashboard stuff that we could, so feel free to get in touch for that. Then on the backend side, there's also plenty of stuff.
Yeah. I mean, the other contributions, more than happy if someone's willing to write about their experiences using SuperTokens, or just on writing content, or talking about authentication, or talking about the different options and authentication, and those kind of things.
I think, always talking about the options and how things work about the industry is always something that, I think we appreciate.

Eric Anderson:
I think the thing that has me so curious are, who are all these people? You seem to have a real tight engagement with them.
How do you think about community management? I'm curious if there's inspiration you take. Are there other companies who manage great communities that, inspire you?

Advait Ruia:
Yeah. From communities, I think the thing that, if I had to say how we manage, or what I'd suggest other people do is, there are a couple of things we do really well, which is we're extremely good at support.
My co-founder is really, absolutely incredible. He's online 16 hours a day. Even other engineers on the team, even if they want to reply, they can't because my co-founder's replied before they've even opened the message. My co-founder's really good at support on Discord. That's a huge thing.
Then GitHub issues, we try and ... If someone opens a PR, if someone opens an issue, if someone is using SuperTokens and is giving us some feedback, we'd try and show them that we really care about their feedback. We try and close that issue as quickly as possible. We prioritize any interactions we have with users and customers, including emails.
That same culture of replying quickly on Discord is now filtered into every user interaction and touchpoint. If I was someone who would take a couple of hours to reply to an email or a customer email, now it's in my mind that, that becomes the most important thing for me to be doing. So, I'll reply as quickly as possible.
I think all of these things just builds a lot of goodwill with people. Then I think, that then just compounds and then people will tell other people that, "You get to interact with the core team." Then they will tell people that they get to interact with the core team and it's such a great experience.
I think that really, really helps with the initial challenges of building an infrastructure company. You get really realtime feedback. You get realtime production users. You get a lot of goodwill, all of these things.

Eric Anderson:
Yeah. This becomes the marketing engine. It's mostly just word of mouth between satisfied developers on support.

Advait Ruia:
Yeah, a lot of it. Yeah. That's one big part it, but not all of it. Yeah.

Eric Anderson:
Yeah. What about content? That blog post that, kind of started it all. Do you continue to push blog posts, and is that an important, also part of the marketing?

Advait Ruia:
Very important. Super important. Again, we're pretty light on the GTM side, but these are the two things that really work for us, is content and word of mouth.
We've 5Xed our SEO traffic in the last year. We think there's at least another 10X here, and then that'll just be an engine that then we never have to ... Once it's done, it just compounds over years. Again, you don't need to actively spend effort, or time, or money on it. You write it once and it's something that plays out over two to three years.
Again, that's something we've been doing really well since day zero. We're reaping the fruits of, some of it today. We're planting the seeds for the next year, now as well.

Eric Anderson:
Back to that inspiration point, it seems like you have figured some things out. Do you look to any other projects? It's like, they're the ones that taught us how to do this, or we want to do it, kind of like they do.

Advait Ruia:
I think that there are certain elements that we like from different companies. I think this is going to be a very common and cliched answer in a couple of years, but I think Supabase's launch week is something that you'll see a lot of people take inspiration from.
I think they've really figured out how to talk about product and features in a way that people pay attention to. So, I think Supabase launch week is definitely something.
Again, I don't think we're going to be the only ones being inspired, but I think that works. Then besides that, I think then it's just about general learning and being aware of how everyone does different things. Yeah, just mostly that.

Eric Anderson:
Adi, appreciate you telling us the story of SuperTokens. Congrats on your success thus far. Thanks for doing this.

Advait Ruia:
Thank you so much, Eric. I've really enjoyed this conversation.

Eric Anderson:
You can subscribe to the podcast and check out our community Slack and newsletter at contributor.fyi. If you like the show, please leave a rating and review on Apple Podcasts, Spotify, or wherever you get your podcasts. Until next time, I'm Eric Anderson and this has been Contributor.