๐ BIG NEWS ๐ โฆ Avo 4 has officially SHIPPED โฆ ๐ the beta is over, 4.0 is here โฆ ๐ ๏ธ build admin panels, dashboards & internal tools at light speed โฆ โญ you are visitor #1,136,366 โฆ ๐ tell a friend โฆ best viewed in Ruby on Rails โฆ ๐ click here to see what’s new โฆ
Licensing
How many licenses do I need across environments and URLs?
One license covers one production app. You don't need a separate license for your staging, testing, or preview environments.
I often think of it as... just having in-house designer, a front end, and a full stack. And AVO just gives you this with a very nice DSL where you just save time. So that's what's nice about it. Every time you use it, you save time
TL;DR;
- You can have many staging and test URLs. As long as they are not real production apps and don't serve real customers.
- Your application can have multiple instances as long as the entry-point is one URL.
We're developers too and we understand that you might want to deploy your app to other environments and URLs before pushing to production.
Those staging environments might have the Rails.env set to production, and that's fine. You should add those URLs on the license page and everything will be ok.
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.
What about multiple instances of the same app?
If that application is hosted on a kubernetes swarm or some similar setup (so there are multiple running instances) but serves off of one URL to one category of customers, that counts as one production environment.
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 book a call.
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 book a call and we'll sort it out with you.