Congrats on the launch, building a product in this space is incredibly difficult. I took a look at the stack, here are a few observations:

- "ISO certified secure auth": What does that mean? I could not find proof of your ISO certification. Can you please share?

- 10k M2M tokens for $250/month sounds like a really bad deal if I can just spin up https://github.com/ory/hydra that can easily handle 10k requests per second.

- Looks like you're using OAuth2 as the primary "login" and "session management". What compelled you to do this?

- It looks like you're using some open source technology under the hood for the OAuth2 flows - which one are you using (out of curiosity)?

And finally, what sets you apart? It looks like the same solution for the known problem that big players (such as Okta and Auth0 - publicly traded) have already mastered. Ory (github.com/ory) for example has it's global network approach where you no longer need datacenter locations and is Open Source. Clerk is targeting React devs. What's your niche? Doing everything from auth to billing is, in my experience, way too much for a small team with little resources. Just getting Auth right is a mammoth task.

> 10k M2M tokens for $250/month sounds like a really bad deal if I can just spin up https://github.com/ory/hydra that can easily handle 10k requests per second.

Spinning one up is easy, sure. Making sure it's production ready, is not so much.