| I'm a netlify customer, and I disagree. Before this pricing change, I paid them $99 a month + bandwidth + build minute overages, with the sort of tacit understanding that until and unless my users need to log in to the site, they aren't billable. After this pricing change, all my developers get a login that they don't need or use, and my baseline price goes from $99 to $693. I technically gained functionality in that developers can now log in and see why their builds failed, but with the rare exception of something being broken in the netlify build image, there is zero utility in that. They can see any of the errors that would be failing the build by looking in their local developer console to see what the linter complains about. Yes, preview and feature branches are handy, as is the ability to rollback to a previous commit's deployed state, but that feature doesn't scale with "number of team members who have access to the repository" nearly as linearly as the pricing model wants it to be. Beyond that, I moved from the $20 a month plan to the $99 a month business plan because of the premium edge network before they imposed a $99 per month per team member pricing change (so really I went from $20 a month + overages to $700 a month plus overages) only to see that now they want me to upgrade to the $3,000 a month enterprise plan to get the edge performance I signed up for. Vercel is tempting. |