When my team cut our monthly Netlify costs by $1.5k, Netlify didn't inquire why, contrasting with GCP's prompt response to a similar spending reduction. Our departure from Netlify was due to significant bugs in Netlify's Next.js Edge and double billing us when Git contributors didn't map cleanly to Netlify accounts, despite us using Github OAuth. Support individuals were great, but it seems like their advocacy for us fell on deaf ears within the Product/Engineering camp.<p>Even more puzzling was that a few months prior, their partnerships team had been working with us to get our customers' ecommerce storefronts on the platform. Netlify's (then) head of partnerships left and nobody else followed up ever. Our customers are now pointed at Fly.io instead, and everyone is quite happy with that recommendation.<p>My anecdote, and this article, seems like evidence of Netlify's reactivity to Vercel over customer-oriented growth. Vercel, in contrast, is more focused on developing open-source projects that organically brings people in.