EN
Back to the archive

The archive · Developer & Business Tools · Product decision · 2026

Micasa bets home tracking belongs in one local SQLite file — written 99% by an AI agent

A terminal UI storing household projects, repairs, and appliances in SQLite, proving an AI agent wrote 99% of a real app.

Micasa

The betThat home-maintenance knowledge belongs in a file you own — one SQLite file, no cloud — and an AI agent can write almost all of a genuinely useful app's code.Live

What the business is

A free, open-source terminal app that tracks home projects, maintenance schedules, appliances, and vendor quotes in a single SQLite file — no cloud, no account, no subscription.

How it started

The author, an experienced open-source developer, built Micasa because he kept losing household details in notes apps and memory: when to clean the dishwasher filter, which quote to take for the backyard overhaul, the mold found behind the trim. His stated second motive was the experiment — a low-stakes project where an AI coding agent wrote essentially the whole program while he reviewed the code and clicked merge (99% agent-written, by his own estimate).

What happened

The Show HN on 2026-02-19 drew 657 points and 218 comments. Discussion ranged from 'this is an Excel template with a nicer face' to serious plans for LLM-based vendor-quote analysis; the author engaged throughout, detailing the Go/Charm/GORM architecture, the single-file design trade-offs, and GitHub issues already filed for LLM-assisted data entry. The repo later moved from the author's personal account to a dedicated organization.

How it ended up

Still live and open source as of 2026-09-03; repository under the micasa-dev organization, documentation at micasa.dev.

Background

Micasa is a terminal app that tracks home projects, maintenance schedules, appliances, and vendor quotes in a single SQLite file. Its author, an experienced open-source developer, built it out of a simple frustration: household details kept scattering through notes apps and his memory, from dishwasher-filter cleaning dates to competing quotes for the backyard overhaul.

Deliberately, it has no cloud, no account, and no subscription: the whole app state is one SQLite file, with manuals, receipts, and photos stored as BLOBs, so backup is cp. The interface is a Vim-style modal TUI written in pure Go (zero CGO) on Charmbracelet's stack, influenced by VisiData, with a local-LLM chat bolted on as an optional feature that can simply be ignored.

The second, stated bet was about how the code gets written: Micasa was built with 99% of its code produced by an AI coding agent, with the author reviewing and merging. The 2026-02-19 Show HN drew 657 points and 218 comments on the front page; while some commenters argued the broader premise — that most SaaS is a curated CRUD layer over a domain model — the project's single-file constraint answered the loudest objection by construction: there is nothing to migrate, sync, or pay for.

What has to be true

  • Making the entire product one portable file turns backup, migration, and privacy from features into free properties — nothing to sync, nothing to export, nothing a vendor holds hostage.
  • The AI-authored-code claim reframed the launch: instead of only reviewing the app, Hacker News argued about whether agents can build real apps — which is precisely the buzz a solo project needs.
  • Designing to the author's own workflow (VisiData-style keys, documents as BLOBs) meant the tool was genuinely useful to its first user, so the launch presented a real product rather than a demo.
  • Shipping without monetization was the point, not an oversight: the bet is that a household's house knowledge is a personal asset that should never carry a subscription.

What can be applied

When the product is 'your data, owned locally', the constraint set is the pitch: one file, cp for backup, no account — every removed dependency is a removed objection.

Aftermath

As of 2026-09-03 Micasa remains free, open source, and in maintenance: the repository moved to the micasa-dev organization, documentation lives at micasa.dev, and the author has continued his primary work. No monetization or company formation has been announced; the project stands as a demonstration of what a single developer plus an AI agent can ship, and of the local-first thesis that one file beats one SaaS.

Sources

spotted an error? The archive wants to know.

Your turn

You just read one. Describe what you are building, and see who is betting on the same thing.

Free account · 3 free questions · no card

Related cases