Serious software is local. AI is finally catching up.

Look at the apps you actually depend on. The ones you’d notice if they were gone for a day. Your word processor. Your photo editor. Your spreadsheet. Your code editor. Your password manager. Your music library. Your notes app. Your CAD tool, your DAW, your terminal, your PDF viewer. Almost every one of them lives on your machine. They open instantly. They work on the plane. They don’t ask you to log in to start a sentence. They don’t get sold to a competitor in the middle of the project. The file you save today still opens in ten years.

And then there’s the most personal tool you’ve picked up in the last three years — the AI you talk to every day — and it lives in someone else’s data centre. You log in to talk to it. It rate-limits you. It goes down for a day in June. The model you learned the rhythm of gets retired in October. The pattern that every other serious tool on your machine settled into forty years ago is the one your most important new tool refuses to follow. That’s finally changing in 2026. This post is about why it had to.

Open your dock. The list is older than you

It’s easy to forget how much serious software runs locally because it’s so obvious you stop seeing it. Microsoft Office is local. Photoshop is local. Logic Pro and Ableton Live are local. Final Cut and DaVinci Resolve are local. Xcode, VS Code, JetBrains, every IDE you can think of — local. 1Password and Bitwarden have desktop apps. Apple Notes, Obsidian, Bear, Scrivener — local. Adobe’s Creative Cloud has roughly 41 million paid subscribers in 2026, and every single one of them is paying for an application that installs on their hard drive. Microsoft supports about 1.5 billion active Windows devices in 2026; the entire premise is local software running on a machine you carry around.

Even the categories that flirted hardest with the browser quietly walked it back. Google Docs added an offline mode. Figma shipped a desktop app. Slack has a desktop app. Notion has a desktop app. Linear, Spotify, Discord, WhatsApp — all desktop apps. The web-first generation learned, one by one, that there’s a thing users want from a daily tool that a tab can’t deliver: weight, presence, an icon on the dock, a process you can quit.

Every category figured this out years ago

The pattern isn’t even subtle. The deeper a piece of software wades into your life — the more you trust it with hours of work, with money, with private words — the more it lives on your machine. Banking apps cache state. Email clients sync. Password managers are the textbook example: the people most paranoid about cloud leakage are the same people who build vaults that decrypt on your device. The ones we trust least are the ones we run locally. There is nothing accidental about that.

There’s a name for the underlying principle. In a 2019 essay that has since become a small canon, Ink & Switch’s Martin Kleppmann and collaborators called it local-first software — the idea that your data should live on your device by default, that the network is an optimisation rather than a requirement, that when the service shuts down your tool should keep working. The essay wasn’t a manifesto for hermits. It was an argument that the way we already build most serious applications — Pages, Lightroom, BBEdit, your IDE — was the better default all along, and that the cloud era had drifted away from it for reasons of business model, not engineering. The essay reads, six years later, like a description of the obvious.

That’s the framing this post is built on. Local isn’t the weird, brave choice; it’s how every other category arranged itself once it grew up. The interesting question is why one category — arguably the most personal of all — spent its first three years arranged the wrong way around.

AI was the one exception. There was a reason.

Until very recently, there was a perfectly honest engineering excuse for cloud-only AI: the models were genuinely too big for the machine on your lap. GPT-3 was 175 billion parameters. Even compressed to 4-bit weights it wouldn’t fit in 64 GB of RAM, and most laptops still shipped with 8 to 16. Running it locally would have meant ten-second latencies on small queries and outright failure on long ones. The cloud-only architecture wasn’t a product preference; it was the only place the math worked.

So the entire UX of AI grew up in that constraint. You logged into a website. You talked to a model whose weights you couldn’t see. You hit a rate limit and went to make tea. You agreed to terms of service that gave the vendor your conversations to train on. The habits we formed in 2023 around how to use AI weren’t about how AI shouldwork — they were about how it was the only place AI couldwork, on hardware that wouldn’t exist for another three years.

The technical excuse was real. The technical excuse expired in 2024. The habit did not.

The exception just expired

Three things shifted in the last eighteen months and the order matters.

First, the hardware caught up. Apple Silicon’s unified memory architecture means a single 128 GB M4 Max runs Llama 70B at roughly 18-20 tokens per second via the MLX framework — slower than a frontier cloud endpoint, but in the same neighbourhood as a year-ago cloud endpoint, and the quality is GPT-4-class on most tasks. Copilot+ PCs ship with an NPU rated at more than 40 trillion operations per second and 16 GB of RAM minimum. A laptop you can buy at Costco can now hold a model you couldn’t run on a $40,000 server in 2022.

