Download

Written in Rust

The fast Git client for Windows, macOS and Linux.

A 100,000-commit history shows its newest commits in 300 ms. It scrolls at 16 ms per frame. Undo anything with Ctrl+Z, even a force push.

Installer, x86-64Disk image, Apple siliconAppImage, x86-64 · .deb, .rpm

  • Free for non-profit use
  • No telemetry
100,000 commits, the whole history

Click the history, then scroll all 100,000 commits, or jump:

Works with

  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps
  • and any Git server, over HTTPS or SSH

Builds that miss one of these do not ship.

Measured on a repository with 100,000 commits.

  • 300msto the first rows of the graph
  • 100msto show a commit's details
  • 16msper frame, while you scroll
  • 0.5%of one CPU core, idle
Start in 1 s. Blame a 5,000-line file in 500 ms.All 20, and how we measure them

Features

Built for the parts of Git that go wrong.

Each one below is live. Try it.

Undo

Undo anything.
Yes, even a force push.

Discarded the wrong file? Ctrl Z takes it back. A push too, until someone pushes on top of it.

Changes
Unstaged files3
  • Msrc/pager.rs
  • Msrc/fetch.rs
  • Adocs/usage.md
Undo history
  1. Opened harbour

Discard a file, then press Ctrl Z.

Drag and drop

Drag to merge or rebase.

Every place a branch can land lights up. Drop it, and Crabway asks which.

harbourmain
Retry fetch with backoff
Cache parsed config
Add a backoff helper
Fix off-by-one in pager
Handle empty diff

Drag retry onto main, or click it. By keyboard: Tab to retry, then Enter.

Merge tool

Merge line by line.

Tick the lines you want from each side. Save and stage in one click.

src/fetch.rs1 conflict
current
1fn backoff(attempt: u32) -> Duration {
2 let ms = 100 * u64::from(attempt);
3 Duration::from_millis(ms)
4}
incoming
1fn backoff(attempt: u32) -> Duration {
2 let ms = 100u64 << attempt.min(6);
3 Duration::from_millis(ms.min(MAX_MS))
4}
Resultas it will be saved
1fn backoff(attempt: u32) -> Duration {
Tick the lines to keep, from either side
2}

Tick line 2 of main and line 3 of retry, then Save and stage.

Privacy

No telemetry.

Your code goes only to your Git servers. The privacy notice lists every field.

A firewall will show you this list. Only the services you connect add to it.

What leaves your computer

  • git fetch, git pushyour Git serversyour code
  • update checkdownloads.crabway.dev, no IDcan be off
  • licence checklicence serviceonce a month
    • key
    • computer ID
    • computer name
    • public key
    • signature
    • time signed
    • terms version
    • time agreed
    • Non-profit answer
    • time answered
  • bug or feature reportCrabway supportwhen you send

One key for all three systems.

What you buy stays yours.

Commercial

49 USD a year per person

Renews yearly. Stop any time.

  • Bought by you, for your own work
  • Every feature, the dark themes included
  • New versions and support for the year
  • Versions up to your last payment stay yours
  • Three computers at a time, on any system

49 USD a year per seat

  • 1 to 100 seats a purchase, by invoice or card
  • Every feature, three computers a seat
  • Versions up to the last payment stay the team's
  • Add seats any time, and pay for the months left

Say how many seats you need. There is no quote to wait for.

Non-profit

Free

  • Learning, hobbies and open source, with donations
  • Teaching, charities and public authorities
  • Every feature but the dark themes, and no support
  • For one person, with private repositories
  • Now and then, Crabway asks: still non-profit?

The invoice comes by email.Questions about buying

Git, the crab way.

Open your biggest repository.