Back to home

Last updated 1 September 2026

Terms of Service

An agent that writes code needs clear boundaries. These terms set them: what Verix may change, who owns the result, and who signs off before anything merges.

01Agreement

These terms govern your use of the Verix website, dashboard, command-line tool and agent. By connecting a repository or signing in, you accept them. If you are accepting on behalf of an organisation, you confirm you have the authority to bind it.

Enterprise customers may have a signed order form. Where it conflicts with these terms, the order form wins.

02The service

Verix detects security, performance and reliability issues in connected repositories, explains the root cause, proposes a fix, validates that fix in an isolated sandbox, and opens a pull request.

  • The only write path to your code is a pull request against a branch.
  • Nothing is patched, restarted or redeployed in your infrastructure by the agent.
  • A pull request is only merged when a human with write access merges it.

03Accounts and access

You are responsible for keeping credentials secure, for the scopes you grant to the code host integration, and for the actions of every user under your organisation. Tell us promptly if you believe an account has been compromised.

Grant the narrowest repository scope that lets the agent do its work. You can revoke access at any time from your code host.

04Ownership

You keep all rights to your source code. You grant us a limited licence to read, analyse and modify copies of it strictly to provide the service.

Diffs the agent proposes for your repositories are yours. We keep all rights to the Verix platform itself — the detectors, the orchestration, the interface and the documentation.

05Agent-generated code

Fixes are generated by an automated system. Every proposed change is validated in a sandbox before it reaches you, but validation is not proof of correctness.

You remain responsible for reviewing, testing and approving every pull request before merging it. We make no warranty that a generated fix is complete, secure or suitable for your use, and merging is always a human decision.

06Acceptable use

  • Do not use Verix against code you do not own or have written permission to analyse.
  • Do not use findings to attack systems you are not authorised to test.
  • Do not attempt to extract model weights, detector internals or other customers' data.
  • Do not resell or expose the service as your own product without a written agreement.
  • Do not circumvent rate limits, seat counts or usage limits.

07Fees

Paid plans are billed in advance for the period you select. Seat changes are prorated on upgrade and take effect at the end of the period on downgrade. Fees are non-refundable except where law requires otherwise.

Prices may change with 30 days' notice, effective at your next renewal.

08Availability

We aim for high availability and publish incident history, but the service is provided as is. Planned maintenance is announced in advance where practical. Enterprise plans carry a contractual uptime commitment; other plans do not.

09Limitation of liability

To the maximum extent permitted by law, neither party is liable for indirect, incidental, special or consequential damages, or for lost profits, revenue, data or goodwill.

Our total aggregate liability is limited to the fees you paid in the twelve months before the event giving rise to the claim. Nothing here limits liability that cannot be limited by law.

10Termination

You may stop using the service and disconnect your repositories at any time. We may suspend or terminate access for a material breach of these terms, or for non-payment after notice.

On termination your right to use the service ends and your data is deleted according to the retention rules in the Privacy & Cookie Policy.

11Changes

We may update these terms. Material changes are announced by email to account administrators at least 30 days before they take effect. Continuing to use the service after that date means you accept the new version.

Questions about this document? Write to legal@verix.dev.