Local private work stays useful on Free
GitGlow’s everyday local workflow includes precise staging, commits, branches, conflicts, history, blame, and reflog without a GitGlow account.
Local Git for independent developers
A calm Git workspace for your own changes and your agents’ work. Review the diff, stage precisely, and ship with confidence.
Free for private local clones. No account needed.
Follow supported agent activity into the affected checkout. Review the changes, then run checks that become stale when the code changes.
Mark files reviewed and run your checks. Later edits bring files back to your attention and make earlier results stale.
The everyday essentials and the deeper tools that help you finish with confidence.
The full comparison names what each product includes, what requires a paid plan, and where the available evidence is incomplete.
GitGlow’s everyday local workflow includes precise staging, commits, branches, conflicts, history, blame, and reflog without a GitGlow account.
Observed and managed runs can carry repository, checkout, event, and attributed-file context into the same Changes workflow.
Both products include an embedded terminal. GitKraken also documents wider hosted-provider support and shared cloud workspaces. Product fit depends on the workflow you value.
Start with a goal or search an exact control. Every guide explains where to find it, what it requires, what success looks like, and how to recover.
Install GitGlow, open a clone, and create a first reviewed commit.
Review changes, work with refs, resolve conflicts, and inspect history.
Connect supported clients, review events, and open the exact changed files.
Search exact button labels, shortcuts, availability, and recovery behavior.
Keep everyday Git free. Add concurrent workspaces, confident review, managed agents, and release tools for €2.99/month or €29/year.
AI provider subscriptions and API usage are separate.
GitGlow 2.0.5 has been manually checked on macOS. Windows x64 and Linux x86_64/aarch64 packages are build-validated for version, architecture, payloads, sidecars, and checksums.
Local status, diffs, history, paths, previews, and audit records stay on your device. Optional GitHub, agent-provider, billing, and consented analytics connections have separate, explicit data boundaries.
Choose your platform. Open a repository. Get a clearer view.
Everything you need to know about GitGlow's privacy, compatibility, and pricing.
Local status, diffs, history, repository paths, previews, and audit records stay on your device. If you connect GitHub, GitGlow sends only the GitHub requests needed for installed repositories through the GitGlow API. Tokens never enter the desktop webview or MCP responses.
GitGlow publishes macOS, Windows x64, and Linux x86_64/aarch64 desktop packages. GitGlow 2.0.5 has been manually checked on macOS. Windows and Linux packages are build-validated for architecture, version, payloads, sidecars, and checksums without runtime claims.
Free MCP access is read-only. Pro can preview an allow-listed Git or GitHub action, but every MCP-originated write waits for native approval in Agent Observatory while the desktop app is open. GitGlow excludes arbitrary shell or Git commands, destructive cleanup, history editing, force pushes, and PR merges. Release publication is available only through Release Workspace after a fresh guarded preview and explicit final confirmation.
Yes. Free works with a private local clone without an account and includes one active repository or checkout, precise staging, commits, branches, sync, merge, conflict resolution, stashes, tags, topology history, compare, blame, reflog, basic observation, latest Replay, manual Indie Log, analytics, export, and read-only MCP. Free also includes terminal tabs in the active checkout. Pro is €2.99/month or €29/year and adds concurrent terminal sessions, review freshness, verification tied to checkout state, multi-repository fetch, guarded history editing, concurrent workspaces, managed agents, advanced Observatory review and Replays, GitHub integration, Release Workspace, managed Indie Log, and MCP writes. AI provider subscriptions and API usage are separate. Existing subscriptions retain their current terms.
Observed sessions remain owned by their originating Desktop or CLI client. GitGlow monitors supported hook events and independent Git changes, but hides message, approval, and interrupt controls unless the provider exposes a supported channel. Runs launched by GitGlow are Managed and can expose those controls.
Still have questions?
Compare with GitKraken