Skip to content
GitRiverGitRiver
RU

GitRiver Software License Agreement

Version 1.4 of 22 September 2026.

Licensor: KRUGLOV ALEKSEI ALEKSEEVICH, individual entrepreneur registered in the Russian Federation, OGRNIP 325774600559571, INN 771506235482, address: 127576, Russia, Moscow, Altufyevskoe shosse 91, bldg. 1 (the “Licensor”).

This agreement is a licence contract between the Licensor and the person using the software (the “User”). It is entered into by accession to its terms as a whole (Article 428 of the Civil Code of the Russian Federation).

Installing, launching or otherwise using the software constitutes full and unconditional acceptance of this agreement. If the terms are not accepted, the software may not be used.

This English text is a translation. The Russian original is published with the product as LICENSE.ru.md (at /legal in an installed copy) and on the publisher’s website; it prevails in case of any discrepancy.

1. Definitions

Software — the GitRiver computer program in object code: the server, the web interface, the build runner, the command-line tools and the accompanying Documentation, including updates received under an active subscription.

Documentation — the installation, administration and usage guides, the descriptions of the application programming interfaces, and the description of the licensing terms. Documentation forms part of the delivery: the installation guide, the vulnerability reporting procedure, this agreement, the settings sample and the third-party code notices are installed together with the Software, and the full set is attached to every release as a separate archive file. The same Documentation is published on the Licensor’s website. In case of a discrepancy, the Documentation attached to the release of the Software that the Licensee uses prevails.

Installation — one copy of the Software operating against one database. An Installation is identified by its own instance_id stored in that database. The number of processes, nodes and replicas serving one database is not limited and does not affect the fee.

Community edition — the mode in which the Software operates without an activated licence.

Pro edition — the mode in which the Software operates while a valid Pro Licence is present. It unlocks the Seat-level Capabilities listed in clause 4.2.

Max edition — the mode in which the Software operates while a valid Max Licence is present. It includes every capability of the Pro edition and, in addition, the Installation-level Capabilities listed in clause 4.2.

Installation-level Capability — a capability that applies to the Installation as a whole: sign-in through an external identity provider, account provisioning, the audit log, quotas, Installation-level IP address restrictions, custom branding. The test is that the capability is configured once for the whole Installation rather than for an individual account. Configuring it is available to an administrator of the Installation; whether an account that can sign in only by means of the Max edition is admitted is governed by clause 4.4.

Seat-level Capability — a capability available to an account that has been granted a Seat (clause 4.4).

Licence — an activation file signed by the Licensor that states the owner, the edition, the number of seats, the subscription expiry date, the length of the grace period and the end of the Confirmation period.

Confirmation period — the period stated in the Licence during which the Installation is entitled to use the paid edition without receiving a new signed activation file. It runs independently of the subscription term and is renewed by every new signed activation file, whether received from the Licence server or entered manually (clause 4.12).

Seat — a user account of the Installation marked by an administrator with the seat attribute (is_pro_seat in the programming interfaces). A Seat belongs to the edition of the Licence it is provided under; a Pro edition Seat and a Max edition Seat unlock Seat-level Capabilities alike (clause 4.4).

Licence server — the Licensor’s service that delivers subscription renewals and confirmations of the right of use (clause 4.12).

2. Subject matter

2.1. The Licensor grants the User a non-exclusive licence to use the Software on the terms of this agreement.

2.2. The territory is worldwide. The Software is supplied in object code; the source code is neither delivered nor disclosed.

2.3. The Software is used in the manner set out in Article 1280(1) of the Civil Code of the Russian Federation: reproduction in computer memory, launching and operating it for its intended purpose, and making a back-up copy.

2.4. The right of use arises upon acceptance of this agreement. No separate transfer certificate is required unless the parties expressly agree otherwise.

2.5. Documentation is provided for operating the Software. The Licensee may reproduce it within its own organisation without any limit on the number of copies: print it, copy it and place it in internal systems. Clause 2.3 does not apply to Documentation — it describes the ways a computer program is used.

2.6. Non-production Installations. In addition to the Installation the Licence was purchased for, the Licensee may run up to three Installations that do not serve end users: test, pre-production and standby ones, including verifying a restore from backup. Such Installations run under the same Licence, require no separate fee and do not count towards the number of Seats.

