Hivecode

legal

Terms of service

Plain language, because terms nobody can read protect nobody.

Last updated 28 July 2026

These terms cover your use of the Hivecode website, the hosted relay, the Hivecode VS Code extension and the hivecode-mcp server (together, “the service”), and any Hivecode Pro licence you buy. They are between you and [your registered name] of [your city, state], India (“we”, “us”).

The open-source parts are not covered by these terms. icr-merge and git-clash are MIT licensed; their licence text governs them, and nothing here restricts what that licence grants you.

What you get

  • A free tier that allows up to two concurrent committers in a room.
  • Hivecode Pro, billed per concurrent committer, which raises that limit to the number of committers on your licence.
  • Access to the hosted relay, or the right to run the relay yourself.

A “committer” is one participant — human or agent — writing to a room at the same moment. Idle agents, read-only participants and browser viewers are not counted.

Your licence key

Your key identifies your licence. It is yours to use across your own machines and your own agents. Do not publish it or share it outside your organisation: anyone holding it can consume your committer allowance. We can change your seat count without issuing a new key, because entitlement lives on our record rather than inside the key.

We may suspend a licence that is being shared publicly, or used to attack the service. Where we do that, we will tell you why and, if it was a mistake, restore it.

Your code

Your code is yours. We claim no rights over anything you or your agents write. The relay forwards changes between participants in a room and does not keep a canonical copy of your repository — see Privacy for exactly what passes through and what is retained.

What we do not promise

The service is provided as it is, without warranty. Specifically, and stated plainly because it matters more here than in most software:

  • ICR guarantees structure, not meaning. It will not emit code that fails to parse, and it will refuse a merge rather than ship one it cannot validate. It cannot tell you that a merge which parses is the merge you wanted.
  • Coordination between agents reduces collisions; it does not eliminate the need for review. Keep your tests and keep reading the diffs.
  • The hosted relay is a single deployment with no uptime guarantee. If continuous availability matters to you, run the relay yourself — every part needed to do that is public.

To the extent the law allows, our total liability for any claim relating to the service is limited to what you paid us in the three months before the claim. We are not liable for lost profits, lost data or consequential loss.

Ending it

You may stop using the service at any time, and cancel a subscription as described in Refunds and cancellation. We may end your access if you breach these terms, do not pay, or use the service to break the law. If we discontinue the hosted relay we will give at least 30 days' notice, and the self-hosting route will remain available.

Changes

We may update these terms. If a change materially reduces what you get while you are paying us, we will tell you by email before it takes effect. Continuing to use the service after that is acceptance.

Law

These terms are governed by the laws of India, and the courts of [your city] have exclusive jurisdiction.

Questions about any of this: contact us.