rConfig Automate Add-On Agreement
Version 1.0 — Last Updated: 17 November 2025
This rConfig Automate Add-On Agreement ("Agreement") is between OS Informatics Limited T/A rConfig ("rConfig") and the customer identified in the applicable Order, SOW, invoice, or Automate service description ("Customer"). This Agreement governs Customer's use of the rConfig Automate service across all rConfig editions (Core, Pro, Enterprise, Vector), as applicable.
By purchasing, accessing, or using rConfig Automate, Customer agrees to be bound by this Agreement.
This Agreement incorporates by reference:
- the rConfig Master EULA for the edition in use (Core/Pro/Enterprise/Vector),
- any Statement of Work (SOW) issued under Automate,
- the rConfig Privacy Policy and Data Processing Addendum (DPA).
In the event of conflict: SOW → Automate Agreement → Edition EULA → Website Terms.
1. Purpose of rConfig Automate
rConfig Automate is an advanced customisation and automation service that provides:
- bespoke scripts, workflows, integrations, or platform extensions;
- custom device drivers or parsing logic;
- automated procedures (backup, compliance, config change workflows);
- custom API integrations;
- environment-specific adjustments;
- optional deployment, training, and documentation.
Automate is delivered through a combination of:
- professional services,
- custom-developed code or workflows,
- and configuration of the Customer's licensed rConfig environment.
Automate is not a standalone software licence.
2. Licence & Ownership
2.1 Use of Deliverables
rConfig grants Customer a perpetual, non-exclusive, non-transferable licence to use any Automate deliverables (scripts, workflows, integrations, etc.) solely within Customer's own rConfig deployment.
If Customer is a Vector MSP:
- Deliverables may be used only to support End Clients under Customer's Vector licence,
- but may not be provided to End Clients as standalone tools or products.
2.2 Ownership
Unless explicitly stated in an SOW:
- rConfig retains ownership of all Automate deliverables;
- Customer receives a use licence only;
- rConfig may reuse non-Customer-specific improvements, patterns, or modules.
2.3 Customer-Specific IP
If Customer provides proprietary code, data models, policies, or unique business logic:
- Customer retains ownership of those inputs;
- rConfig will only use them to deliver Automate services.
3. Scope of Automate Services
Automate may include:
- custom automation logic;
- parsing, normalisation, or compliance rules;
- custom drivers or connectors;
- reporting or workflow extensions;
- custom API endpoints;
- operational tooling or procedures;
- environment-specific deployment assistance.
Automate does not include:
- general-purpose professional services outside the agreed scope;
- ongoing managed services;
- modifications to core rConfig products beyond supported extension points;
- 24/7 monitoring or incident response;
- custom services for End Clients unless Customer is licensed under Vector.
All deliverables and timelines are defined in the SOW or order form.
4. Support & Maintenance
4.1 Standard Support
Automate deliverables are supported under the same Support plan as Customer's rConfig edition ("Support"). Support covers:
- break/fix issues directly related to Automate deliverables;
- clarifications and usage guidance;
- adjustments required due to minor version updates.
4.2 Out-of-Scope Support
Support does not include:
- major rewrites due to Customer infrastructure changes;
- redesigns caused by Customer policy changes;
- modifications to accommodate unsupported environments;
- new features or workflows.
These may be purchased under a new SOW.
4.3 End-of-Life
If a customisation becomes incompatible due to:
- deprecation,
- architecture changes,
- new rConfig major versions,
then updates may require a new Automate engagement.
5. Customer Responsibilities
Customer agrees to:
- provide accurate requirements, network examples, and test environments;
- make knowledgeable personnel available;
- maintain backups of configuration data;
- ensure access to required systems;
- implement security best practices for custom workflows.
Customer is solely responsible for:
- how Automate workflows are executed internally;
- operational risk decisions;
- local deployment and approval policies.
6. Payment Terms
Fees for Automate are:
- defined in the Order or SOW;
- due within 30 days unless otherwise specified;
- non-refundable once work has commenced.
Time-and-materials SOWs are billed monthly.
Failure to pay may result in suspension of Automate work or Support.
7. Confidentiality
Both parties agree to maintain confidentiality per the rConfig Master EULA and DPA.
Where Automate deliverables touch network data or infrastructure details:
- Customer data remains Customer's property;
- rConfig will treat all such data with strict confidentiality.
8. Warranties & Disclaimers
8.1 Limited Warranty
Automate deliverables will function materially as described in the SOW for 30 days after delivery.
8.2 Exclusions
Warranty does not cover:
- changes made by Customer or third parties;
- changes required due to Customer infrastructure or topology shifts;
- usage outside documented instructions.
8.3 Disclaimer
Except for the above limited warranty, Automate services and deliverables are provided "AS IS".
9. Limitation of Liability
Liability is limited to:
- the amount paid for the Automate engagement in the 12 months prior to the claim.
Neither party is liable for indirect or consequential damages.
10. Term & Termination
This Agreement:
- begins when Customer purchases or accesses Automate,
- continues until Automate services are delivered and accepted,
- and is superseded only by the associated SOW.
Upon termination:
- Customer retains the use licence for all delivered Automate components;
- unpaid fees remain due;
- rConfig has no obligation to deliver incomplete work unless paid for.
11. Governing Law & Jurisdiction
As per the rConfig Master EULA:
- Governing law: Republic of Ireland
- Jurisdiction: Irish courts
12. Definitions
- "Automate" – a customised automation and integration service, including custom code, workflows, and tooling.
- "SOW" – a written Statement of Work describing deliverables and scope.
- "Deliverables" – any scripts, integrations, workflows, configurations, or materials produced under Automate.
- "Customer" – the entity purchasing or using Automate services.
END OF AGREEMENT