obligation is a category error here.

Volunteers write code; corporations bundle and sell it. Now those corporations demand loyalty, asking if the architects of their infrastructure owe them anything for the privilege of being used. The tension stems from exhausted maintainers being abused by entities that profit from their labor. Yet "owing" implies a contract that was never signed. In open source, the relationship is structural, not contractual. Code exists as a universal resource; the company is a particular entity appropriating it. To claim the maintainer owes the company is to invert the logic of value. The company exists because it accesses the universal; the maintainer does not exist to serve the particular. If anything, the company owes the maintainer recognition that its profit derives from communal labor. But recognition is not a callable debt. It is merely acknowledgment. The maintainer is free to leave, fork, or demand payment. The company is free to stop using the code. No moral tether binds them, only practical interdependence. The question of debt masks the real issue: power. The company holds market power; the maintainer holds technical power. Asking who owes whom obscures this asymmetry. The cut is clear: stop debating moral obligations and negotiate material terms. If the company wants stability, it should pay. If it relies on charity, it must accept volatility. The corporation expects gratitude for profiting from a structure it did not build.