Licensing and Support


How does licensing work?flowscholar

Licensing is based on the number of concurrent users (similar to floating licences) product tiers (packages), storage needs (for on-premise deployments), and a number of other factors. To learn more, please contact our sales team.

How does concurrent user licensing work?flowscholar

The number of concurrent users is defined as the number of user accounts that are signed-in and active at any given time. Similar to floating licenses, concurrent licenses are consumed by active users and released after a period of inactivity. Note that many more users can be registered in the system because the licensing limits apply only to the number of concurrent active users.

PathcoreScholar: All users, whether a Student, Educator, or otherwise, will consume a concurrent license when accessing the platform.
Is there a limit on the number of users?flowscholar

No. Pathcore supports an unlimited number of registered users and concurrent users.

What is the cost of licensing?flowscholar

There are a variety of package options to choose from we don’t want to charge you for something you will not be using so it is best to contact our sales team and let us help put together a package that works with your needs.

What is included in the cost of licensing?flowscholar

The limited license to use the software in a deployed environment as well as a dedicated account manager to support your onboarding with Pathcore. Bug fixes and regular product updates are also included in all current support contracts.

What is included in the support and maintenance?flowscholar

Technical support, product updates, bug fixes, and access to a dedicated account manager.

How often do you update the software?flowscholar

We update the product frequently.

  • Major releases (e.g. 3.0, 4.0) are launched infrequently and typically include many new improvements.
  • Minor releases (e.g. 3.1, 3.2) provide incremental improvements and are targeted for quarterly release.
  • Patch releases (e.g. 3.01, 3.02) are released as needed, usually to address critical issues and/or bug fixes in between minor and major releases.