Plans and shared access

Choose a plan for the capability and repository scope you need. Free supplies managed PR operation and basic repository history. Pro adds historical file exploration and context. Business adds coordinated policies and delegated operation. Readers with current GitHub access can use a connected repository’s available capabilities without buying seats.

Planned prices

These tables are generated from the canonical App plan contract. Prices are consumer totals in EUR, including applicable consumption tax. Annual amounts are charged annually; the monthly equivalent is a comparison, not a monthly payment schedule. The shared Works billing service supplies the authoritative quote and tax treatment when paid enrollment opens.

On a narrow screen, scroll each comparison horizontally. Keyboard users can focus the table area and use the arrow keys.

Purchase	Monthly	Annually	Monthly equivalent when paid annually
Pro, including one connected organisation	€9	€90	€7.50
Business, including one connected organisation	€42	€400	€33.33
Each additional organisation, on either paid plan	€9	€90	€7.50

An extra organization inherits the parent plan’s features, billing cadence and renewal date. A Business connection therefore carries Business coordination; a Pro connection carries the Pro organization allowance. There are no per-reader seats, per-PR fees or purchasable processing credits in this offer.

Capabilities and repository allowances

Capability	Free	Pro	Business
Configured checks, size labels and owned size replies	Included on enabled eligible repositories	Included	Included
Personal private repositories	Up to 3, pooled with one connected organisation	No repository-count limit	No repository-count limit
Public repositories with labelling	No repository-count limit	No repository-count limit	No repository-count limit
Public repositories with history	Up to 10, pooled with one connected organisation	No repository-count limit	No repository-count limit
Included organisation	One, using the pooled Free allowances	One, with up to 3 private repositories	One, without a repository-count limit
Additional organisations	Not included	Paid add-on; same Pro capabilities and 3-private allowance	Paid add-on; same Business capabilities
PR size, lifecycle and basic repository history	Included when history is enabled	Included	Included
Base file measurements needed for policy replay	Retained with history, including excluded observations	Included	Included
File-history exploration, clouds, Turnover and co-change	Preview/approved repository grant only	Included	Included
Premium file-context modules in optional PR briefs	Approved repository grant only	Included	Included
Progressive historical import	Up to 100 recent PRs per selected repository import	Recent first, followed by older recoverable history	Same, with coordinated onboarding
Monthly import allowance	Bounded; value to be published before sale	Bounded; value to be published before sale	Bounded; value to be published before sale
Historical recalculation	Manual per repository	Manual per repository	Automatic/coordinated for linked policies; manual available
Repository-specific policy	Included	Included	Included
Reusable account default	No paid default-library capability	One personal default and one per connected organisation	Shared named policies and a default per account scope
Policy linking, propagation and bulk application	No	No	Included
Automatic eligible repository setup	No	No	Included
Administration	One administering person per managed scope	One administering person per managed scope	Delegated scoped administration
Full administrative audit experience	No	No	Included
Reading currently authorised repository data	No paid reader seats	No paid reader seats	No paid reader seats

Free’s personal repositories and included organization share one pool; connecting the organization does not create another set of Free slots. Each additional Pro organization has its own three-private-repository allowance. Installed but unselected repositories do not consume every allowance automatically. A public repository outside Free’s history allocation can still receive labels.

Live eligible checks, labels and size replies have priority. Historical import, enrichment and broad recalculation may wait or pause under sustained load and GitHub’s rate limits. The monthly import allowance is separate from live PR operation; its numeric values still need publication. Retrying the same logical import or recovering service work does not spend the allowance twice. “No repository-count limit” is not a promise of unlimited compute, storage or instant backfill.

History retention follows the disclosed service policy and the controls you choose. Read the actual retention and archive deadline before enabling collection or buying a service; Security and data explains the distinct ending paths.

Read a repository somebody else funds

Sign in with GitHub and open a connected repository you currently may read. Your own Free account can read the Pro or Business capabilities funded for that namespace. The payer does not have to buy you a reader seat or keep a browser session open.

