Google’s Content Offer Pilot Now Buys Code: What Developers Should Check Before Agreeing

Posted on by
Contents show
A two colour screen print of a small teal rectangle being passed into a large coral box, representing the repository delivery that the Content Offer Pilot pays for

Google is paying developers for code. The Content Offer Pilot, which started with content partnerships and was reported in June as an approach to Android app developers, now covers proprietary code repositories, archived prototypes and side projects that never shipped. The pitch in Google's own email is direct: get paid for sharing the code powering your apps, and keep your intellectual property, because the licence is non-exclusive.

For a small studio with a repository of old projects, that sounds like free money. For anyone who has read how Google's parallel payment programme for publishers is going, it sounds like the opening of a negotiation whose terms are not on paper anywhere public. Both reactions are reasonable, and the gap between them is where this article sits.

Here is what Google has confirmed about the Content Offer Pilot, why a company with Google's resources is buying code it could not scrape, and the six questions to answer before anything leaves your repository.

Two documents make up the whole of the public record on the Content Offer Pilot. The first is the invitation email Google sent to selected app developers, and the second is a page on Google's AI site about partnerships to improve its products. Everything below comes from those two documents, from the reporting that reproduced the email in June, and from what any business with a repository should ask for before it hands one over.

What Google confirms, in its own words

The clearest description of the Content Offer Pilot comes from the invitation itself. Google's email invites a selected group of Google Play app developers to “join a confidential content offer pilot”, and describes what it wants in plain terms: high-quality, real-world codebases to help improve Google's developer tools and products.

The email lists the reasons the code is useful, and they are worth reading closely because they describe the purpose rather than the product. Google says real-world code helps it understand complex logic and develop coding evaluations and benchmarks. That is a narrower claim than training a model on your application, and it points at a specific gap in the industry, which is that agentic coding tools are judged on whether they can work inside real repositories rather than on synthetic exercises.

The commercial terms in the email are the part that will decide whether this is a good deal for any given business:

  • The licence is non-exclusive, which means you can sell the same access elsewhere.
  • Google states that the developer retains 100 percent of the intellectual property and that the app remains yours.
  • Google states that you retain the right to monetise your data anywhere else.
  • The invitation does not mention artificial intelligence. A link in the email leads to a page about partnerships to improve Google's AI products, where Google writes that it has “been piloting a partnership program to pay for the delivery of non-public content in a range of media formats”.

The distinction between code for developer tools and code for AI training is not cosmetic. It affects what an agreement might permit, how the material is stored, and whether you can argue later that a use was outside the scope. When the email avoids the word and the linked page uses it, that ambiguity is the first thing to resolve in writing.

The content of the Content Offer Pilot was first reported in June by 404 Media, which reproduced the email after a developer shared it anonymously. Details that a prospective participant would want, such as payment ranges, the list of products that will use the code, and what a standard agreement permits, are not in the public record. Google has not published them, and I have not seen a sample contract.

Why Google is buying code it could not scrape

Companies have been scraping public code for years. Paying for private repositories only makes sense if the material that matters is not public, and there are three reasons to think that is now the case for coding tools. The Content Offer Pilot also fits a broader move toward paid data licensing, in which model developers pay for material they cannot lawfully take.

The first is evaluation quality. A coding agent that looks strong on generated exercises can fail on a real codebase with historical baggage, undocumented decisions and inconsistent conventions. Building benchmarks that reflect that requires real repositories, and the ones worth testing against are usually private. Google's own purpose statement in the email, about understanding complex logic and developing evaluations and benchmarks, matches this need exactly. The Content Offer Pilot is, in effect, an attempt to buy the raw material for those benchmarks.

The second is competitive pressure. 404 Media noted that Google has fallen behind in code generation, with Anthropic's Claude Code and Microsoft's Copilot widely adopted, and argued that buying code suggests the company has not been able to reach the standard it wants using material available on the open web. The tools developers already use for their own work are documented in our guide to how developers supercharge Codex, Claude and Antigravity, and the fact that Google is paying for inputs its competitors trained on for free is a signal about how the coding market is being contested.

