Three years ago, I open-sourced a lightweight routing layer for edge deployments. By late 2023, it had 14k GitHub stars and zero revenue. I assumed visibility would naturally convert into income. I was wrong. The transition from community project to sustainable business required a complete rethink of how engineering teams actually budget for tooling. Today, my API infrastructure company brings in $42k MRR with a 91% gross margin. The journey wasn’t about shipping more endpoints. It was about pricing architecture, usage psychology, and aligning my billing model with how developers actually run production workloads. Here’s what worked, what failed, and the exact numbers behind the decisions. The Pricing Shift: From Flat Tiers to Telemetry-Driven Metering Early on, I used a flat $29/month Pro tier capped at 500k requests. Conversion hovered around 1.2%. The flaw was obvious: I was charging for access, not consumption. Developers don’t care about “Pro” labels.…