An Installation that serves end users is not a non-production one, whatever it is called.

3. Community edition

3.1. The Community edition is provided free of charge and without a time limit. No activation is required.

3.2. The Community edition includes: Git repositories over HTTP and SSH, issues, pull requests, wiki, pages, build pipelines, package and container registries, search, notifications and the other capabilities of the Software, except those listed in clause 4.2.

3.3. The number of users and repositories in the Community edition is not limited.

3.4. The fact that the Community edition is free of charge does not waive the restrictions of section 6.

4. Paid editions: Pro and Max

4.1. The Pro and Max editions are provided for a fee, on a subscription basis. The edition, the fee, the subscription term and the number of seats are set out in an invoice or a separate contract and are reflected in the issued Licence.

4.2. In addition to the Community edition, the following are available:

in the Pro edition — Seat-level Capabilities:

  • code and dependency vulnerability scanning, dependency licence compliance and software bill of materials (SBOM) export;
  • DORA metrics and value stream analysis;
  • the code index: finding declarations and call sites across the repository;
  • team-wide knowledge counters and the dead knowledge report;
  • custom roles, IP address restrictions and CI variables at the group level;
  • the large language model assistant: failed build job analysis, preliminary pull request review, assistant settings, usage accounting and limits;
  • priority support on terms agreed by the parties;

in the Max edition — everything listed for the Pro edition and, in addition, the Installation-level Capabilities:

  • SAML SSO sign-in and SCIM account provisioning;
  • LDAP directory sign-in;
  • the audit log;
  • resource quotas and knowledge draft limits;
  • Installation-level IP address restrictions;
  • custom branding.

Installation-level Capabilities are provided in the Max edition only. A valid Pro Licence does not unlock them, whatever the number of seats it carries.

4.3. Seat limit. The number of Seats existing in an Installation at the same time may not exceed the number of seats stated in the Licence. The value “0” means that the number of seats is unlimited. The Software enforces the limit when a Seat is assigned; circumventing that enforcement is prohibited by clause 6.1.

Seats are added together only within one edition: seats of valid Pro edition Licences add up with one another, and seats of Max edition Licences with one another. A Licence of an edition other than the one in force in the Installation is not accepted for activation; to move from one edition to another, the Licensor reissues the Licence at the User’s request.

4.4. Seats and the scope of access. A Pro edition Seat and a Max edition Seat unlock Seat-level Capabilities alike. A Seat is assigned by an administrator of the Installation; it is not assigned on an account’s first sign-in.

An account without a Seat that can sign in with a password, or through an identity provider available in the Community edition, operates within the scope of the Community edition and is not charged for.

An account that can sign in only by means provided in the Max edition (SAML SSO sign-in, LDAP directory sign-in) works only with an assigned Seat and a valid Max edition Licence. While the Licence is valid but there is no Seat, the sign-in completes, but further work is unavailable; the Software tells the User so and states that a Seat is assigned by an administrator of the Installation. Without a valid Max edition Licence, sign-in by these means does not complete (clause 4.7).

Where the Licence does not limit the number of seats (the value “0” under clause 4.3), the seat attribute is not required: Seat-level Capabilities are available to every account of the Installation, and an account that can sign in only by means of the Max edition works without an assigned Seat while a Max edition Licence is valid.

Installation-level Capabilities are configured by an administrator of the Installation and apply to the Installation as a whole.

4.5. Subscription term. The right to use the Software under a paid edition lasts until the expiry date stated in the Licence. Subscriptions are sold for terms of one month to one year unless the parties agree otherwise.

4.6. Grace period. After the subscription expires, the paid edition is retained for a grace period whose length is stated in the Licence and defaults to:

Subscription term Grace period
1 to 3 months 7 days
4 to 11 months 14 days
12 months or more 30 days

Throughout the grace period the Software warns every signed-in User of the date it ends, not only the administrators of the Installation.

4.7. When the grace period ends, the capabilities of the paid edition are switched off and Seats in excess of the limit are released automatically. Along with them, sign-in by means of the Max edition — through SAML SSO and through an LDAP directory — stops working: it forms part of the paid edition and is not provided once that edition has ended.

Sign-in with a password and through identity providers available in the Community edition continues to work; an administrator of the Installation may set a password for any account. The Software does not allow a state in which the Installation is left without a single administrator who signs in with a password.

