<!channel> We've just published our consumption-ba...
# ory-network
f
<!channel> We've just published our consumption-based pricing model for Ory Cloud. We'll add more details going forward, but you can view it right now at https://ory.sh/pricing. Please reach out if you have any questions & feedback! Note: We will only charge for the base fees throughout July and August. Of course we will create the necessary transparency on your Cloud usage and reach out before billing for any additional usage!
g
Hi, How do you define "Active Network Peers" and "Permission Check"?
f
A permission check is a API call to the "Check Permissions" endpoint (https://www.ory.sh/docs/keto/reference/rest-api#operation/getCheck) An Active Network Peer (ANP) is any actor - human or machine - exchanging tokens, establishing sessions and verifying identities on the Ory Cloud network. This includes users signing up for or logging in to applications, services acting on behalf of users, and devices and robots performing authenticated actions. (We will publish some additional details on how exactly this is metered)
g
Thanks, Did I get it right that ANP = MAU? To be frank, it removes the main reason why I advocated for Ory Cloud in our org :/
(the link you provided didn't work)
f
sorry here is the correct link
ANP will be substantially lower than MAUs in almost all scenarios because it takes the average of daily active users
c
Yeah about this new pricing, we made the decision to go with Ory Cloud because it does not have a limit like this. It may get really expensive for us. Do you already have an idea on how much the overages will be?
f
it's on the pricing page - $0.03 per additional ANP and month
I fully appreciate that you would prefer us to not charge based on users or devices, but please understand that as an infrastructure provider we have to charge based on consumption. As for the rationale: we really didn't want to charge per API call when it comes to authentication because we don't want to incentivize compromises like fewer session checks, longer session durations and so forth for cost optimization - but also didn't want to go with MAUs which punishes you for single exceptional days/events. Reach out via DM if you'd like to discuss more, please, I'd be keen to understand your scenarios and constraints!
g
a couple of points here: 1. not sure why price per user is higher in Pro vs. Business (now that I'm re-reading it, you may want to make it clearer what I get for the money, instead of "+20k users" it could be better to say "NNk users") 2. Why do you use new wording instead of saying DAU? 3. At this point it makes much harder to compare Ory Cloud with SuperTokens (different price metrics, etc.; previously it was an easy win for Ory)
f
that is great feedback, thank you 1. we will clarify - thx! 2. this is because we want our pricing to scale to IoT and machine-to-machine use cases - Ory isn't only useful for consumer-facing auth 3. yes, I appreciate that
👌 1
g
regarding p.2, it seems like I didn't understand the metric then is there a place where I could read about it? maybe it would be helpful to make it more discoverable for other users too?
f
we're creating this additional documentation right now and will share it when it's done - including details on measurement & calculation!
g
thanks, appreciate it!