rConfig Vector Agent, Product Schedule

Version 1.0 Last Updated: 1st January 2026

This Product Schedule forms part of, and is subject to, the rConfig Vector MSP Edition Software Licence Agreement (the "Vector EULA").

Parties and Scope

This Product Schedule ("Schedule") is made between:

OS Informatics Limited, trading as rConfig, a company incorporated in Ireland under company number 751053, with its registered office at 44 Longshore Drive, Jacobs Island, Cork, Ireland ("rConfig"); and

the customer identified in the applicable order, invoice, MSP agreement, or grant letter ("Company").

This Schedule governs Company's use of the rConfig Vector Agent ("Agent"), being the software component installed within a managed network that connects outbound to a Vector Server in order to collect device configuration and to perform configuration operations as directed by that Vector Server.

Relationship to the Vector EULA

This Schedule supplements and does not replace the Vector EULA. All terms of the Vector EULA apply to the Agent as if the Agent were part of the Software, except as expressly varied by this Schedule.

Where this Schedule conflicts with the Vector EULA, this Schedule prevails, but only in respect of the Agent and only where it expressly identifies the provision of the Vector EULA that it varies. The Vector EULA prevails in all cases in respect of confidentiality, ownership of Intellectual Property Rights, the aggregate limitation of liability and the exclusions from it, data protection roles, and the general restrictions on use.

Capitalised terms not defined in this Schedule have the meanings given in the Vector EULA. A reference to a numbered Section is a reference to a Section of this Schedule unless it expressly refers to the Vector EULA.

1. Prerequisite Licence

1.1 Vector Licence Required

The Agent is not separately licensed and is not available on a standalone basis. Company's right to install and operate the Agent is conditional on Company holding, and maintaining in good standing:

a current licence for the rConfig Vector MSP Edition; and
a current, paid Vector subscription or maintenance arrangement.

No separate licence fee is charged for the Agent. The Agent confers no right to install, access, or use any other rConfig product.

1.2 Effect of Suspension or Termination

Where Company's Vector licence or subscription is suspended under Vector EULA Section 6.4, Company's right to deploy new Agents is suspended, and Company must not install any additional Agent until the suspension is lifted.

Where Company's Vector licence terminates, Company's right to operate every Agent terminates immediately, and Section 8 applies.

1.3 No Free or Evaluation Tier

There is no free, community, or Core-tier Agent. Any Agent supplied for evaluation or at no charge is Evaluation Software for the purposes of Vector EULA Section 11.

2. Licence Grant and Permitted Deployment

2.1 Licence Grant

Subject to this Schedule and to the Vector EULA, rConfig grants Company a non-exclusive, non-transferable, non-sublicensable licence to install, operate, and use the Agent solely:

in connection with a Vector Server operated by Company under Company's Vector licence; and
for the purpose of delivering Company's managed service to its End Clients, or for Company's own internal network.

The Agent is licensed as object code only. Company obtains no rights in the source code of the Agent.

2.2 Permitted Locations

Company may install the Agent:

on infrastructure owned or controlled by Company;
on infrastructure owned or controlled by an Affiliate or a Managing Party permitted under Vector EULA Sections 1.3 and 1.4; and
on infrastructure owned or controlled by an End Client, solely within that End Client's network and solely for the purpose of delivering Company's managed service to that End Client.

2.3 Deployment into End Client Networks

Where Company installs an Agent on infrastructure owned or controlled by an End Client, Company must:

hold a written contractual right, from that End Client, to install, operate, update, and subsequently remove the Agent, and to access the host for those purposes;
ensure that the terms required by Vector EULA Section 3.3 extend expressly to the Agent, including the prohibitions on reverse engineering, on removal of proprietary notices, and on use of the Agent other than as part of Company's managed service;
ensure that the End Client acquires no licence, right, title, or interest in the Agent, and that the End Client is not permitted to operate, repoint, copy, redistribute, decompile, or independently configure the Agent;
ensure that the End Client is not given administrative access to the Agent or to its configuration, save to the extent operationally unavoidable, in which case Company remains fully responsible for that access; and
retain the practical and contractual ability to remove or disable every such Agent on termination of this Schedule, of the Vector EULA, or of that End Client's engagement.

