Clarity from the start
We set out ownership of deliverables, source code and licenses in your agreement before work begins, so there are no surprises.
You own
Custom deliverables and source code built for your project (after full payment), plus your business data, files and information.
We retain
Our pre-existing tools, templates, libraries, frameworks and methods, with the rights you need to run what we deliver.
Third parties
Software, platforms and services stay under their own license terms, identified and agreed with you before we build.
Who owns what
| Item | Client | RobotizeLab | Third party |
|---|---|---|---|
| Custom workflows, scripts and configurations | ✅ Owns | – | – |
| Custom source code | ✅ Owns | – | – |
| Documentation and reports | ✅ Owns | – | – |
| Business data and files | ✅ Owns | – | – |
| Reusable tools, templates, libraries and know-how | Right to use with the solution | ✅ Owns | – |
| Software platforms, APIs and open-source components | Licensed to you where practical | – | ✅ Owns |
Our ownership terms
Deliverables and Intellectual Property Ownership
Upon receipt of full payment for the applicable project, the client owns the custom deliverables created specifically for their project, including agreed automation workflows, custom scripts, project-specific configurations, documentation, and reports.
RobotizeLab retains ownership of its pre-existing intellectual property, including reusable tools, templates, libraries, frameworks, development methods, and general know-how.
Where RobotizeLab' existing technology is incorporated into a deliverable, the client receives the necessary rights to use, operate, and maintain it as part of the delivered solution, subject to applicable third-party licensing terms.
The client retains ownership of their business data, files, and information. Specific delivery, access, and handover arrangements will be agreed upon in the project agreement. See how we handle data.
Source Code and Handover
Upon receipt of full payment for the applicable project, RobotizeLab will provide the client with the source code for custom automation solutions developed specifically for their project, together with the agreed documentation and deployment instructions.
Ownership of custom-developed source code will transfer to the client in accordance with the intellectual property terms of the project agreement.
RobotizeLab retains ownership of its pre-existing code, reusable components, libraries, frameworks, templates, and development tools. Where these are incorporated into the delivered solution, the client receives the necessary rights to use and maintain them as part of that solution, subject to applicable third-party licensing terms.
Credentials, passwords, and sensitive access information will be transferred separately through an appropriate secure method.
The client may maintain, modify, or appoint another service provider to maintain the delivered automation, subject to applicable third-party licensing terms and any separate support agreements.
Software Licenses and Third-Party Services
Any third-party software, platforms, hosting services, APIs, plugins, or subscriptions required to develop, deploy, or operate the automation will be identified and agreed upon before implementation.
Where practical, required licenses and subscriptions will be purchased and held directly by the client in their own business name and accounts, ensuring the client retains control over their software and associated services.
RobotizeLab can assist with selecting, purchasing, configuring, and managing licenses where requested and agreed upon.
Any licenses or subscriptions held by RobotizeLab will be clearly identified, including associated costs, renewal arrangements, usage restrictions, and responsibilities for ongoing payment.
All third-party software, open-source components, and services remain subject to their respective licensing terms and conditions. Ongoing subscription and licensing costs will be the client's responsibility unless otherwise agreed in writing.
RobotizeLab will not introduce additional paid software, subscriptions, or third-party services without the client's prior approval.
Confidentiality and Client Data
We treat your business information, processes, credentials and data as confidential and use them only to deliver the agreed work. Confidentiality obligations, including any non-disclosure agreement, are set out in the project agreement.
At the end of the project, or on request, data held by RobotizeLab is returned or securely deleted, as agreed in writing.
Documentation and Knowledge Transfer
Each project includes the documentation agreed in the project agreement, which may cover process descriptions, configuration details, deployment and run instructions, and support contacts. Training or a handover session for your team can be included where agreed.
Acceptance and Change Requests
Deliverables are reviewed against the agreed requirements and acceptance criteria before go-live. Changes to scope, systems or requirements after sign-off are handled through a written change request, with any impact on cost or timing agreed before work proceeds.
Support, Maintenance and Warranty
Support, maintenance and any defect-correction period after go-live are described in the project agreement or a separate support agreement. See support expectations.
Portfolio and Reference Use
We will not name you, show your data or share project details publicly, including as a case study or reference, without your written permission.
How handover works
Accept
You review and approve the deliverables against agreed criteria.
Pay
Ownership of custom deliverables transfers on full payment.
Hand over
Source code, documentation and instructions are delivered.
Secure access
Credentials are transferred separately by a secure method.