Rightmark vs pre.dev: code licensing and sourcing

Rightmark's code route Rightmark, 18 Oct 2026 (opens in a new tab) and buyer process Rightmark, 21 Oct 2026 (opens in a new tab) describe those steps.

Consider pre.dev when runnable coding tasks are the purchase. The useful comparison is the proposed data transaction. A coding-assistant subscription, a repository license and a task environment should not share one price comparison.

We publish this comparison at Rightmark. Our recommendation follows the fit described below; neither provider's public material establishes a universally better payout or lower buyer cost.

Rightmark's fee and approval details come from its Trust page, updated October 18, 2026 Rightmark, 18 Oct 2026 (opens in a new tab). The pre.dev evidence used here is a technical article published September 4, 2026 pre.dev, 4 Sep 2026 (opens in a new tab), not an owner contract. Unknown contract terms are questions to resolve, not evidence of a disadvantage.

Start by writing what the buyer expects to receive. Is it code with its history? A collection selected for a particular language or engineering pattern? A task that an agent attempts in a specified environment? A bundle can include more than one, but the bundle needs to say so.

Rightmark's code page describes private repositories with full Git history. That does not mean every repository is already packaged for a buyer's evaluation system. The owner can have a useful archive while the buyer still needs work on documentation, dependencies or acceptance criteria. Source-code licensing preparation Rightmark, 18 Oct 2026 (opens in a new tab) explains the rights and technical evidence to assemble.

These are procurement fields, not a claim that either provider includes everything by default. A test directory in a repository may answer an inventory question while leaving the runnable-task requirement unresolved.

Ask both: What exactly is the licensed unit, and which preparation or evaluation work is included in the quote?

Rightmark states that owners pay nothing upfront. On standard licenses, it takes no deduction from the owner's payout and the buyer pays its fee on top. Premium and bespoke arrangements have a share agreed in writing. That distinction makes the fee payer visible; it does not establish the size of the final offer or make the buyer's total bill lower. Rightmark's published fee model Rightmark, 7 Oct 2026 (opens in a new tab) and route terms Rightmark, 18 Oct 2026 (opens in a new tab) are the starting point.

For an owner, the useful comparison is what reaches you for the rights you grant. For a buyer, it is the complete cost of obtaining an acceptable deliverable. Those are related calculations, but they are not the same number.

Ask each provider to return the following against one fixed scope:

• The asset and version covered, including whether workspace records or derived tasks are bundled with code.
• The owner's proceeds and the party paying any intermediary fee.
• Any preparation, review or transfer charge, with its calculation basis.
• The payment event: signing, accepted delivery, a later license or another stated milestone.
• What changes on another license, an expanded grant or an additional deliverable.

A code-only proposal and a proposal including company records cannot be compared solely by headline amount. Nor can a non-exclusive grant be treated as equivalent to a broader exclusive commitment. Put the differences beside the amount before deciding which offer is better.

The dated pre.dev source reviewed here does not establish its owner payment terms. Request the current agreement and quote. Do not substitute the price of its software product or assume its economics match Rightmark's.

Ask both: For this exact grant, what reaches the owner, who pays each cost, and what event makes payment due?

Owners often need a way to assess readiness before deciding whether to share source. Rightmark's Repo Check, updated October 21, 2026 Rightmark, 21 Oct 2026 (opens in a new tab), runs locally and produces share.json, a file of counts and fixed labels. That step does not upload source code.

Its limits matter as much as its convenience. The report does not establish ownership, consent, the absence of third-party material, legal clearance, buyer demand or a license price. Use it to identify what needs review, not to declare the repository ready for any use.

Keep the initial assessment separate from later access:

Rightmark's code route can involve connecting a Git host to a licensing partner chosen for the deal after signing. Local assessment is therefore not a promise that source never leaves your environment. The code-route explanation Rightmark, 18 Oct 2026 (opens in a new tab) sets that boundary out.

Ask both: What must leave my machine first, and what later agreement authorizes source access?

Retaining ownership does not necessarily mean approving every subsequent transaction. On Rightmark's standing code route, the initial agreement covers later non-exclusive licenses without a further approval each time. Withdrawal applies to code that has not been licensed yet. Read that condition before treating repeat licensing as a series of separate decisions. Rightmark's route-specific approval terms Rightmark, 18 Oct 2026 (opens in a new tab) distinguish code from company archives.

