17 Apr

Setting the Record Straight on Adobe Connect Licensing

At RealEyes we’ve found it is absolutely crucial that Adobe Connect buyers understand the available licensing structure or have a resource on hand that can be used to answer questions that may come up. In some cases, we’ve found that the licensing parameters were never properly explained in pre-purchase discussions, and the resulting deployment may not be as beneficial to the end user as they initially thought. Because there is no documentation available that goes in-depth about the licensing models (how they work, limitations, advantages, etc.), please consider this post as a reference point.

What we will not cover in this post however is pricing. Since the pricing is dependent on which vertical you fall into (Commercial, Education, Government, Non-Profit, etc.). Pricing is something that should be discussed with your vendor. Please feel free to contact us if you have question about pricing.

First and foremost, it is important to point out that Connect is available in a few different flavors:

  1. On-Premise (Enterprise) – This deployment is typically hosted on your server(s), and behind your firewall. Since it is a server platform product, it is subject to perpetual licensing. This means that the server software itself and all licensing must be purchased initially, but thereafter (year 2, year 3, etc.) only the Maintenance & Support is required to be purchased annually. M&S is required at time of purchase, and is normally 20% of the total Connect product purchase. In some cases, special exceptions and/or agreements, contracts, etc. have been established and agreed upon by the end user(s) and Adobe, so they may differ. Please visit the Adobe Platinum Maintenance & Support homepage for further details. Please also note that On-Premise deployments can also be a Managed Service offering; meaning that the deployment is an On-Premise installation that is managed by another company.
  2. Hosted (SaaS) – This works is also known and referred to as a Software as a Service (SaaS) model. In this case, your Adobe Connect deployment is hosted on Adobe’s reserved server clusters. That being said, you are behind Adobe’s firewalls. In some cases, having your account Hosted may or may not be the best solution. It is always best to first check with your IT Dept., Systems Admin, etc. to see what may or may not be a requirement. Since there may be several compliance regulations that your institution may need to adhere to, or if you may need full integration with other pre-existing server based products, Adobe’s servers may be able to suffice, but those kinds of questions cannot be answered here and now, as the scenarios tend to vary greatly. Hosted account purchases through resellers typically include baseline standard Adobe Connect Help and Support.
  3. Adobe Connect Managed Services (Enterprise & SaaS) – This deployment is hosted on dedicated server(s) and managed by Adobe Systems. It includes all of the benefits of an Enterprise deployment, (adhering to your firewall settings, LDAP and/or AD integration, etc) but since it requires no internal network administration, it feels like a SaaS deployment. It is a perpetual licensing model where all licensing must be purchased initially, and must be renewed annually. In some cases, special exceptions and/or agreements, contracts, etc. have been established and agreed upon by the end user(s) and Adobe, so they may differ. Please contact us directly if you have questions about the Adobe Connect Managed Services option. An overview on Adobe Connect Managed Services can be viewed and/or downloaded (.pdf) here.

Note: On-Premise deployments can also be managed by other 3rd party companies have various managed service offerings.

Next, are the available Modules for Connect and their correlating licensing models.

Training Module

  • Concurrent Learner – These licenses are indicative of the Training Module within Connect, and therefore will enable it. With this licensing model, it enables Connect to deploy Curriculums and/or Courses on the system. Any enrolled users will have their results tracked via the lightweight LMS that Connect offers. The concurrency portion translates to having the ability to have up to the total amount of licenses purchased online at any given time having their results tracked systematically. For instance, if you purchase 100 Concurrent Learner licenses, you have the ability to have up to, but no more than, 100 enrollees online concurrently having their results tracked. Unlimited Curriculums and/or Courses can be created, and you can enroll an unlimited amount of users, but you are capped at how many concurrent licenses you have. So if you have 1,000 enrollees and only 100 licenses, only 100 enrollees can be tracked at any given time, and the remaining enrollees will have their results tracked once the first enrollees have completed the training and logged out of the system.

Meeting Module

  • Concurrent User: These licenses are indicative of the Meeting Module within Connect, and therefore will enable it. With this licensing, the total number of licenses you purchase will be the total number of users that can be online in a live meeting at any given time, either hosting or attending a meeting. These licenses do not have to be assigned or applied to named individuals, they can be generalized. However, the concurrency principal described above is still relevant in this case. This model works as a “licensing pool” per se.
  • Named Host: These licenses are also indicative of the Meeting Module within Connect, and therefore will enable it. With this licensing, a Named Host can host a Connect Meeting at any given time of up to 100 attendees. The licensing model itself refers to a named, specific user (cannot be a general login) that is in the Meeting Hosts System Group. For instance, if you purchase 15 Named Host licenses, you have the ability to place up to 15 people in the Meeting Hosts System Group. Each of the people in that group can have up to 100 attendees (internal users and/or external users, etc.) in any Meeting Room that they’ve created. Each Meeting Host Group member can run any one of their rooms at a given time and they must be present in the room for it to have full functionality.  This licensing model is best used for frequent usage in Meeting Rooms, or also very adequate for webinars that will not exceed 100 attendees. This is currently the most popular licensing model.

