| Wow - really surprised at this move by Netlify. It looks like that's a new policy[1] where a "Member" is not just someone who can log in to the Netlify UI and manage a site, but anyone who can trigger a build. Relevant quote from the article outlining the policy changes: > For sites connected to private Git repositories on Pro and Business teams, Git contributors will need to be team members in order to trigger builds. > Teams will only be billed for the number of team members. Currently, Git contributors are people who trigger builds on your team’s site(s). Moving forward, in order to trigger builds, Git contributors who aren’t Team Members, such as people in the ‘Contributors via Git’ section, Reviewers, or people not on the team entirely, will need to have their deploy approved by a team Owner. > Once their deploy is approved, they’ll be invited to become a Team Member and can deploy without approval from then on. If their deploy is rejected, their build won’t run and they will not be added as a team member to your monthly bill. > This change does not apply to sites linked to public repositories or sites on Starter or Open Source plan teams. So it sounds like you could limit your costs by limiting your team Owners. This pricing doesn't seem like a good value proposition to me. I see Netlify as a web host and CDN which has products very comparable to some of Cloudflare's products. In those spaces billing is generally based on usage, not number of seats. What you get from Netlify doesn't scale with the number of seats you pay for. If I have 1 member on the Business plan I'll pay $99/mo and get 1.5TB of bandwidth per month. If I have 5 members on the Business plan, I'll pay $495/mo and still only get 1.5TB of bandwidth. Hardly seems fair or reasonable. [1] https://answers.netlify.com/t/upcoming-changes-to-netlify-pl... |