Company is fully responsible and liable for every Agent it deploys, wherever installed and whoever owns the host, as if Company operated it on its own infrastructure.

The installation of an Agent on End Client infrastructure does not create any licence, contract, or relationship between rConfig and that End Client, and Vector EULA Section 3.2 applies.

2.4 Restrictions Specific to the Agent

In addition to the restrictions in Vector EULA Section 2.6, Company must not, and must not permit any Affiliate, Managing Party, End User, or End Client to:

configure, repoint, proxy, tunnel, relay, or otherwise cause an Agent to communicate with any endpoint other than a Vector Server operated by Company under its Vector licence;
intercept, decrypt, replay, modify, or inject traffic between an Agent and a Vector Server;
operate an Agent against a Vector Server that is not licensed to Company;
extract, repackage, redistribute, or embed the Agent in any other product, appliance, image, or distribution, save that Company may include the Agent in its own standard deployment images and automation solely for the purposes permitted by Section 2.2;
use the Agent, or any information derived from its operation or its protocol, to develop any product or service that competes with the Software; or
circumvent, disable, or interfere with any authentication, enrolment, certificate, entitlement, or usage-measurement mechanism in the Agent.

3. Entitlement

3.1 No Separate Agent Count Limit

No limit applies to the number of Agent instances Company may deploy.

Company's entitlement is determined solely by the Product Entitlement under its Vector licence, as set out in Vector EULA Section 2.1, measured by managed device count, tenant count, and instance count in aggregate. Deploying additional Agents does not increase that entitlement.

3.2 Devices Reached Through an Agent

Every network device managed, monitored, or configured through an Agent counts towards Company's Product Entitlement in the same way as a device reached directly by a Vector Server. Vector EULA Sections 2.4 and 6.6 apply.

4. Communication and Network Path

4.1 Agent Communication

The Agent is designed to establish outbound connections to a Vector Server only. In its supplied and unmodified form, the Agent does not connect to, transmit data to, or receive instructions from any system operated by rConfig, and does not transmit configuration data, credentials, device data, telemetry, diagnostic data, usage data, or licence-check data to rConfig.

Where rConfig introduces any Agent functionality that would communicate with a system operated by rConfig, rConfig will document that functionality on the Documentation Website, will make it capable of being disabled by Company, and will notify Company not less than sixty (60) days before it takes effect in a generally available release.

4.2 Company Responsibility for the Network Path

Company is solely responsible for:

the host on which each Agent runs, including its operating system, patching, hardening, resource allocation, monitoring, and physical and logical security;
outbound network connectivity, name resolution, proxy configuration, firewall and NAT traversal, and certificate trust between each Agent and the Vector Server;
the availability, latency, and reliability of that network path; and
obtaining any End Client approval required for the necessary network access.

rConfig has no responsibility or liability for any failure, delay, or defect arising from the host, the network path, or any intermediate device or service, and no response target under Vector EULA Section 4.2 applies to any such matter.

5. Credentials and Security

5.1 Local Storage of Credentials

Company acknowledges that the Agent stores device credentials locally on the host on which it runs, in order to authenticate to managed devices, and that the retention period for those credentials is configurable by the operator of the Agent.

Company is solely responsible for configuring that retention period, and must set it to the shortest period consistent with Company's operational requirements. Where Company does not configure a retention period, the default set out in the Documentation applies and Company accepts that default.

5.2 Company Security Obligations

Company must, in respect of every host on which an Agent runs, whether owned by Company, an Affiliate, a Managing Party, or an End Client:

