OpenAI banned PewDiePie twice over his homegrown AI model Ajax

The YouTuber trained a local model called Ajax on OpenAI API outputs and lost his account twice.

OpenAI banned PewDiePie twice over his homegrown AI model Ajax

OpenAI banned PewDiePie's account twice, and the reason was straightforward: he used the company's API outputs to train a local model he calls Ajax.

banned getting openai pewdiepie twice

Felix Kjellberg, the Swedish creator who commands one of the largest audiences on YouTube, has spent months running a fine-tuning project on his own hardware. The goal is a fully local language model, one he can run without sending prompts to a remote datacenter. To build the training dataset, he leaned on OpenAI's API, generating text at scale and feeding it into the training pipeline. OpenAI noticed. The company flagged his account for violating its usage terms, which explicitly prohibit using model outputs to train competing AI systems.

This is not a gray area in OpenAI's documentation. The policy on "Competing models" has been public for years, and it states plainly that customers may not use outputs to develop models that compete with OpenAI's offerings. The second ban reportedly came after Jullie attempted to continue the project, possibly by routing around the first suspension. That detail matters, because it suggests OpenAI's enforcement is not a single automated flag but a repeated intervention tied to his identity and payment details.

The technical story underneath the memes is more interesting than the headline suggests. Building a local model means choosing an open-weight base, assembling a dataset, and running supervised fine-tuning, a process where a model learns from input-output pairs. Using a closed commercial API to generate those pairs is called synthetic data distillation, and it is one of the most common shortcuts in the fine-tuning community. It works because a strong frontier model can label problems, write code, or produce reasoning traces that would be expensive to collect by hand.

The catch is that the shortcut depends on permission. OpenAI's terms are designed to prevent exactly this: extracting capability from a paid service and redeploying it as a free or open alternative. Kjellberg's Ajax project sits on the wrong side of that line by the letter of the rules, even if the spirit of a hobbyist fine-tuning experiment on a home machine feels different from a competitor scraping a production API.

Community reaction split along predictable lines. On the r/LocalLLaMA subreddit, where the story surfaced, commenters framed it as top-tier comedy, a famous YouTuber getting slapped down by the very AI labs he helps promote. Others pushed back harder. One recurring argument holds that Kjellberg simply did not read the terms he agreed to, and that the "everyone does this" defense does not change the legal reality. Another thread pointed out the irony that a creator whose channel depends on platform rules was surprised to discover API rules function similarly.

There is also a quieter, more technical criticism worth noting. Several builders argued that synthetic distillation from a single frontier model produces models that inherit its biases, its phrasing, and its blind spots. If Ajax was trained largely on OpenAI-generated text, it would not be a genuinely independent model in the way the project implies. It would be a compressed copy of one provider's behavior, run locally for convenience.

The enforcement question cuts deeper than one creator. OpenAI faces a real tension: its API is a revenue stream, and its outputs are increasingly valuable training fuel for the open-weight ecosystem that competes with it. Every fine-tuning script that hits /v1/chat/completions and dumps the results to a JSONL file is a small instance of the behavior OpenAI is trying to suppress. The company cannot inspect every training run, so it acts on the visible ones, often with the help of automated anomaly detection on usage patterns.

Whether Kjellberg will return to the project after a second ban, and whether he will pursue a model built entirely on open datasets instead, remains unanswered. What is settled is this: as of the bans, OpenAI's terms of service forbid using its API outputs to train competing models, and that rule now has at least two documented enforcement actions against one of the most visible people on the internet.


Source: PewDiePie getting banned twice by OpenAI while making a local model is top-tier