We're All Living in Someone Else's Model Now

A

Adil Sher

Author

Oct 30, 2026
4 min read
1 views
We're All Living in Someone Else's Model Now

Last month, I was debugging a feature in our API layer when a colleague asked me a question that stuck with me: "If we expose our endpoint responses, can someone just scrape them and build a competitor?" I laughed it off, we're a small fintech team in Islamabad, not OpenAI. But then I read about DeepSeek and Moonshot allegedly using GPT outputs to train their own models, and suddenly that casual question didn't feel so hypothetical anymore.

This isn't just an abstract AI ethics debate. It's about what ownership means when you're building anything with machine learning baked into it. And it's a problem that's going to touch every developer's career in the next few years, whether we realize it or not.

The Distillation Reality Check

Let me be honest: model distillation isn't new, and it's not inherently evil. I've used the concept myself when optimizing ML models for mobile deployment. You take a heavy, powerful model, the teacher, and train a lighter one to mimic its behavior. The student learns patterns from the teacher's outputs without copying its internal weights or architecture.

Think of it like this. If I study how a senior architect structures their code, I'm not stealing their code. I'm learning their thinking patterns. Over time, I can apply those patterns independently. That's legitimate knowledge transfer. But there's a threshold where "learning from" becomes "systematically extracting commercial value from," and that's where things get murky.

The technical mechanism doesn't change. What changes is authorization, scale, and intent.

Why This Matters for Production

Here's what keeps me up at night: the economics of AI development are flattening in ways that could democratize the field, or create a free-rider problem that kills investment in frontier research.

If you're a smaller team like mine, you can't spend $100 million on GPUs and training infrastructure. We never could. But if you can query an API repeatedly, collect its responses, and train a competitive model on that synthetic data, suddenly the barrier to entry drops dramatically. That's genuinely exciting for innovation.

But it's also a form of intellectual property extraction if it's done without authorization. There's a world of difference between "I studied this publicly available research paper" and "I built an automated pipeline to systematically extract this company's proprietary model outputs."

What I Actually Think About This

I'm not a purist about IP. I think the current copyright system is broken, and I believe open models like Llama have done more for the industry than closed ones. But I also recognize that someone had to fund the research that made those breakthroughs possible.

What bothers me isn't distillation as a technique. It's the ambiguity around authorization. When you call an API, are you bound by terms of service? Should you be? If a company doesn't want their model distilled, can they enforce that? Or is it fair game because you're just using their public endpoint?

I don't have a clean answer. But I know what I'd do: if I built something valuable, I'd document my process transparently. I'd use synthetic data or public datasets openly. I wouldn't run an automated scraping pipeline against someone else's API, that crosses into unfair competition territory. And if I used distillation, I'd be upfront about where the training signal came from.

A Simple Rule I Use

# Before using another model's outputs for training:

def is_this_ethical(scenario):
 checks = {
 "authorized_or_licensed": False,
 "within_api_terms": False,
 "synthetic_data_generated": False,
 "competitive_intent": True,
 "scale_systematic": True
 }
 
 # If authorized or licensed, it's fine
 if checks["authorized_or_licensed"]:
 return True
 
 # If using public research + synthetic data, probably fine
 if checks["synthetic_data_generated"] and not checks["scale_systematic"]:
 return True
 
 # If you're systematically scraping without authorization
 if checks["competitive_intent"] and checks["scale_systematic"]:
 return False
 
 return "Ask a lawyer"

This isn't legal advice, it's just a mental framework I use to think about what feels right.

The Real Question

Here's what I want to know: Are we going to let the AI industry establish real norms around this, or are we waiting for lawyers to force everyone's hand? Because right now, the rules are being written by whoever moves fastest, not by any consensus on what's fair.

The shift from "biggest model wins" to "most useful model wins" is real and exciting. But it only works if the field stays competitive without becoming extractive.

Source: This post was inspired by "The AI Copycat Problem: When Intelligence Becomes a Training Dataset" by Dev.to. Read the original article

Written by Adil Sher

Full stack developer building high-traffic platforms, AI services, and custom web applications. Explore my portfolio, learn about my background, or get in touch.

Related Articles

Why I Stopped Dismissing Air-Gapped Code Review as "Enterprise Theater"
AI & Machine Learning Oct 29

Why I Stopped Dismissing Air-Gapped Code Review as "Enterprise Theater"

Six months ago, I was talking to a potential client in Islamabad about integrating AI code review into their development pipeline. They seemed interested until they mentioned one thing: their entire codebase had to stay behind their firewall. No cloud services. No external API ca...