## the manifesto

# why open source

Most tools you rent are tools you could own. The code isn't the hard part — the hard part is someone sitting down and building the boring, useful thing without a growth team attaching strings to it.

So that's the whole initiative: one useful tool, built in one weekend, shipped as MIT. Ten of them. Twenty, if the weekends cooperate. No open-core bait, no enterprise tier holding the good features hostage, no license that turns "free" into a lawyer's homework. The README is the only documentation, because if a tool needs more than a README, it missed the point.

## the constraint is the feature

A weekend is a filter. It forces every project down to the version of itself that actually matters — the five features people use, not the fifty they compare. What ships is small enough to read, small enough to trust, and small enough to run yourself.

## then why is there a paid plan?

Because the same content renders two ways. Free means the code, not our servers. If you'd rather skip the setup, the subscription buys hosting, backups, and a human answering email — the code underneath stays identical and stays MIT.

$ cat plan.md — you run it

**every feature**, no gates
**your data**, your servers
**₹0**, forever
*support:* github issues
*setup:* a saturday morning

rendered — we run it

Every feature, no gates

Your data, our servers

A small subscription, monthly

Support: email, a human replies

Setup: there isn't any

Same markdown. Different rendering. That's the entire business model.

## the rules

  1. Every repo is public and MIT. No exceptions, no relicensing tricks.
  2. One README per project. No docs sites, no wikis.
  3. Scope is fixed before the weekend starts. Feature requests become new projects, not bloat.
  4. If it can't be self-hosted, it doesn't ship.