2 ms·

Thank you for this comprehensive explanation! I will look into Stripe for billing, and look into Auth0, SuperTokens, and Stytch for auth. I just checked out Wa

Thank you for this comprehensive explanation! I will look into Stripe for billing, and look into Auth0, SuperTokens, and Stytch for auth. I just checked out Warrant and your docs are very clean :) One limiting factor for my adoption of Warrant would be that my application would need to perform auth on each request from each user, which in total may be on the scale of thousands of requests per second for my application. When I looked at the pricing section, Warrant's Standard Plan costs $1 per 1,000 API requests / mo. This would be too expensive for my use case, but perhaps I am not the target customer...? sweat smile Regardless, I wish you the best of luck with Warrant! I agree with what you said about rate limiting. Given that Warrant is also an API product, has rate limiting been something you have found to be a necessity already? What factors or indicators would push you to add rate limiting?

kkajla 5y ago
I'm glad you got some value from my answer. Happy to help! Thank you! We put a lot of effort into maintaining quality documentation, so I appreciate the compliment! Our pricing is intended to scale with an application. $1 per 1,000 API requests / mo is expensive for an application with thousands of requests per second, but I would imagine an application with that kind of traffic would fall into our enterprise tier which provides volume discounts. We also have a nice free tier for testing out the product in some capacity at any stage and offer better deals for early stage startups. Regarding rate limiting. It hasn't really been an issue for us yet. As an API product, the only users I would rate limit would be free tier customers who are generating tons of requests and degrading performance for paying customers (hasn't happened yet). For paying customers, I would probably want to scale our infrastructure to support the amount of traffic they're bringing in since they're paying.
cco 5y ago
I work at Stytch, let me know if you have any questions while trying us out!

kkajla 5y ago

I'm glad you got some value from my answer. Happy to help! Thank you! We put a lot of effort into maintaining quality documentation, so I appreciate the compliment! Our pricing is intended to scale with an application. $1 per 1,000 API requests / mo is expensive for an application with thousands of requests per second, but I would imagine an application with that kind of traffic would fall into our enterprise tier which provides volume discounts. We also have a nice free tier for testing out the product in some capacity at any stage and offer better deals for early stage startups. Regarding rate limiting. It hasn't really been an issue for us yet. As an API product, the only users I would rate limit would be free tier customers who are generating tons of requests and degrading performance for paying customers (hasn't happened yet). For paying customers, I would probably want to scale our infrastructure to support the amount of traffic they're bringing in since they're paying.

cco 5y ago

I work at Stytch, let me know if you have any questions while trying us out!