The User’s data is neither deleted nor made inaccessible: the Installation continues to run under the Community edition.

4.8. Activation. A paid edition is enabled by a challenge-response procedure: the User enters the licence key, receives an activation request, passes it to the Licensor and enters the activation response. Activation does not require the Installation to be connected to a public network. The number of activations per key is limited by the value carried in the key. An activation is neither revoked nor transferable; the same key may be activated again within the remaining number of activations.

4.9. Renewal. A paid renewal is delivered by the Licence server and applied by the Installation on its own. Where there is no connection to the Licence server, a renewal is entered manually in the same way as the first activation. Unavailability of the Licence server does not by itself terminate the right of use; the consequences of unavailability lasting longer than the Confirmation period are set out in clause 4.12.

4.10. Fees paid for a subscription term are non-refundable, except where the law provides otherwise.

4.11. An edition unknown to the installed version. If the Licence states an edition that the installed version of the Software does not recognise, the Licence is accepted and the Installation runs within the scope of the Community edition until the Software is updated. Such an update is provided under clause 5.1 and is not charged for separately. The right to use the paid edition is not terminated by this and is not shortened beyond clause 4.5.

4.12. Confirmation of the right of use. A signed activation file is valid for the Confirmation period stated in the file itself. The Confirmation period is renewed by every new signed activation file; the Installation requests one from the Licence server on its own, and where there is no connection the User obtains such a file from the Licensor and enters it manually, in the same way as the first activation. The manual route is of equal standing and is not treated as exceptional.

The length of the Confirmation period is stated in the Licence and by default depends on the subscription term, never exceeding it — there is no point in confirming a right for longer than it has been paid for:

Subscription term Confirmation period
1 month 14 days
3 months 30 days
6 months 60 days
12 months 90 days

For a subscription term not listed in the table, the value of the nearest shorter listed term applies.

For Installations operating without access to a public network the Confirmation period is set longer by agreement of the parties.

The Software warns the Installation’s administrator before the Confirmation period ends — no later than 7 days in advance, and earlier where the Confirmation period is a long one.

When the Confirmation period ends, the capabilities of the paid edition are disabled, and at the same time:

  • the subscription term and the number of paid seats are unchanged, and the fees paid for the subscription term are not forfeited and remain usable once a new signed activation file is received;
  • the seat attribute is not removed from user accounts;
  • the User’s data is neither deleted nor made inaccessible: the Installation continues to operate under the Community edition;
  • the capabilities of the paid edition are restored immediately upon receipt of any new signed activation file, with no further payment and no re-activation.

4.13. Binding of the activation file to the database. A signed activation file may carry an anonymised fingerprint of the Installation’s database (clause 7.1), in which case it is accepted only by the Installation whose fingerprint matches. Restoring the database into a new cluster and upgrading the database management system change that fingerprint; in such a case the Licensor re-issues the activation file at the User’s request free of charge, and the file issued earlier remains valid until the end of its own Confirmation period.

A re-issued file is entered by the User manually, in the same way as the first activation: an automatic confirmation (clause 4.12) does not rebind a Licence to a different database. This does not limit the User’s rights — the subscription term, the number of seats and the Confirmation period are unchanged — and requires no payment.

5. Updates and support

5.1. During the subscription term the User may obtain and use updates to the Software. Updates released after the subscription term ends are available only after renewal.

5.2. Updates obtained during the subscription term may be used after it ends — within the scope of the Community edition, and within the scope of the paid edition for the duration of the grace period.

5.3. The Licensor is under no obligation to release updates at any particular frequency or to keep the set of capabilities unchanged, save for obligations undertaken in a separate support contract.

6. Restrictions

6.1. The User may not:

  • modify the Software or its activation files, or remove or circumvent the enforcement of the Licence, the Seat limit or the subscription term;
  • decompile, disassemble or otherwise study the Software in order to obtain its source code, beyond the cases expressly permitted by Article 1280 of the Civil Code of the Russian Federation;
  • reproduce the Software for delivery to third parties, sell it, lease it, transfer the right of use or grant sub-licences, unless agreed with the Licensor in writing;
  • give third parties access to the Installation as a service in its own right (including as a cloud service for other organisations) without the Licensor’s written consent;
  • remove or alter the notices of authorship, copyright notices and licence notices, except for the branding facilities provided by the Software itself under the Max edition;
  • use the name “GitRiver”, the logo or the Licensor’s other means of individualisation in a way that suggests that the User’s own product was released or endorsed by the Licensor.

