Yes, a license and the associated developer seats can be used across multiple projects within your company. There is no limit to the number of projects Scheduler can be incorporated into. However, we kindly ask that you purchase additional developer seats as your team grows. Please contact email@example.com when you need to do this.
The Scheduler Premium license requires you to choose a number of developers. How many should you choose?
You are only required to purchase licenses for developers that will be working with Scheduler’s source code or with Scheduler’s API. If your developers are writing code to initialize a Scheduler, using any of the API hooks documented on the docs page, or writing custom CSS to be applied to the Scheduler, then they will need their own developer seat.
No, each developer represents a seat and is not linked to a specific individual. If one developer leaves a project and a new developer comes aboard, you can reuse the same license for them. We kindly ask that you purchase additional developer seats as the size of your team grows. Please contact firstname.lastname@example.org when you need to do this.
Each commercial license requires a one-time fee. Once you pay this one-time fee, you can perpetually use the version of Scheduler you paid for. You can also perpetually use versions of Scheduler that were released within a year of the date of purchase. Free upgrades, as well as email support, end after the first year but can be extended.
Credit card is the preferred payment methods. ACH and wire transfer are available for larger payments.
After paying with credit card from the purchase page, you will receive an automated email with an invoice and license key information.
The cost depends on when you make the renewal purchase. If you purchase before your license expires, you’ll receive a 50% discount off the base price. If you purchase after your license expires, you’ll only receive a 25% discount off the based price.
The “base price” is defined as the price of the same or equivalent license near the time of your license’s expiration date.
If you build sites or applications with Scheduler for companies other than your own, these are considered “clients”.
Do you allow your clients to edit your app’s source code after you hand it off to them?
If you DO allow source code editing, then you must purchase an individual license for each client. The type of license you must purchase depends on the nature of your project. The license is purchased and managed by you, but is owned by your clients. Thus, you cannot reuse the same license across multiple clients. If you envision using Scheduler in a multitude of different client projects, an OEM license might be more appropriate.
An OEM license allows you to include Scheduler in an unlimited number of client projects, and allows your clients to continue development.
It also allows an unlimited number of developer seats.
An OEM license requires a one-time fee. Please contact email@example.com for more information.
Yes, but the instructions depend on the license of your project.
If your project is licensed under GPL, then you can bundle Scheduler directly into your source code and hardcode the GPL license key. Most open source projects are not GPL however, because GPL is a license that disallows inclusion of your project in closed-source projects.
If your project is not GPL, then the procedure is a bit more complex, though still manageable:
- Do not include Scheduler directly into your repository’s source code. Instead, use a package manager such as Bower or NPM to reference Scheduler as a dependency and have an install script initiate the download.
- Do not hardcode any type of license key. Instead, leave the
schedulerLicenseKeyproperty undefined, as Scheduler is technically considered “unlicensed” at this point. This will cause a warning message to show on the Scheduler widget.
Provide a convenient way for the developer installing your app to enter their own license key. Either do this via a prompt in an install script, or through a well-documented config file.
For questions about more complex scenarios, please contact firstname.lastname@example.org