MonthlyAnnual
A Git GUI the whole team can share
Gitoryx Team gives every developer the same native Git client on macOS, Windows and Linux, billed as one yearly capacity of seats rather than as a pile of individual licences. Buy 5 to 100 seats, hand them out from an admin console, and take them back when people move on.
Every seat includes the full Pro feature set: unlimited commit history on private repositories, unlimited Git identity profiles, the advanced commit graph, and pull request management across GitHub, GitLab, Bitbucket and Gitea, including their self-hosted and enterprise variants.
Seat capacities and prices
Team
Billed annually$3,900/ year
25 seats × $13 / seat / month · 7% off
Billed once a year · about $325 a month
- You pay for the capacity, occupied or not. Pending invitations hold a seat for 14 days.
- The account owner does not use a seat unless they add themselves.
- Everything in Pro, for every member
- One invoice, one renewal date
- Assign and revoke seats as people join or leave
- Admin console: members, seats and pending invitations
- Priority support
How Team seats work
- You buy a capacity
- Choose 5, 10, 25, 50 or 100 seats, billed once a year. The price follows the capacity, even when some seats are empty.
- Seats move freely
- Admins invite members and revoke access at any time. A pending invitation holds a seat for 14 days; removing a member frees theirs and ends their Pro access immediately.
- Change capacity when you need to
- Adding seats applies right away, prorated. Reducing them takes effect at renewal, as long as the seats in use fit.
Team seats vs individual Pro licences
A Team seat costs more per developer than an individual Pro licence, and that is deliberate rather than a volume penalty: the premium pays for the administration layer around the licences. If your team is three people who each expense their own tool, buy individual Pro licences instead. The moment someone has to track who has what, Team starts paying for itself.
- One invoice, one renewal date
- A single annual charge for the whole capacity instead of a receipt per developer landing in finance all year round. Purchase orders and VAT details are set once.
- Seats follow the team, not the person
- When someone leaves, you revoke their seat and hand it to whoever replaces them. Nobody has to repurchase, and no licence is stranded on a former employee's account.
- An admin console
- Members, occupied seats and pending invitations in one place, with invitations that hold a seat for 14 days before expiring back into the pool.
- Priority support
- Team accounts jump the queue. A stuck rebase blocking a release is not a ticket that should wait its turn.
Choosing a Git client for a team
Most teams land on this decision after outgrowing a mix of command line, GitHub Desktop and whatever each person installed themselves. Three things tend to decide it.
Does everyone need an account to use it?
Gitoryx runs locally and needs no account to install or to work on public repositories, so developers can evaluate it before you buy anything. An account is only needed to hold a seat. GitKraken requires an account up front, which is a real obstacle when you are trying to get a team to try something.
Is it the same tool on every machine?
Gitoryx is a single Tauri codebase, so macOS, Windows and Linux get the same features on the same release cycle. Clients that maintain separate codebases per platform drift, and a mixed-OS team feels it in every support conversation.
Does it cover the hosts you actually use?
In-app pull request creation and review works across GitHub, GitLab, Bitbucket and Gitea. If part of your team is on self-managed GitLab or a Gitea instance, that difference decides the tool. See the full comparisons.
Worth reading alongside this: getting a team to agree on Git, on the conventions worth standardising before you standardise a client.
Team pricing questions
- How does Team pricing work?
- You buy a yearly capacity of seats (5, 10, 25, 50 or 100) and pay for that capacity, whether or not every seat is used. Every member gets Pro while they hold a seat.
- Can I change the number of seats?
- Yes, from your organization dashboard. Adding seats applies immediately and is prorated. Reducing them takes effect at renewal, as long as the seats in use fit in the smaller capacity.
- What happens when I remove a member?
- Their seat is freed right away and their Pro access from the organization ends. A Pro plan they pay for themselves is not affected.
- Why does a Team seat cost more than an individual Pro licence?
- A Team seat carries what an individual licence does not: an admin console, seats you can reassign when someone joins or leaves, a single invoice with one renewal date, and priority support. If none of that is useful to you, buying individual Pro licences is cheaper and perfectly fine.
- Do we need an account for every developer?
- Only to hold a seat. Gitoryx itself runs locally and needs no account to install or to use on public repositories, so people can try it before you assign them anything.
- What if we need more than 100 seats?
- Past 100 seats there is no self-serve checkout. Contact us and we put a quote together with you.
Buying for yourself? See individual Free, Pro and Lifetime plans.