Skip to content
Revus
Menu
A clearer Git desktop client

Git clarity,
at native speed.

A modern desktop Git client for seeing the shape of your work, navigating repositories without friction, and keeping advanced workflows understandable.

Windows · macOS · LinuxLocal-first by intent
revus / revus
Open repository
mainclean
History
24 commits · 3 branches
Filter
Refine repository overview
a8f2c91 main
2m
Add branch context to history
9c4e120 feat/branch-panel
18m
Tighten diff review layout
62d3aa7 main
1h
Keep selection on refresh
e14ba3d feat/branch-panel
3h
Create project shell
4ff9b12 main
5h
mainGit 2.47.0● local

Conceptual preview · interface direction, not a released screenshot

The point

Keep the whole repository in view.

Git is powerful because it keeps history close. Revus is being shaped around that idea: less hunting through panels, more confidence about what happens next.

01 / HISTORY

Understand repository history

Follow commits and branches as a connected story, not a list of hashes you have to decode alone.

02 / FLOW

Make common Git actions feel direct

Open a repository, read its state, prepare changes, and create commits without unnecessary ceremony.

03 / CONTROL

Stay understandable as work gets advanced

A calm interface for everyday work, with enough depth for the branch, merge, and rebase decisions that follow.

Core capabilities

Useful before it is impressive.

Revus starts with a small, focused foundation. Capabilities that are not ready are labelled as such, so the public roadmap stays as trustworthy as the product should feel.

01 / Start clean Available

Repository opening

Open a local repository and get straight to the worktree without a tour of hidden panels.

02 / Know the state Available

Working-tree status

See changed, staged, and untracked files in a focused view built around the native Git CLI.

03 / Move forward Available

Commit creation

Write a commit message, review the staged set, and create the commit without leaving the app.

04 / Make it yours Available

Themes and diagnostics

Use light, dark, or system appearance and inspect local Git availability when something needs attention.

05 / See the story In development

Visual commit history

A clear graph for branches and merges is being shaped as part of the next foundation milestone.

06 / Keep context In development

Branch management

Create, switch, merge, and rebase through a coherent workflow designed around everyday Git usage.

07 / Review clearly In development

Structured diffs

Review changes with enough context to make confident decisions before a commit or handoff.

08 / Stay extensible Planned

Provider integrations

Provider-ready architecture is planned for optional online workflows when the local core is solid.

See the full capability map, grouped by delivery state.

Explore all features

A natural workflow

From repository to next move.

The product should make a useful loop feel obvious: orient yourself, inspect the change, then choose the Git action with context intact.

01

Open a repository

Point Revus at a local project and land in a useful view immediately.

02

Understand its history

Follow the commit story and branch relationships as the graph takes shape.

03

Review the work

Inspect the working tree and prepare a focused set of changes.

04

Move it forward

Commit, branch, merge, or rebase with the context still in view.

Local by intent

Your repositories stay close to the work.

Git operations are performed against repositories on your machine. Core repository workflows are designed to remain local; optional online integrations may require communication with their respective providers.

01
local repository
02
explicit integrations

Initial release

Free while the foundation takes shape.

No payment is required to evaluate the core Git client. Any future optional professional or hosted capabilities will be communicated clearly before changes.

Free during the initial release phaseView availability

Keep in touch

A better way to see what your Git is doing.

Report an issue, request a feature, or help shape the workflows that make the foundation useful through the public issue tracker.