Note: Named Host and Concurrent User cannot co-exist on any Connect deployment, as they are both representative of the Meeting Module

Content Module

  • Content Publish: Also known as Author licenses. These licenses are indicative of Content Module within Connect, and therefore will enable it. This will give anyone placed in the Authors System Group the ability to publish Content to Adobe Connect for on-demand access. For instance, if you purchase 15 Content Publish licenses, you have the ability to place up to 15 people in the Authors System Group.

Note: Content Publish licenses are not applicable in On-Premise Connect deployments, as the Content Module is automatically enabled because the Content will be directly published to your server*

Available add-on Modules for Adobe Connect.

  • Seminar Rooms: Typically used for webinars, large meetings, etc. A Seminar Room compared to a Meeting Room is like an auditorium compared to a classroom. Seminar Rooms are meant to handle a higher amount of connections. They are priced on a per seat basis. For Hosted deployments, there is a minimum of 200 seats, and a maximum of 1,500 seats. Further, a 30 Day Seminar Room can also be purchased and added for a “one off” event(s), and will be valid for 30 days after implementation. The same seating rules (200 minimum, 1,500 maximum) apply for 30 Day Seminar Rooms.

For On-Premise deployments, it is a minimum of 200 seats as well, and there is no set maximum. It is very important to note that the maximum amount of connections into one Adobe Connect Server is 500. If a higher number is needed, an additional Connect Server (or servers, depending on the account’s capabilities, additional licensing, etc.) is recommended for load balancing.

  • Events Module: Also known as Adobe Connect for webinars.  The Events Module will give the ability to create custom landing pages tied to any Meeting Rooms, Seminar Rooms, or Virtual Classrooms. When enabled and configured, the Events Module will automatically register and track all attendees that register for the event itself, and report the data into Connect. The data can then be downloaded for future follow-ups, etc.
  • WebCast: This is another available licensing model/add-on that is for large events (up to 80,000 attendees). Purchasing and enabling this add-on is also for “one off” event(s), and has set pricing for all verticals. WebCast has the ability to manage all facets of large events, from registration, to post-event follow up and all tracking capability. For further information and pricing, please contact your reseller directly.

Feel free to check out the Adobe Connect Homepage, it is a great resource when you have questions about Connect.

If you have immediate questions contact us directly.

Share this

Comments (5)

November 2, 2012 Reply

Hi there,

I'm Eddie from Malaysia. I'm interested in Adobe Connect to purchase Adobe Connect On premises version for eLearning/Training. Are you able to quote?
Also are you able to give me the link to download 30 days eval/trial version?

Kathy perkins
May 11, 2014 Reply

What are the differences, pros and cons of event vs, webcast for audiences over 400 but less than 1000

    Jeff Dicker
    May 12, 2014 Reply

    Hi Kathy,
    Thank you for the inquiry.

    The Adobe Connect Webcast offering has a 600 attendee minimum, so for less than that the best solution would be to leverage the Seminar Room licensing model. The main differences between the two is that the Adobe Connect Webcast has its own licensing and pricing model, and also is meant for one off events that don't last longer than an hour or two.

    With the Seminar Room licensing model on the Adobe Connect, it is native to your account and can be used at any time for as long as needed.

kimberly Murray
October 30, 2017 Reply

The article does not really explain the enterprise versus the nonenterprise and why it is beneficial to have AdobeConnect through an enterprise.

Thank you

    Jeff Dicker
    October 31, 2017 Reply

    Hi Kimberly,
    Thank you for your comment.

    This article was written to clarify the differences in available Adobe Connect licensing models since they function the same; whether Hosted or On-Premise. In regards to features, benefits, etc. for each, that is always something to take into consideration when evaluating the the functionality for each and how it will work for the customers, end users, etc. The main reason why Adobe offers multiple deployment options is based on organizational requirements. So, it is up to the user to see what, if any, of the offerings meet their needs both initially and long-term. Regardless, I will give you my opinion on the more important benefits of each, but choosing what is best for your needs is entirely up to you.

    one of the more essential benefits of having a Hosted (SaaS) Adobe Connect account is that Adobe maintains everything (updates, server maintenance, etc) and the organization's end users simply utilize the product through the web UI. This is widely considered one of the larger benefits because smaller organizations around the world may not have the infrastructure, man power, etc. to maintain an application of this magnitude in-house. Additionally, Adobe's server up time is 99.99%, and any bandwidth is provided by them.

    With respect to Adobe Connect in an On-Premise (Enterprise) deployment, there are little to no benefits from a product usability standpoint (most users don't see a difference aesthetically or functionally), it's pretty much apples-to-apples in that regard. The largest benefit of an On-Premise deployment is the points of integration. Internal user authentication options such as LDAP can be integrated with On-Premise deployments out-of-the-box, and third party applications may also be integrated with additional development. Since the server is hosted in your infrastructure, it must be maintained internally and Adobe will only support it if/when needed.

    The bottom line is that even though Adobe Connect is available with different deployment options, it's best to know what the requirements are and see which licensing model will meet your needs.

Leave a reply