Skip to main content

Six AIs Said Graphify Uploads Your Code. I Checked.

Jamie Watters

Operational resilience and AI delivery practitioner.

Six AIs Said Graphify Uploads Your Code. I Checked.

Watch on YouTube →

Six AI models told me, with total confidence, that Graphify uploads your code to a server. They were wrong. So I ran it myself, measured what actually left the machine, and found a real privacy trap: just not the one they warned about.

The honest verdict: the token savings are real (I measured 47-83% less context on my own A/B test), but only on code-heavy repos, and the default build quietly phones a model API if you have a key set in your shell. "Local-first" has fine print.

What's in this video:

  • What Graphify actually is, minus the hype
  • Why the viral "71x fewer tokens" number is a cherry-pick
  • My own A/B test and the real numbers
  • The privacy trap: a default that uses a key you set for something else
  • How to run it genuinely local (strip the key, --no-label, watch zero in / zero out)

I build with AI in the open and show you what actually happened. Real code, real numbers, no hype.

No paywall, no sponsors. If this saved you some time, you can buy me a coffee.

☕ Buy me a coffee

Get the next one in your inbox

I build with AI in the open and write up what held and what didn't. Real numbers, the failures before the wins.

Share this post