Datasheet · RC-DEV · rev 5.14.0

One review workflow, whichever VCS the team chose.

Reviewer rules pick the right people from the paths a changeset touches, then hold the merge until policy is satisfied — identically on Git, Mercurial and Subversion. Developers get one workflow instead of three.

Download Community Edition See pricing

Bill of capabilities 10 lines

01 Pull requests across Git, Hg, and SVN git · hg · svn CE 02 Inline comments and task notes git · hg · svn CE 03 Code review tool that scales git · hg · svn CE 04 Reviewer rules and automatic reviewers glob paths → owners EE 05 Branch permissions and protection git · hg · svn EE 06 Customizable workflows per repository whole platform CE 07 Gists for snippet sharing snippets · artifacts CE 08 Web file editor git · hg · svn CE 09 Smart commits and integrations Jira · Jenkins · Slack EE 10 Webhook and REST API whole platform CE

7 of 10 lines free in AGPLv3 all 10 · user / year

Fig. 1.0 Spec

Technical specification

RC-DEV · rev 5.14.0

What it speaks, what it runs on and what it will hold — the questions an architect asks before a feature list matters.

Technical specification for RhodeCode productivity
Area	Supported	Edition
Version control	Git, Mercurial and Subversion, natively — not through a bridge	CE
Protocols	HTTPS, SSH, and Subversion write over HTTP	CE
Review scope	Pull requests and inline review on all three systems	CE
Reviewer rules	Glob paths mapped to owner groups, with required approval counts	EE
Merge gate	Blocks the merge until the rule is satisfied	EE
Editor	Syntax-aware browser editing; commits land in a pull request	CE
Large files	Git LFS and Mercurial largefiles, with per-repository quotas	CE
Automation	REST API over the whole platform, rcextensions and server-side hooks	CE
Integrations	Webhooks, email and Slack in CE; Jenkins, Jira and Redmine in EE	EE

Full requirements and tuning guidance in the system administration docs.

Fig. 1.1 Review

1.1 Review Rules: EE · PRs: CE

One review workflow, whichever VCS the team chose.

Reviewer rules pick the right people from the paths a changeset touches, then hold the merge until policy is satisfied — identically on all three systems.

Path-based reviewer rules with required approval counts

Split and unified diffs with per-file review tracking

Built-in review chat beside the diff, not in another tool

Signed-commit and branch-protection enforcement

Scope All three VCS

Rules Glob paths → owner groups

Gate Blocks merge until met

Fig. 1.2 Editor

1.2 Editor CE

Small changes without a clone.

Edit files in the browser with syntax support and land the result in a policy-compliant pull request — no clone for a one-line fix.

Syntax-aware editing in the browser

Commits land in a pull request, not straight to a branch

Same reviewer rules and protections apply

Snippets and gists for shareable fragments

Scope All three VCS

Output Pull request, policy-checked

Extras Snippets · artifact store

Fig. 1.3 Integrations

1.3 Integrations API: CE · prebuilt: EE

Fits the toolchain you already paid for.

Ready-made integrations for the enterprise stack, event hooks for everything else, and a REST API that covers the whole platform.

Jira, Redmine and third-party issue trackers

Jenkins, Bamboo and generic CI via webhooks

Slack and email notification routing

Full REST API plus server-side event hooks

Trackers Jira · Redmine · custom

CI Jenkins · Bamboo · webhooks

Hooks Pre/post push, pull, merge

Fig. 2.0 Integ

Fits the toolchain you already paid for

Integrate an existing code base with new tools and issue trackers. Automate your workflow to implement faster.

Jira Issue tracker

Redmine Issue tracker

Jenkins CI

Bamboo CI

Slack Notifications

Email Notifications

Webhooks Generic

REST API Automation

Fig. 3.0 Next

Try it on your own repositories

The Community Edition is free forever with unlimited users and repositories. The Enterprise trial is the full feature set for 30 days, enforced by the application itself.

See pricing Download Community Edition Talk to an engineer