Verkada licenses are co-termed to a single expiration date even if you have multiple product types. The combined expiration date is still the weighted average of the individual licenses claimed into that organization. Each product is weighted by the MSRP of the license cost for that product.

For example, if an organization has 2 licenses:

Because the camera license MSRP is US$199 and the air quality sensor license MSRP is US$249, the co-termination date would be calculated as:

Assuming the 2 licenses were bought on the same day, the co-term expiration date would be 771 days from the start of the license. If you compare that to the 730 days in the camera-only example above, you see that the co-term expiration date is at a future time. This is because Verkada Air Quality Sensor licenses are more expensive than camera licenses and, therefore, are given more weight in the co-term calculation.

Verkada sells 1-, 3-, 5-, and 10-year licenses. When you add a license to an existing organization, the co-terminating expiration date is extended for all of your devices, accordingly.

Example scenario: You originally purchased 10 x 1-year camera licenses. Upon purchase, you have 10*12 = 120 camera months.

4 months into the license term, you decide to purchase 3 x 1-year camera licenses. Immediately prior to purchase, you have 10*8=80 camera months.

After purchase, you have extra credit of 3*12=36 camera months for a total of 80+36=116 camera months. Verkada automatically applies those 36 camera months for your new 13 camera organization.

So with this new purchase, your organization's expiration date moved forward by 0.92 months.

In this way, your organization only has a single co-terminating expiration date, avoiding the confusion associated with multiple expiration dates.

Some customers want to manage multiple renewal dates for their company. For example, a company with regional budgets may want to track a renewal date for each region separately to match their budgeting cycles.

Verkada Command's License Manager tracks a single co-terminated renewal date for an organization. Therefore, customers who want to manage different renewal dates need to create multiple Command organizations, where users can be members of multiple organizations. Admins can create different organizations to match the way they want to manage licenses.

For example, the company that wants to have regional tracking would set up each region as an organization and claim license keys and devices for each one separately. Command users can easily switch between organizations to view different sites, and permissions can be synced via System for Cross-domain Identity Management (SCIM) or other identity management tools.