We’re still under the $2M/year limir but hope to reach it next year!! So I just want some explanation on your pricing. We have a staging/prod instance with around 20/30 functions each (as they are the same) right now.
And the dashboard, right now we see only 2 instances. So Serverless v4 is going to force me to pay money only if I launch a new project like dev or another backend with staging/prod, right?
Is that correct ? Is there a case where I need to pay more credits because I have too many functions on one instance?
if your org is under the $2 million ARR limit, you do not need to purchase credits to cover your V4 licenses and you can deploy as many
I had exactly the same initial thought - and as we run an agency-type modal where we have multiple clients - we have maybe a dozen stacks, each with at least a dev&live stage.
But seems we are both wrong, and apart from having to register and issue licence keys to our teams, can just go on as we have been (and incidentally telling anyone who’ll listen how good Serverless is).
For example, if I start a simple project for learning purposes, I can create multiple services for my app. However, how can I demonstrate that this application is just for testing before I build something “real”?, I wanna to do some stress test of API, for example.
Hi folks. There is no need to issue license keys for each service. You can just use serverless login and authenticate via browser. For headless systems such as CI/CD you can use the access keys as well and add them to your CI/CD environment as an environment variable SERVERLESS_ACCESS_KEY.
Needing to pay for V4 licenses is 100% opt in and organisations needs to decide that they are now going to pay for each unique service instance they deploy and ensure that the option is toggled in when they create their subscription and add payment details.
Anyone else can just log in on CLI or use access keys.