6.2. The restrictions of section 6 apply to every edition of the Software.

6.3. Using the Software for acts that breach the applicable law is prohibited. The User is responsible for the content stored in the Installation.

7. Information transmitted to the Licensor

7.1. An Installation with an activated Licence periodically contacts the Licence server and transmits: the instance_id, the Software version, the list of its Licences with their expiry dates, the number of users, the number of repositories, and the number of assigned and paid Seats.

7.2. The Software does not transmit to the Licensor any repository content, files, source code, commit messages, issues, personal data of the Installation’s users, e-mail addresses or credentials.

7.3. The information referred to in clause 7.1 is used solely to deliver renewals and confirmations of the right of use (clause 4.12), to verify compliance with the subscription terms and to account for installations.

7.4. An Installation under the Community edition, and an Installation with no connection to the Licence server, transmit no information to the Licensor. For an Installation under a paid edition, having no connection means that the confirmation of the right of use is carried in by the User manually (clause 4.12).

8. Personal data

8.1. The Software runs on the User’s equipment and under the User’s control. With respect to personal data processed in the Installation the User is the data controller; the User determines the purposes and the scope of processing and discharges the controller’s duties.

8.2. The Licensor has no access to the Installation’s data and does not process the personal data of the Installation’s users, except for information the User provides when purchasing, contacting support or reporting a vulnerability.

9. Intellectual property

9.1. The exclusive right to the Software belongs to the Licensor. This agreement does not alienate that right.

9.2. The Software includes third-party components distributed under their own licences. Those terms apply to the respective components and prevail over this agreement to the extent they concern them. The list of components and their licence texts is provided by the Licensor on written request.

10. No warranty

10.1. The Software is provided “as is”. The Licensor does not warrant that the Software is free of errors, that its operation will be uninterrupted and error-free, or that it is fit for purposes not communicated to the Licensor in writing.

10.2. The Licensor does not warrant compatibility with any particular hardware, software or network environment of the User.

10.3. The User is responsible for backing up the Installation’s data and for verifying restoration from those backups.

10.4. The absence of warranties does not affect rights granted to consumers by mandatory provisions of law where the User is an individual using the Software for personal needs.

11. Liability

11.1. The Licensor’s liability to the User is limited to the fee actually paid for the subscription during which the ground for liability arose. Under the Community edition, which is provided free of charge, the Licensor bears no liability.

11.2. The Licensor is not liable for lost profit, loss of data, downtime or other indirect losses.

11.3. The limitations in clauses 11.1 and 11.2 do not apply to wilful breach or to any other case where limiting liability is not permitted by law.

11.4. A breach of section 6 entitles the Licensor to withdraw from this agreement unilaterally and to claim damages in full.

12. Term and termination

12.1. This agreement takes effect upon acceptance of its terms and continues until the User ceases to use the Software.

12.2. The right of use under a paid edition ends when the subscription term and the grace period expire, unless the subscription is renewed.

12.3. In the event of a material breach the Licensor may withdraw from this agreement upon notice to the User. From that moment the User must cease using the Software under a paid edition; deletion of the Installation’s data is not required.

12.4. Termination does not oblige the Licensor to refund the fee for the elapsed part of the subscription term.

13. Amendments

13.1. The Licensor may amend this agreement. A new version is published as part of the Software distribution and takes effect for the User from the date the version containing it is installed.

13.2. A subscription already paid for is governed by the version in force on the date of payment, unless the new version is more favourable to the User.

13.3. A User who does not accept a new version may continue to use the previously installed version of the Software on the previous terms.

14. Governing law and disputes

14.1. This agreement is governed by the law of the Russian Federation.

14.2. The parties adopt a pre-action claim procedure: a claim is to be considered within 30 (thirty) calendar days of receipt.

14.3. Disputes that remain unresolved are referred to the commercial (arbitrazh) court at the Licensor’s place of business or, where the User is an individual using the Software for personal needs, to the court determined by the jurisdiction rules established by law.

14.4. If any provision of this agreement is held invalid, the remaining provisions stay in force.

15. Contacts