---
title: "Software as a Coffee"
description: "You can make coffee at home or you can go to a cafe. I think software can be sold the same way. It's open source if you want to host it, and a small fee if you don't want to do the dishes."
pubDate: "2026-11-16"
heroImage: "/saac-cafe-counter.jpg"
typora-root-url: ../../../public
---

**You can make coffee at home**. It's the cheapest way to drink coffee, and with decent beans it can be very good.

However, people still go to a cafe and pay more for the same cup. Nobody there feels robbed. They're paying for someone else to make it, for a table by the window, and for not having to do the dishes after.

I think software can be sold the same way. I've been calling it **Software as a Coffee, or SaaC**.

<figure>
  <img src="/saac-cafe-counter.jpg" alt="A dark blue cafe counter with a coffee grinder and three tan leather stools, and a barista working at the back" />
  <figcaption>Photo by <a href="https://www.pexels.com/@teresa-jang-6930116/">Teresa Jang</a> on <a href="https://www.pexels.com/photo/the-counter-of-a-cafe-11439363/">Pexels</a>.</figcaption>
</figure>

## How it works

**The code is open source**. If you want to run it on your own server, go for it. That's coffee at home, and no cafe owner is upset that you own a kettle. You can rent/buy your servers, update them, keep them clean and healthy.

If you don't want to run a server, you pay a small, sensible fee and someone else runs it for you. They do the updates and the backups, and keep script kiddies away. They're the ones who get up when it breaks on a Sunday.

**It's the same coffee either way**. The hosted version runs the code you can download, with nothing held back for paying customers.

## Bob Young said it in 1999, with ketchup

This isn't a new idea. Bob Young, who co-founded Red Hat, wrote an essay called [Giving It Away](https://www.oreilly.com/openbook/opensources/book/young.html) in 1999. Red Hat was selling Linux in a box for $50 while anyone could download it for free, and people kept asking him how that could be a business.

His answer was ketchup. It *"can be made in your kitchen sink without so much as bending a copyright rule"*, he wrote, and still *"Heinz owns 80% of the market"*. He had a second example, tap water against Evian, and he put that one down to *"a largely irrational fear"* of the tap.

**I like coffee better than both**. Nobody is afraid of the coffee they make at home. They go to the cafe because they like it there.

Two years before Young, Eric Raymond had written [The Cathedral and the Bazaar](https://firstmonday.org/ojs/index.php/fm/article/download/578/499?inline=1). The cathedral is software built in private by a small group. The bazaar is software built in the open by whoever shows up, the way Linux was. The bazaar won that argument a long time ago. But it's an essay about how software gets written, and who keeps it running afterwards isn't its subject. Young's ketchup is about that part, and so is the cafe.

## Why now

For a long time, **the code** was what a software company protected. Writing it took a team and a few years, so you kept it closed and charged for access.

**With AI and agents that's changing**. I had the first version of Slirc about [70% ready to publish after two days](/blog/slirc) and a few bucks in credits. If I can do that, so can anyone who wants to copy it. **The code isn't the moat anymore**, so I don't see the point in hiding it.

The biggest example I know is [ArtCraft](https://github.com/storytold/photocraft). In October, Brandon Thomas and his team published PhotoCraft, a Photoshop written from scratch in Rust with AI, under the MIT or Apache-2.0 license. It's one of 15 apps that go after Adobe's full suite and then some. Thomas had been charged Adobe's cancellation fee more than once, and [his pitch](https://techstrong.ai/articles/open-source-finally-has-its-take-on-the-adobe-creative-suite/) was *"No more subscriptions with cancellation fees. These are yours to own forever."*

In [his talk at CODE Summit 2026](https://www.youtube.com/watch?v=UCL4K36SHp0), he says the first Photoshop approximation took about **24 hours to build**. He also says artists were *"vibe coding their own workflows"* on top of the software ArtCraft gave them.

PhotoCraft is in early alpha, and its [README](https://github.com/storytold/photocraft#readme) says it's *"not yet a Photoshop replacement for daily professional work"*. If a small team can get that far this fast, closed code doesn't protect much.

ArtCraft was also an inspiration for [myArc](https://myarc.dev), the Arc browser replacement I'm building (open-source, no account needed). From PhotoCraft I took the Rust core, and the command-line tool that also runs as an MCP server, so agents can use the app.

Agents make self-hosting easier too. You can ask one to set up a server and it will. That's fine. Home espresso machines got good as well, and the cafes are still full.

What's left to sell is the **convenience**. Someone keeps it running and fixes what breaks. I'd rather charge a fair price for that than for a recipe anyone can now write.

## Slirc works this way

[Slirc.org](https://slirc.org) is a Slack-like chat built on top of IRC. Thomas brings up IRC in his talk too, as what the web lost: *"IRC is like Discord, but you could spin up your own servers that you actually own."*

In the [first post](/blog/slirc) about it I wrote that I'd publish its source, so anyone can install it on a homelab server or a cheap VPS. It's small enough to run on a Raspberry Pi. The source isn't public yet, because I'll run several security checks before people put it on their computers.

For those who don't want to install and maintain it, there's [slirc.app](https://slirc.app). Each team gets its own instance with daily backups, running in the EU, for €29 a month flat, up to 250 users. It's not per seat, the same way a cafe doesn't charge by the sip.

## Is this a new business model?

Not really. Red Hat was doing it in 1999. What's new is **who** can do it. Red Hat needed a company to put Linux in a box. I'm building Slirc before and after work, with agents doing the coding. I'm the architect, and I [review the proof, not the code](https://youtu.be/O_zcc6Xl12g). There's a company behind it, a ZZP, which is what the Netherlands calls a one-person business. It's the same setup a plumber or an electrician has.

That's the part that makes me optimistic about AI. If one person can build and run a product, it can pay for itself with a small number of teams at €29 flat, and nobody has to chase millions of users. And when the source is open, you can leave whenever you want and take the recipe with you. Thomas says Adobe charges up to $200 to cancel a monthly plan early. I've never paid a cafe for walking out. A cafe that knows you can make coffee at home has to be nice to you.

I think we'll get a lot more of these. Small cafes, each run by someone who answers their own email. Thomas says AI *"gives us a chance to take the web back"*, and I agree with him. And I'm one who wants to take it back.

If you make your own coffee, great. If you'd like someone else to do the dishes, there's a [waiting list](https://slirc.app/#waitlist).