The third is that purchased data carries less legal exposure than scraped data, which is the argument every data licensing programme now makes to the businesses it approaches. That motive is visible in a different Google programme. Digiday reported in September that Google has been scaling an “AI contribution pilot” that pays publishers when their content significantly contributes to AI answers in Gemini, AI Overviews and AI Mode, with payouts shown in a Search Console widget that participants describe as a black box. One publishing executive told Digiday that the calculation is opaque and the early returns amount to peanuts relative to advertising revenue, while analysts quoted in the same piece describe these pay-per-value programmes as a cheap way to reduce legal, regulatory and reputational risk at once.

That precedent matters for anyone weighing the Content Offer Pilot, and not because the two programmes are identical. The publisher programme pays for content that already appears in search results, while the code programme buys material that was never public. The lesson is about the shape of the deal: Google is testing payment models across several kinds of non-public material, it has not published how it values any of them, and it can opt participants in and out of its experiments. If you are being asked to name a price for your code under the Content Offer Pilot, the publisher experience suggests that the first number offered will reflect Google's valuation, not yours.

Six questions to answer before you agree

None of these require a lawyer for the first pass. They require an hour with your own repository and a written answer to each. Every question below applies to the Content Offer Pilot as described in the invitation, and to any similar programme that asks for access to a private repository.

1. Which rights are you actually granting?

Non-exclusive is a good start under the Content Offer Pilot, but it answers only one question. Ask what the licence permits: training, evaluation, fine tuning, use in benchmarks that get published, or reproduction in a product that a competitor could buy. Then ask for how long, whether the rights survive termination, and whether Google can sublicense the material to partners or contractors. A perpetual, sublicensable licence over code from a non-exclusive deal is a very different asset from a three year term limited to internal evaluation.

2. Which repositories are in scope?

The Content Offer Pilot explicitly invites archives of prototypes and side projects no longer in use. Those are the repositories with the least review and the most history, and they are usually where the mess accumulates. If a repository contains credentials that were committed once and removed later, they are still in the history, and shipping the history ships the secrets. Decide per repository, not per company, and treat a delivery as a disclosure of everything inside it.

3. What else lives inside the code you are sending?

Production repositories can contain third-party code under licences that restrict redistribution, customer data embedded in fixtures and logs, personal data that answers to privacy rules, and internal documentation that describes how your business works. Selling access to that material is a data transfer with obligations attached, and the Content Offer Pilot does not appear to include any review of those obligations on Google's side. That work is yours.

4. Do you own the code you are offering?

This is the question that surprises people. Code written by contractors, agencies or employees in jurisdictions with different assignment rules may not be yours to license, and client projects certainly are not unless the contract says so. The promise that you keep 100 percent of your intellectual property is worth exactly as much as your ownership of that property. If your team used an AI coding assistant that was trained on restrictive material, that is a separate question from whether you can license your own repository, and it is worth separating the two rather than treating them as one risk.

5. What does payment actually look like?

Google's process has the partner propose a price, with the deal proceeding only when both sides agree. That is a seller-friendly structure on paper and a hard one in practice, because you are naming a number without any public comparable. Anyone entering the Content Offer Pilot should decide in advance whether they want a one-off payment, a term licence with renewal, or a per-delivery fee, and price the material against the value of the work rather than the value of the storage. Also settle the unglamorous parts before delivery: what counts as delivered, what happens to the files afterwards, whether you can audit their storage, and who is responsible for tax in your jurisdiction.

6. What does confidential mean for you?

The invitation describes the Content Offer Pilot as confidential, and the first developer to speak about it did so anonymously because of concerns about retaliation. If you sign, ask in writing what you may say to clients, investors and your own team, and whether participation requires secrecy. If your customers include businesses that require notice before their code or data goes to a third party, confidentiality in the other direction is now your problem. Our earlier coverage of how coding agents were breached is a reminder that the security question and the contract question tend to arrive together.

How to run the test on one repository

Pick the least sensitive repository you own and treat the exercise as a rehearsal rather than a deal. It takes an afternoon, and it produces the answers you need.

  1. Scan the full history for secrets, not just the current state of the code. Credentials that were committed and later removed are still there.
  2. List the third-party components and their licences, and note anything that restricts redistribution.
  3. Confirm ownership in writing: employment agreements, contractor agreements and client contracts all decide whether you can license the repository at all.
  4. Write down the purpose you are authorising. An agreement reached through the Content Offer Pilot should say what the code may be used for, and a purpose that is narrower than the invitation is an improvement worth asking for.
  5. Price the repository against the work that produced it rather than the disk space it occupies, and keep the reasoning in the file.
  6. Record the decision and the correspondence. A decision to sell access to a repository is one you may need to explain later to a client, an investor or an acquirer.

