Eyeshot's licensing model combines both SAAS and perpetual licensing, offering developers several advantages by introducing new dynamics for both development and runtime usage. Below is an overview of the key features:
- Developer-specific licenses: Each developer must have their own license.
- No runtime licensing: Runtime applications do not require a license.
- Royalty-free redistribution: The license allows for royalty-free redistribution of applications that use Eyeshot.
Developer
A Developer is defined as anyone who uses or interacts with the Eyeshot product, either directly or indirectly, when a debugger is attached. This includes tasks such as coding or debugging any application that integrates Eyeshot.
Installation on Unlimited Devices
Developers are allowed to install Eyeshot on an unlimited number of devices. However, only one device at a time can be used with a single license.
Internet Connection
An internet connection is always required for development purposes. A grace period is allowed for temporary disconnections, but extended offline use is not supported.
Build Server
If a server is only used for generating builds without any active development work, a separate license is not required.
Transfer of License
Licenses can be transferred from one developer to another, within or outside the organization, using the license Assign and Revoke buttons in the devDept website account. This allows team flexibility, ensuring that the license can be reassigned as development roles or team members change.
Trial License
Eyeshot can be evaluated for a 30-day trial period. During this period, users can submit unlimited support requests through the ticketing system, with a 72-hour response time.
Subscription Expiration
If the subscription is not renewed, all development-specific features will be blocked. However, the runtime usage of the product will remain perpetual and continue without requiring further payments.
Comments
Hello Eyeshot team,
We are reviewing our software subscription, and I need some help understanding the implications of letting it expire based on the following term:
I understand the runtime part is perpetual. However, I'm concerned about the "development-specific features". Could someone confirm if this means we would no longer be able to debug our applications using the tool if we don't renew? Is debugging considered one of the features that gets blocked?
Any insights would be greatly appreciated.
Thanks!
Hello Pablo,
Yes, debugging is blocked if the subscription is not renewed.
Please sign in to leave a comment.