A small employee count does not mean a product runs on one person's labor. Open code does not mean its maintenance will fund itself. Both descriptions can hide the relationships that supply expertise, real usage, support, and the time to keep responding when something breaks.
The two historical readings in this collection look at those relationships from different directions. Sidekiq's early records show a developer finding a usage setting and a way to fund continuing work. Matrix's protocol and financial report separate the ability to communicate across operators from the arrangements that pay for a common foundation.
Sidekiq beyond the employee count ↗
Read the early hourly-pay calculation, the production testing relationship, commercial support, and a second product that did not repeat Sidekiq's outcome.
Paying for the upkeep of openness ↗
Distinguish the service a hosting customer purchases from the shared compatibility and maintenance work many operators benefit from.
When evaluating a project, draw the work before drawing the organization chart: who supplies each capability, who encounters the failures, who can repair them, and who pays for that time? The relevant comparison is the collaboration saved by a connection against the continuing work needed to keep it useful.