Second, open weights caught up to closed ones. The LMSys Arena gap between the top open-weight model and Claude Opus 4.6 has narrowed to somewhere between 25 and 42 Elo points — small enough that for most real tasks, a blind reader can’t tell which one wrote the answer. Apple now ships an on-device 3-billion-parameter foundation model with its OS, fine-tuned for summarisation, extraction, and tool-calling. Microsoft ships Phi Silica as a Windows component on every Copilot+ machine. The two largest consumer-OS vendors on Earth, in other words, decided in 2025 that on-device AI is now part of the operating system — the same bucket as the file picker.

Third, the tools became boring. Boring is the goal. Ollama crossed 52 million monthly downloads and 168,000 GitHub stars in early 2026. LM Studio has become the Photoshop of local inference for people who don’t want to learn what a Modelfile is. Installing a 70B model is now drag-and-drop. The category looks, to a normal user, exactly like installing Slack.

What you get when AI behaves like every other app

Here’s the part that’s worth saying out loud, because cloud-AI users have spent so long taking the inconveniences as physics that they’ve stopped noticing they’re features that weren’t there a decade ago.

You don’t lose work when the provider has a bad day. On June 10-11, 2025, ChatGPT went down for roughly thirty-four hours after an Azure datacenter lost power. On October 20, 2025, an AWS US-EAST-1 DNS bug took down hundreds of services — including ChatGPT’s sign-in — for fifteen hours. Photoshop did not go down on either day, because Photoshop runs on your machine.

You don’t get rate-limited mid-thought.Local models bill in electricity, not tokens. There’s no “you have used 47 of 50 messages this hour” banner. The interaction feels like opening Notes, not pulling a lever at a machine.

The model you learned doesn’t get retired.A local weight on your disk is yours until you delete it. Cloud providers retire models on a schedule that suits their roadmap, not yours — we covered the eight obituaries in twenty-four months in AI products are mortal. Excel 2003 still opens an .xls file. A 2024 Llama checkpoint will still run on your laptop in 2034, exactly the same way.

Your work is in files you control.A local AI session is a transcript on disk. You can grep it, back it up, export it, delete it, take it to a new machine. A cloud chat is a row in someone else’s database, governed by a terms-of-service document that can change next Tuesday. We dug into the dollars-and-ownership side of this in BYOK vs SaaS AI.

None of these are exotic local-AI superpowers. They’re the baseline you already get from every other application you trust. AI moving local isn’t a privacy moonshot — it’s catching up to the floor.

Where the cloud still earns its keep

Honesty matters here. Local-first AI is not a religion and the cloud isn’t evil. Three places it still wins, today:

• The frontier.The very best models in May 2026 — GPT-5.5, Claude Opus 4.7, Gemini 3.1 Pro — still outclass open weights on the hardest reasoning and coding tasks. When you actually need the smartest model for a thirty-minute problem, the cloud is the right call. The interesting move is to run the daily 80% locally and pay for cloud minutes when the task earns it. We laid out that pattern in the personal-compute shift.
• Tasks bigger than your machine.A million-token context window, a 405B model, a fine-tune you can’t afford to train at home. Cloud is a rented data centre; sometimes you need a rented data centre. The trick is to know which tasks actually require one and which were just routed there out of habit.
• Installation has a tax.Local AI requires you to download a multi-gigabyte file, occasionally pick a quantisation, maybe wait for a model update. Cloud AI requires you to log in. Neither is free. For some users, the install tax is too high and that’s a real preference, not a defect.

The healthy posture is hybrid. A laptop that handles the everyday questions on-device, with a cloud tab open for the hard ones. The same way most people manage photos — Lightroom on the machine, a cloud backup running quietly underneath.

The default is your machine

The argument isn’t that cloud AI is doomed or that everyone should ditch their ChatGPT subscription tomorrow. It’s narrower and weirder: the only thing strange about local AI was that it took this long. We don’t subscribe to a remote Photoshop. We don’t SSH into someone else’s Excel. We don’t open a tab to use a calculator. The browser-only era of AI was a brief, load-bearing detour around a hardware limit that no longer exists. The moment the math worked on a laptop, the gravity that pulls every other category towards the user’s machine started pulling AI too.

That’s the framing worth keeping. The next time someone calls local AI a privacy stance or a developer’s quirk, it’s worth saying back: it’s how serious software always worked. The category that didn’t was the anomaly. We’re just watching it correct.

If you want to see the correction in motion, take a minute and look at your own dock right now. Count the apps that live on your machine. Count the ones that don’t. Then ask yourself which list you trust more for a thing you’ll use every day for the next ten years. The answer to that question is older than AI. It’s older than the cloud. It was true in 1984 and it’s true now, and the category that just figured it out is also the one that’ll spend the most time defining the decade.