What's the best practice handing over UiPath code

We are trying to figure out how to handover our client the code we developed. We have tested the code successfully in our Orchestrator platform - it’s time for us to pass it to client. Our client will have their own Orchestrator and Robot agent server. One of the options we were thinking of is to zip all the files from UiPath Studio and have client open on their Studio and publish wherever they want to. Problem with that - it will not have all the project dependencies. As a second option, we can publish it in our local folder and provide them nupkg file - problem with that - client will not be able to modify the code if needed.
What’s the best practice when it comes to delivering client the code? I would greatly appreciate your input and advice. Looking forward to hear from you soon.

1 Like

Some companies use a repository for storing and versioning code (e.g. github, bitbucket, svn, etc.). This is very convenient for getting what was originally written, as the uploaded packages change some of the information in order for it to run in Orchestrator.

1 Like

Use of SVN is obviously good idea for repository. However, wanted to find out how companies deliver to client. Do they provide the whole raw codes or published nupkg? What’s the best practice?

1 Like

Sending the package file and code wouldn’t hurt. Especially since the client will want to see exactly what the code is doing anyway. That way the Client can decide how to handle it.

1 Like

Mostly company let the developers develop the code in their own infrastructure - be it via Citrix or providing the laptop. So that the company code relies within their control.

In your case , it will depend on the client , if they want to future enhance the bot with their developers , they would require source code.

It would be good to provide both the nudget and the source code. And as far as the dependencies are concerned - so whenever you are delivering the project , it would be your responsibility that the project run atleast once in client infrastructure… For that anyways you have to set up the dependencies.


hi @Akimalam ,
When as you are the vendor , you have several ways to manage your client ,

If , you and your customer have strong enough to manage package control from GUT/TFS/SVN , you can use those to deliver it to your customer

Considering development codes , its your decision to provide the development code to your customer , (when they aware and if they change codes or modify the development without knowing your , your trouble shooting will be a big problem)

So , if you have several options more …

Bring your project to deliverable media and run it on your customer end and publish it to customer’s Orchestrator , so they don’t need your development code when u publish it to their Orchestrator.

of cause there may have some dependency , for that you can have separate folder location and store your all dependencies and other for the relevant (by using Manage Sources)
send them all dependencies and create a common location on your customer end (like file server) to keep all data and access all via studio as well as robots.

As development company best practices , they wont provide development codes for the customer(but it will be depend that how your agreement sign on) , if not your company have right to keep source code, its development company intercultural property .

1 Like

Thank you all for your inputs - I appreciate it.

1 Like