One license per URL
"How many licenses do I need if I have multiple staging environments?"
You don't need a license for each staging/testing subdomain of one application.
My team uses AVO and I must say it is very good and has helped us Build Faster and save time. This is a must-use by engineering teams worldwide. Awesome tool @adrianthedev
TL;DR;
- You can have many test/staging URLs. As long as they are not real production apps and don't serve real customers.
We're developers too and we understand that you might need to deploy your app in other URLs before pushing to production.
This does not cover multi-URL tenancy scenarios where you have a subdomain or a custom URL for each user account. That requires a different type of license and if you'll write to us here we'd love to share more details.
Check out the related One production environment FAQ page.
Examples
Single URL licensing
Your production environment is https://example.com. You run a few staging servers at, for example, https://staging.example.com, https://pr-182.example.com, https://new-feature.example.com, or https://development.example.com
For this case you don't need multiple licenses. One is enough as it covers https://example.com as the production URL.
Multi URL licensing
Your production environment is https://example.com. You expose the same app to customers through multiple subdomains or paths at https://accountants.example.com, https://lawyers.example.com, https://doctors.example.com, or https://drivers.example.com/
For this scenario you need a license for each subdomain as it caters to different types of customers.
Please get in touch.
Multi URL licensing
Your production environment is https://example.com. You have subdomain multi-tenancy like so https://adrian.example.com, https://paul.example.com, https://john.example.com, or https://cody.example.com/
For this scenario you need special licensing.
Please fill out this form and we will get in touch with you.