Wednesday, April 8, 2026Amsterdam

Colophon · Vol. I

About Entropedia

A practical archive for operators who buy, build, and run small software businesses — written like a handbook, organized like a library, refused like an editor.

Entropedia exists because the operator content space is full of opinions and short on craft. Most of what gets written about small software is either listicles, recycled funding news, or breathless takes from people who have never actually owned the workflow. This site is the opposite: structured archives, cited comparisons, judgment that earns the page it sits on.

Every entry is built from the same five primitives — guides, comparisons, directories, glossary entries, research — wrapped in the same visual language. The intent is that a returning reader can find any page in three clicks and know exactly what kind of answer it will give them.

Entropedia is part of Entrolab, a small venture studio working across software, distribution, and operator tools. The library is the public surface. The studio is what funds and tests the ideas behind it.

What this site is

  • A structured archive of guides, comparisons, directories, glossary entries, and research about small software.
  • An opinionated editorial filter — every page must hit at least two of: original synthesis, cited sources, practical utility, strong opinion.
  • A long, slow build. Quality over volume. Updated entries over new ones.
  • Free, open, and ad-free. No tracking beyond basic analytics. No newsletter pop-ups.

What this site isn’t

  • Not a SaaS blog. Not chasing keywords. Not optimizing for hot takes.
  • Not a community, forum, or directory of paid placements.
  • Not affiliate-driven. Tools and marketplaces are listed by editorial judgment, not partnership.
  • Not built for AI engagement. Pages are written to be read by an operator at a desk.

Editorial standards

Every published page has gone through ten states: idea, research, outlined, drafted, reviewed, fact-checked, ready, published, and eventually either updated or archived. High-stakes pages — those touching legal claims, deal mechanics, or specific marketplace recommendations — get a manual review pass before publishing.

When pages drift out of date, they move to needs_update and stay there until corrected. The editorial board lists everything currently in flight so the work is legible from the outside.