Funding and permission remain separate. Payment cannot reveal a private repository or confer diffdevil administration. Saved analytical links and each new export request check current GitHub authority; without that access, protected repository names and file paths stay unavailable. A file already downloaded is outside this access check and cannot be recalled. During explicit repository offboarding or confirmed installation removal, a qualifying pre-existing service-account or organization administrator has only the narrow numeric/pathless recovery exception (offboarding and export details). A namespace’s funded features do not turn your unrelated personal repositories into Pro repositories. Premium All repositories aggregates follow your own plan and identify the eligible coverage.

One individual owns the subscription and its organization connections. An organization has at most one ordinary funder; several colleagues cannot stack Pro subscriptions to enlarge the same allowance. Its owner can disconnect or replace the connection, and the funder can withdraw it. A replacement needs the incoming subscriber’s agreement and an available connection. Organization settings and data stay with the organization; its administrators do not receive the payer’s card or unrelated invoices.

Community and commercial self-hosting

Community supplies the basic Free capability set without the official hosted service’s repository-count, import or history-retention quotas. You supply the resources and choose the operating limits. It works without a hosted subscription.

The public Community application does not include rich historical file exploration or Business coordination hidden behind a disabled button. Those capabilities are supplied by separately maintained private application modules. Commercial self-hosting is a separately licensed Contact us deployment option, not another hosted tier or a promise of a Docker adapter. The engine, CLI, library, Actions, extension and free learning surface remain useful independently. Self-host the App explains the operating responsibility.

Try premium history or request Open Source support

The selected one-time preview lets a stable GitHub account capture up to 100 historical PRs from one authorized repository. The resulting premium sample remains explorable and frozen; it does not keep collecting premium updates or enable live premium brief modules. An interrupted capture resumes the same attempt. Reinstalling does not create another entitlement.

The Open Source programme is a manually approved grant for an eligible public repository, including premium file history, corresponding backfill and refresh when its own policy changes. It uses none of the requester’s ordinary repository allowances and can cover a personal or organization repository. It does not grant cross-repository Business policy linking.

Making the repository private stops its public serving and revokes the OSS benefit. An independently sufficient ordinary subscription can continue operation. Grant revocation is not itself a request to delete history. Public GitHub visibility also does not automatically publish an anonymous analytical view: that requires a separate explicit choice and an available public-view implementation.

Change or end a paid plan

Plan & funding separates your current standing, organization connections, a proposed change and the result returned by Works. Inspect the quote’s amount due now, credit, funded period and next renewal together. A redirect back from checkout is not payment proof.

An upgrade starts a new full period and credits unused value actually paid for the old components. Adding an organization partway through a period keeps the existing renewal date and charges the remaining fraction. Downgrades and add-on removals take effect at the paid period’s end. Select which eligible repositories remain before a lower allowance takes effect; the service should not choose arbitrary winners.

Eligible Free operation can continue after premium ends. Premium exploration and processing stop, while authorized export and deletion remain available. Frozen selected state follows the disclosed recovery policy and visible deadline; payment renewal cannot restore deliberately deleted data or override lost GitHub access. The service guide distinguishes a pause, financial ending and repository offboarding.

Beta and participation

Paid beta subscribers retain their existing plan and purchased add-on prices throughout beta and for at least twelve months afterward while continuously subscribed. Already-paid periods are honored, and recovery within ordinary payment grace preserves that protection. This is not a lifetime-price promise or a beta launch date.

When an operator has enabled a participation campaign, an eligible Pro participant can reach its survey from Plan & funding. The App may show an invitation and one reminder after qualifying use. Successful and unsuccessful use can qualify; a repository merely enabled is not yet use. Business is outside this reward campaign. Campaign dates, eligibility and reward amounts come from the actual configured campaign and Works, not from this guide.

You can save a draft, complete the survey, inspect your submitted answers and delete them. Positive, negative and mixed answers qualify equally. The answers stay in diffdevil; Works receives a completion fact to issue the reward. Deleting answers preserves the earned commercial reward. The reward card distinguishes pending delivery, available alternatives, reservation, use, expiry and an unknown result. A monthly or annual preview is created only when you request it; it is not a charge.

Participation is optional, and signing in does not subscribe you to marketing. Source support for the survey and reward journey does not establish a running campaign, real payment or public beta. Releases keeps those availability boundaries visible.