A service we operate, or software you do. Decisions stay yours either way.

What is provided

There are two things on offer, and they carry different obligations:

• A managed service. We operate the workspace, connect it to your error tracker, and review what it finds. The scope, the response targets, and the term are set in your service agreement, which governs wherever it differs from this page.
• The software, to run yourself. No licence cost and no account with us. You deploy it, you operate it, and the licence distributed with the source governs your use of it.

Your responsibilities as the operator

Running the product makes you responsible for:

1. the infrastructure it runs on, and the security of that infrastructure;
2. the credentials you configure, including the encryption key that protects stored tokens;
3. the third-party services you connect — the AI provider, your error tracker, Git hosting, FTP or SFTP targets, and notification channels — and their own terms;
4. the data you allow into event payloads, and any obligations that data carries;
5. every change that reaches one of your environments through the product.

Automated analysis is advisory

Analyses are produced by a language model. They can be wrong, incomplete, or confidently mistaken. Risk scores are produced by rules, and rules can be miscalibrated for your system. Neither output is a professional opinion and neither should be treated as one.

The product is built so that a person approves anything that changes a system. Removing that step — by automating approvals in your own tooling, for example — moves the entire risk of the resulting change to you.

Changes to your systems

Pull-request creation and approval-based file changes are optional integrations. When enabled, they act with the credentials you supply and the permissions those credentials carry. File changes keep backups so a revert has something to restore, but a backup is not a guarantee of recovery.

Verify a proposed change before approving it. Approving is the moment responsibility transfers to the approver.

Warranty and liability

Self-hosted, the software is provided as-is, without warranty of any kind, express or implied, including warranties of merchantability, fitness for a particular purpose, and non-infringement. We are not liable for damage arising from its use, including damage caused by an analysis that was wrong or a change that was approved.

On the managed service, our obligations are the ones written in your service agreement — the response targets, the availability commitment where one is given, and the liability position agreed with you. Nothing on this page reduces them.

Changes to this page

This page may change as the software changes. Because it describes behaviour rather than granting rights, the authoritative record of what changed is the repository’s change history, which is public on the changelog page.