GitRiverTerms of Service
Last updated: 22 September 2026
1. General
These Terms of Service (hereinafter "Terms") govern the use of the GitRiver website and the ordering and payment of Pro and Max subscriptions. The rights holder of the GitRiver software and the seller of subscriptions is KRUGLOV ALEKSEI ALEKSEEVICH, individual entrepreneur registered in the Russian Federation, OGRNIP 325774600559571, INN 771506235482, address: 127576, Russia, Moscow, Altufyevskoe shosse 91, bldg. 1 (hereinafter "Rights Holder"). Use of the Software itself is governed by the licence agreement shipped with GitRiver (LICENSE.en.md; inside the installation it opens at /legal): these Terms neither replace it nor narrow the rights it grants, and clauses of the agreement are cited as numbered in the version currently shipped. Ordering, payment and refunds are governed by these Terms; use of the Software, by the licence agreement. By placing an order you agree to these Terms.
2. Software Description
GitRiver is a self-hosted git platform for managing repositories, CI/CD, Container Registry, Package Registry, and other development tools. The Software is available in three editions: Community - free and perpetual, with no limits on users or repositories; Pro - by subscription, unlocking seat-level capabilities; Max - by subscription, including all of Pro and unlocking installation-level capabilities on top. Max is the next step up from Pro, not a different product: everything Pro gives, Max gives too.
3. Community Edition
GitRiver Community is provided free of charge for any use, including commercial. No activation is required, the term is unlimited, and the number of users and repositories is not capped. Community includes every capability of the Software except those listed in section 4 for the Pro and Max editions: Git over HTTP and SSH, LFS and GPG signatures, issues and boards, pull requests, branch protection and CODEOWNERS, merge queue, CI/CD pipelines, Container and Package Registry, GitOps deployment (RiverCD), backups, notifications and webhooks, Pages, Wiki, releases, OAuth2 and two-factor sign-in. The restrictions of section 9 apply to the Community edition as well.
4. Pro and Max Editions
The Pro and Max editions are provided for a fee on a subscription basis, for terms of one month to one year. The edition, the number of seats and the subscription term are set by the order and recorded in the licence issued. The Pro edition unlocks seat-level capabilities - those available to an account that has been assigned a seat: DORA metrics and value stream analysis, code and dependency vulnerability scanning, dependency licence compliance and SBOM export (SPDX), the code index, team-wide knowledge counters, custom roles, group-level CI variables and IP address restrictions, the large language model assistant, and priority support. The Max edition includes everything listed for Pro and, in addition, installation-level capabilities - those that apply to the installation as a whole: SAML SSO sign-in, SCIM account provisioning, LDAP directory sign-in, the audit log, resource quotas and knowledge draft limits, installation-level IP address restrictions, and 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. The exhaustive scope of each edition is defined by clause 4.2 of the licence agreement. Which editions are open for ordering at any given time is shown on the pricing page. While trial licences are being issued, one may be obtained in the dashboard free of charge: one per user or organisation — no more than one per site account, per email address and per installation. A confirmed email address is required. A trial licence grants the capabilities of the Pro edition and is activated on a single installation on which no GitRiver licence has been in effect before; its term runs from the first activation, and its seat count, term and activation deadline are stated when it is issued. A trial licence cannot be renewed or extended; a one-time extension is possible only at the Rights Holder's discretion.
5. Seats and How They Are Counted
A seat is an account of an installation to which the administrator has assigned the seat attribute. Seat-level capabilities are available to such accounts only. The number of seats existing in an installation at the same time may not exceed the number of seats stated in the licence (clauses 4.3 and 4.4 of the licence agreement). A Pro seat and a Max seat unlock seat-level capabilities alike. Seats are assigned by the installation administrator; no seat is assigned to an account on its first sign-in. A seat goes to whoever is given the tooling: a company where forty people out of three hundred need it pays for forty seats. An account without a seat that can sign in with a password or through a sign-in provider of the Community edition works within the scope of Community and never reaches the invoice. An account that can sign in only through SAML SSO or an LDAP directory works only with an assigned seat and a valid Max licence: corporate sign-in is not part of Community, and without a seat such an account signs in but is not admitted to work - not in the interface, not through the API, not over git - and the Software tells it that seats are assigned by the administrator (clause 4.4 of the licence agreement). So in the Max edition you need as many seats as the people who sign in through the directory and single sign-on, plus those given the tooling. The smallest number of seats each edition is sold from is stated on the pricing page. Licences stack only within one edition: the seats of Pro licences add up with each other, and the seats of Max licences with each other. A licence of another edition is not accepted for activation on an installation that already has a valid licence; to move from one edition to another, the Rights Holder reissues the licence (clause 4.3 of the licence agreement). Seats may be added to a valid licence - such an addition is charged for the remainder of its term and does not change the edition.
6. Subscription Term, Renewal and Change of Edition
The right to use a paid edition lasts until the expiry date stated in the licence and is retained for a grace period whose length is stated in the licence and depends on the subscription term. Throughout the grace period the Software warns every signed-in user about its end date, not only the administrator. Once the grace period ends, the capabilities of the paid edition switch off, seats above the limit are removed, and with them sign-in through SAML SSO and an LDAP directory stops working: it is part of the paid Max edition and is not provided once that edition ends. Sign-in with a password and through the sign-in providers of the Community edition keeps working, the installation administrator may set a password for any account, and the Software does not let the last administrator who signs in with a password be removed. The installation keeps running in the Community edition; data is neither deleted nor made inaccessible. Within a paid term the edition of a licence does not change. The edition is chosen at renewal: a renewal starts a new term, and from its start the licence runs in the chosen edition. Renewing into another edition is a new purchase for a new term at the rate of the chosen edition, not a top-up of the difference: no recalculation is made for the term already paid for, whether the move is up or down. Adding seats does not change the edition. A licence is activated by a challenge-response procedure and, once activated, works without a permanent network connection. The default length of the grace period for each subscription term is stated on the pricing page. Renewal, the grace period and confirmation of the right are described in clauses 4.5-4.13 of the licence agreement.
7. Pro Sold Before the Editions Were Split
SAML sign-in, SCIM account provisioning and LDAP directory sign-in were part of the Pro edition until September 15, 2026. A Pro licence issued before that date is honoured as Max until the end of the term already paid for: what was paid for stays with the buyer. The edition purchased is not silently rewritten - the licence, the order and the dashboard still say Pro, and a renewal is charged at the rate of whichever edition the buyer chooses. A renewal starts a new term and this clause does not apply to it: a licence renewed as Pro is honoured as Pro from the start of the new term, and installation-level capabilities are unlocked by renewing into Max. The edition actually honoured is shown for every licence in the dashboard.
8. Payment and Refunds
The currency and the payment method follow the domain the order is placed on: on gitriver.ru, Russian roubles paid by card through T-Bank (JSC T-Bank), or by bank transfer against an invoice for an order above the single card payment limit; on gitriver.com, US dollars paid either by Visa or Mastercard through the Robokassa payment service (Robokassa LLC) or by bank transfer against an invoice. The price in US dollars is fixed and is not converted at any rate: the invoice is issued for that amount, and the sum charged in the currency of the card is set by the issuing bank at its own rate. Cards issued in certain countries are not served by the payment service - for those orders payment by bank transfer against an invoice remains available. The prices of the two domains are each set for their own market and are not tied by an exchange rate. All prices include VAT where applicable. The licence key is issued once payment arrives: immediately for a card payment, and after the funds are credited for a bank transfer. The Rights Holder refunds the fee within 14 days of purchase provided the licence has not been activated on any installation; after activation no refund is made on that ground. This is a term of the storefront: clause 4.10 of the licence agreement provides for no refund, and these Terms grant one over and above the agreement. A refund is made by the same means as the payment. Rights granted to consumers by mandatory provisions of law are not limited by this clause.
9. Usage Restrictions
You may not: modify the Software or its activation files, or remove or circumvent the enforcement of the licence, the seat count or the subscription term; decompile or disassemble the Software beyond the cases expressly permitted by Article 1280 of the Civil Code of the Russian Federation; share licence keys with third parties, or sell, rent or sublicense the Software without the Rights Holder's written consent; give third parties access to an installation as a service of its own, including as a cloud service; use the Software to violate applicable law. The full list of restrictions is section 6 of the licence agreement. The restrictions apply in every edition; upon discovering a violation the Rights Holder may revoke the licence.
10. Limitation of Liability
The Software is provided "as is". The Rights Holder is not liable for damages arising from the use or inability to use the Software, for data loss, or for the acts of third parties. The Rights Holder's liability is limited to the fee actually paid for the subscription during which the ground for liability arose; no liability arises under the free Community edition. These limitations do not apply to wilful breach or to any other case where limiting liability is not permitted by law.
11. Governing Law
These Terms are governed by the laws of the Russian Federation. The parties adopt a pre-action claim procedure: a claim is to be considered within 30 (thirty) calendar days of its receipt. Disputes not settled through that procedure are referred to the commercial court at the Rights Holder's location; where the buyer is an individual purchasing a subscription for personal needs, jurisdiction follows the rules laid down by law. Legally significant notices are to be sent to the addresses listed on the Contacts page.