restrict operating system and administrative access to named, authorised individuals on a least-privilege basis;
apply full-disk or equivalent encryption where the host is capable of it, and in any event protect the Agent's local credential store from unauthorised access;
not co-locate an Agent on a host shared with any untrusted workload, or with any workload belonging to a different End Client, unless Company has assessed and accepted that risk in writing;
control the creation, storage, and transfer of backups, snapshots, images, and memory dumps of the host, and treat each as containing credential material;
monitor and log access to the host;
rotate device credentials on a schedule appropriate to Company's and each End Client's risk profile, and immediately on any suspected compromise; and
follow the Agent hardening guidance published on the Documentation Website.

5.3 Disclosure to End Clients

Where an Agent stores credentials belonging to, or granting access to, an End Client's devices, Company must inform that End Client that credentials are cached locally within that End Client's network, and must obtain any approval that End Client's own policies require.

Company must not represent to any End Client that rConfig holds, escrows, manages, or has access to those credentials.

5.4 Allocation of Risk

To the maximum extent permitted by law, rConfig has no liability for any exposure, disclosure, loss, or misuse of credentials arising from:

the compromise, theft, loss, or misconfiguration of any host on which an Agent runs;
Company's configuration of the credential retention period;
Company's failure to meet an obligation under Section 5.2;
the copying, imaging, snapshotting, or backing up of a host by Company, an Affiliate, a Managing Party, or an End Client; or
credentials supplied to an Agent with a level of privilege greater than necessary.

Company's indemnity under Vector EULA Section 10.1 extends to any claim arising from any of the above, including any claim by an End Client.

5.5 Least Privilege

Company must supply each Agent with device credentials scoped to the minimum privilege necessary to perform the configured operations. Where Company supplies credentials with greater privilege, including full administrative or enable-level access where read-only access would suffice, Company does so at its own risk.

6. Versions and Updates

6.1 Updating Is Company-Controlled

rConfig does not update the Agent automatically. The Agent does not self-update, and rConfig has no ability to change, upgrade, or reconfigure any deployed Agent.

Company is solely responsible for deciding when and whether to update each Agent, for testing each update, and for deploying it across its own estate and its End Clients' estates.

6.2 Obligation to Remain Current

Company must:

maintain each Agent on a version compatible with Company's Vector Server version, as set out in the compatibility matrix published on the Documentation Website;
not operate an Agent version that has reached End-of-Life; and
apply any Agent update that rConfig identifies as addressing a security vulnerability within thirty (30) days of rConfig making it available, or within such shorter period as rConfig reasonably specifies for a vulnerability it classifies as critical.

6.3 Consequences of Not Updating

Where Company operates an Agent version that is End-of-Life, that is incompatible with Company's Vector Server version, or in respect of which Company has not applied a security update within the period in Section 6.2:

the Limited Warranty in Vector EULA Section 9.1 does not apply to that Agent;
Support in respect of that Agent is excluded under Vector EULA Section 4.5;
no response target under Vector EULA Section 4.2 applies; and
Company assumes all risk arising from its continued operation, and Company's indemnity under Vector EULA Section 10.1 applies.

rConfig may require Company to update one or more Agents to a specified version as a condition of investigating or resolving any issue.

6.4 Compatibility

rConfig will use reasonable efforts to maintain a documented compatibility window between Agent and Vector Server versions, but gives no warranty of forward or backward compatibility beyond the versions stated in the compatibility matrix current at the relevant time.

Company acknowledges that an Upgrade to the Vector Server may require Company to update Agents across its own estate and its End Clients' estates, that this may require End Client change windows, and that Company is solely responsible for planning, scheduling, and executing that work.

7. Support, Warranty, and Operational Risk

7.1 Support

The Agent is supported under Company's existing Support entitlement for the Vector MSP Edition. No separate Support entitlement, coverage, or response target applies to the Agent.

Vector EULA Sections 3.4, 4.2, 4.3, 4.5, and 4.9 apply to the Agent. Company must complete first-line and second-line triage of any Agent issue, including confirming host health, network path, and credential validity, before escalating to rConfig.

7.2 Warranty

