Hi everyone, can someone explain what is the difference between developer license and production license? Why we need to have licenses in the same project?
1 Like
Hi @JoyceP
- Developer License:
- This type of license is used during the development phase of a project.
- It allows developers to create, test, and debug automation workflows using UiPath Studio on their local machines.
- Typically, a developer license is free and comes with certain limitations, such as restrictions on the number of attended or unattended robots that can be connected, and limitations on the runtime environment.
- Production License:
- This type of license is used when deploying and running automation workflows in a production environment.
- It is required to execute robots in a production environment, whether the robots are attended (executed with human interaction) or unattended (executed without human interaction).
- Production licenses often have different pricing models and terms compared to developer licenses.
Why Both Licenses in the Same Project:
- During the development phase, developers use their developer licenses to build and test automation workflows on our local machines.
- When it comes time to deploy the automation to a production environment, production licenses are used to run the robots in that environment.
- Having separate licenses for development and production ensures that the platform is used appropriately in each context and allows for proper licensing management.
Hope you understand!!
Regards,
1 Like
Hi,
A developer license is used during the development phase of an automation project. It allows developers to create, test, and debug automation workflows within Studio. This license is typically used in non-production environments and is focused on the development and refinement of automation processes.
On the other hand, a production license is essential when deploying and running automation workflows in a live or operational environment. This license is associated with the Orchestrator, which helps manage and schedule automation jobs in a centralized manner. It’s required when you want to execute your automation processes on a production server or interact with production-level systems.
Having both licenses in the same project allows for a smooth transition from development to production. Developers use the developer license to work on and perfect the automation workflow, and once it’s ready for deployment, the production license ensures it can run seamlessly in the live environment managed by the Orchestrator.
Thank you for your response. Are these two licenses purchased separately? Or does a developer’s license come with the purchase of a production license?
1 Like
Thanks for your reply!
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.