The scope should also distinguish code you control from material requiring another party's permission. Rightmark's preparation guide identifies client code, contractor assignments and third-party components as review areas. A repository can combine these, so an owner's own contribution is not a sufficient description of the whole archive. The rights checklist Rightmark, 18 Oct 2026 (opens in a new tab) provides the preparation path.

Use a separate line for each question that could change the grant:

• Is the proposed use corpus training, evaluation, task creation or a defined combination?
• Which recipient categories and sublicensing or derived-use permissions are included?
• Which client-owned components, dependencies or confidential records are excluded?
• When is a recipient identified, and can business-conflict recipients be excluded under this route?
• What remains licensed after withdrawal, expiry or termination?

These are questions for the actual agreement. They do not imply either provider has a particular unpublished restriction or approval policy. If rights are uncertain, narrow the proposed scope and resolve the uncertainty before promising access.

Ask both: Which permissions are decided when we sign, and which decisions, if any, come back to us later?

In its September 4 analysis of two coding tasks, pre.dev shows how toolchain differences can distort grading. Tommy's practical test is “whether the agent can execute the thing that will judge it.” Read the technical analysis pre.dev, 4 Sep 2026 (opens in a new tab).

That is a useful prompt for procurement, not a verdict on a provider's entire catalog. Ask the engineer reviewing the sample to write an acceptance rule that another reviewer can execute. 'Looks useful' leaves too much room for different expectations after delivery.

For a corpus, that rule might concern the agreed versions, fields, formats and exclusions. For a task asset, add the environment, run command and behavior being assessed. Keep infrastructure failures distinct from the outcome the task is intended to measure when agreeing the evaluation method.

Rightmark's buyer process starts with a written scope and representative scrubbed samples under NDA for evaluation. Its sample guide, updated October 18, 2026 Rightmark, 18 Oct 2026 (opens in a new tab), expressly separates sample fit from a license, price, acceptance or full-collection quality. Permission to inspect a sample should not be assumed to authorize training on it.

Ask for the final acceptance and mismatch process in writing. A useful sample does not itself answer what happens if the delivered batch differs in coverage or cannot meet the agreed check.

Ask both: Which checks can we run before purchase, and how will the agreement handle a delivery that fails them?

Copy this into an internal document. Fill it with the owner, technical reviewer and person approving the purchase. Use evidence references rather than pasting private source, credentials or personal information. This is an editorial worksheet, not a contract or automated Rightmark assessment.

For each row, record the evidence, the buyer's acceptance rule and a status: confirmed, unknown or not applicable.

An illustrative scenario: a repository includes tests, so the inventory row is complete. Nobody has yet established whether they run in the proposed environment. The environment and acceptance rows remain unknown. This is not a customer example or evidence of a fault in either provider.

Use the unanswered rows to shape the next request. An unknown sample format may need clarification; an unresolved right to license material may require excluding it until the responsible people resolve the issue. Completing a table cannot replace that work.

Its published task analysis offers an engineering buyer a concrete evaluation starting point. If task environments are the main procurement requirement, ask for a current representative asset, its commercial terms and the checks your team can run. Use the card to make the evaluation specific.

An owner considering a pre.dev proposal should obtain the actual owner agreement and compare it with the same grant offered elsewhere. The evidence gap in this article is a reason to request terms, not a reason to reject a potentially suitable offer.

Rightmark is our recommended starting point for a code owner who wants to assess readiness locally, understand the published standard fee basis and clarify the grant before committing source. Start with Repo Check Rightmark, 21 Oct 2026 (opens in a new tab) or the appraisal, then address the rights and agreement questions the result cannot answer.

For AI buyers, start with Rightmark when you can define the data requirement and want to evaluate a scoped sourcing proposal, route ownership evidence and a permitted sample. Send that requirement through the buyer request path Rightmark, 21 Oct 2026 (opens in a new tab) with the acceptance card. A request starts scoping; it does not establish current supply, a final quote or acceptance. Rightmark does not take health data yet.

If neither proposal resolves the essential rights or acceptance questions, pause the transaction. The best next step is the one that makes the intended exchange clear enough for both sides to approve.