The Limited Warranty in Vector EULA Section 9.1 applies to the Agent, measured from the date of Delivery of the Software, and is subject to the exclusions in Vector EULA Section 9.2 and to Sections 4.2, 5.4, and 6.3 of this Schedule.

7.3 Operational Risk

Company acknowledges that the Agent connects to, authenticates against, reads from, and may write configuration to production network devices, including devices belonging to End Clients, and that incorrect configuration or inappropriately scoped operation of an Agent is capable of causing loss of device connectivity, service outage, configuration loss, or credential exposure, potentially across more than one End Client.

Company is solely responsible for how, when, where, and against which devices each Agent operates, and for all consequences of that operation. Before enabling any configuration-changing operation through an Agent against a production device, Company must test in a non-production environment, apply its own and the relevant End Client's change management processes, and confirm that a current backup and a rollback path exist.

To the maximum extent permitted by law, rConfig has no liability for any loss arising from the operation of an Agent against any device or environment where that operation was configured, scheduled, or authorised by Company.

8. Term, Termination, and Removal

8.1 Term

This Schedule takes effect when Company first installs or operates an Agent and continues for so long as Company holds a valid Vector licence, unless terminated earlier in accordance with the Vector EULA or this Schedule.

The licence in Section 2.1 is perpetual in the same manner, and subject to the same conditions, as the licence granted under Vector EULA Section 1.5.

8.2 Termination

This Schedule terminates automatically on termination of the Vector EULA for any reason.

rConfig may terminate this Schedule, or require Company to cease operating one or more Agents, where Company materially breaches this Schedule and fails to cure the breach within thirty (30) days of written notice. Breach of Section 2.3, 2.4, 5.2, or 6.2 is a material breach for the purposes of Vector EULA Section 5.2.

8.3 Removal of Agents on Termination

On termination of this Schedule or of the Vector EULA, Company must, within thirty (30) days:

disable and remove every Agent instance, including every Agent installed on infrastructure owned or controlled by an End Client;
securely delete every local credential store and every cached credential held by an Agent;
destroy all copies of the Agent, including copies held in deployment images, artefact repositories, and automation; and
certify in writing to rConfig, on request, that it has done so.

Where Company is granted a transition licence under Vector EULA Section 5.5, Company may continue operating existing Agents during the transition period but must not install any new Agent, and the obligations in this Section apply on expiry of that period.

Company acknowledges that it is solely responsible for obtaining the End Client access necessary to comply with this Section, and that an inability to obtain that access does not excuse compliance.

9. Data Protection

The data protection provisions of Vector EULA Section 13 apply to the Agent.

For the avoidance of doubt, and consistent with Section 4.1:

rConfig does not receive, access, or process any Personal Data, configuration data, credential, or device data through the Agent;
Company is the controller, or where it acts for an End Client the processor, in respect of all data collected, cached, or transmitted by an Agent; and
rConfig acts as a processor only where it obtains access to an Agent host or to its data in the course of providing Support or Professional Services, and then only on Company's documented instructions.

Company is responsible for ensuring that its contract with each End Client permits the installation of the Agent, the local caching of credentials described in Section 5.1, and any access rConfig may require for Support purposes.

10. Artificial Intelligence

The Agent contains no AI Feature.

Where an Agent executes an instruction, configuration, command, or workflow that originated as AI Output generated elsewhere in the Software, that AI Output remains subject to Vector EULA Section 12 in full, including the review and validation obligations in Vector EULA Section 12.2.

Company must not configure the Software so that AI Output is dispatched to an Agent for execution against a production device without human review and approval, and rConfig has no liability arising from any such configuration.

11. Definitions

In this Schedule, and in addition to the terms defined in the Vector EULA:

"Agent" means the rConfig Vector Agent software component, in object code form, together with any update or upgrade to it supplied to Company under the Vector EULA.

"Vector EULA" means the rConfig Vector MSP Edition Software Licence Agreement in force between the parties.

"Vector Server" means the rConfig Vector controller component licensed to Company under the Vector EULA, to which an Agent connects.

END OF SCHEDULE