The rehearsal has a second benefit. If you cannot answer those questions for your safest repository, the first conversation about the Content Offer Pilot is premature, and the exercise has told you which housekeeping comes first.

What to do instead, if the answer is no

Selling access through the Content Offer Pilot is one way to turn existing code into revenue, and for a studio with genuinely dead repositories it may be the easiest. The alternatives are slower and larger.

Productising is the well-worn path: the internal tool that saved your team time becomes the thing you sell, which is how a great deal of software, including several of the AI coding tools now competing for your repository, came into existence. Licensing directly to a business in an adjacent market keeps the material private and prices it against a specific outcome. Publishing under an open licence with a paid support layer trades scarcity for distribution. And for teams whose interest is in what the code can earn rather than what it can be sold for, the more immediate lever is usually reducing what you spend on the tools themselves, which is where our list of free AI APIs and the Gemini 4 Argon pricing changes are worth reading.

None of those options requires deciding whether a confidential pilot run by email is a good idea for your business, which is precisely their advantage.

Where the details stop

  • Google has not published payment ranges, the products that will use the code, the term of a typical licence, or a sample agreement. Everything above about the terms of the Content Offer Pilot comes from the invitation text and Google's public page, not from a contract I have seen.
  • The email does not use the word artificial intelligence, while the page it links to describes paying for non-public content for AI products. Treat the purpose as described in the agreement you are asked to sign, not as described in the invitation.
  • The public record on this programme is thinner than the record on the publisher programme beside it. Google has described the code pilot in an invitation email and on a general partnerships page, and the specifics a business would need in order to price its own repository are absent from both.
  • The publisher programme covered by Digiday is a different programme with different participants. I am using it as a signal about how Google has handled transparency in paid content deals, not as evidence about how the code pilot will pay.
  • I have not tested the Content Offer Pilot, have not seen a payment, and have no relationship with Google or with any participant.

FAQ

What is Google's Content Offer Pilot?

The Content Offer Pilot is a Google programme that pays developers and small businesses for access to non-public content, including proprietary code repositories and archived projects, for use in improving Google's developer tools and products. It is a form of data licensing, with the unusual feature that the seller proposes the price. Prospective partners submit material through a portal, propose their own price, and a deal happens only if both sides agree. Google states that the licence is non-exclusive and that participants keep their intellectual property.

Do you keep ownership of your code?

Under the Content Offer Pilot, Google's invitation states that participants retain 100 percent of the intellectual property and the right to monetise the data elsewhere, because the licence is non-exclusive. That promise covers ownership of code that is genuinely yours, which is why the fourth question above about contractors, clients and employment terms comes before any price discussion.

Is the Content Offer Pilot worth it for a small business?

It depends on the repository rather than the company. The Content Offer Pilot pays for access rather than for an outcome, so the question is what that access exposes rather than what the payment is worth. Archived code with no customers, no third-party obligations and no secrets in its history is close to free money if the price is acceptable. Production code that contains client work, credentials, personal data or licensed components carries obligations that a one-off payment will not cover, and the same code may be worth more productised than sold. The responsible test is to take one repository through the six questions and see how many of them you can answer in writing, which is also the cheapest way to find out whether the Content Offer Pilot suits your business.

The short version

Google's Content Offer Pilot now buys proprietary code, offering a non-exclusive licence, retained intellectual property and a price the partner proposes. Google says the material helps it understand complex logic and build coding evaluations and benchmarks, which is why a company that can scrape the open web is paying for private repositories. The risks are not in the headline terms but in the details: which rights the licence covers, what is hiding in the git history, whether you own the code at all, how payment is defined, and what confidentiality stops you saying. Answer those six questions in writing before a repository leaves your hands, and run them once on your safest repository before you decide whether a second conversation about the Content Offer Pilot is worth having.

Sources
Subscription Form