We have not been able to connect anyone successfully. One person made it through email account creation but then couldn’t connect their Github because they have a personal account as well. I get wanting more monies, but this mandate feels half baked and we can’t even get developers on to pay you the money. We’ve spent half a day on it with no success, We’re ignoring our CI/CD for now but it’s annoying because we’ve already been sent 88 [Netlify] Heads up - you have a deploy request on your site emails, but never received one telling us of this change.
thank you for that detail, @mwood23 ! i’ll pass it back to the folks investigating.
We are experiencing issues with this as well related to commits/builds. We have many more users committing than we do in our Netlify account. We are right under the Enterprise limit and this will put us well over (which will increase the cost by 15x). Team name VOXO.
Thanks for any assist here!
Heya @mwood23 - I think you are in the wrong place there in that screenshot. That is about connecting a github login to your own personal login, which yes, can only be connected to a single Netlify login. If you need to connect your existing github to that login instead of the other one, you’ll have to disconnect it from the other one where it is already connected. But, you shouldn’t necessarily need to do that at all.
Could you try starting from the approval process on the deploy, instead, to get the invitation created? That’s this screen, which notifications in our UI and via email should have driven you to:
This is the most relevant section of our docs on the topic: Site deploys overview | Netlify Docs
We want to pay. We want to pay a price proportionate to the service. We want to pay a price that scales according to our usage. For me, as the head of a small team with literally seven employees, it’s like a nightmare here. Six people at $20 for $120 I can handle. But seven people doesn’t scale to $140, it scales to enterprise pricing, which seems like that will be more than $99/user, so what is that? What changes after six users that goes from $120 to $1200 (a guess)
I mean I’m just sad about this more than anything. What a crazy day. I am really sincerely happy to pay a little bit per seat. It’s fair. I have a team of fewer than ten. Let me pay for seats. Sure! Let me pay something like what Atlassian charges, or something like that. Let me pay something reasonable. $20 a month is on the higher side, but ok, why not!
The thing that blows my mind is this weird laddering from $20, to $99, to enterprise, for teams larger than six. Six is a small team still, right? I mean six people is a college final project, or a bunch of guys in a garage. Six people is not Oracle or Microsoft. Six people fit in a car.
So what’s the responsibility you have to your community to not threaten the entire livelihood of businesses by announcing usury prices on a product that has a high likelihood of having locked in customers? I guess you can do what you want. But trust is a big part of IT. The sides of the road are littered with companies that exploited the trust off their customers.
Lots of us simply can’t afford what you’re proposing.
Surely, surely, there is a better way to identify your true enterprise customers from your small business users and create an offering that differentiates between them in a way that isn’t going to damage the livelihoods of the smaller customers among your ranks.
5 Likes
We’re unable to connect any of our team’s GitHub users to their corresponding Netlify members, so our entire deploy workflow is stuck in the mud.
No matter what we do it says “Committer is already associated with a different user”.
Also our team has contractors that do some occasional work, and we’d prefer not to invite them into Netlify.
hey jared, could you tell me the team or site name or API ID pleases so we can identify you? thanks.
I’ve just been bitten by this, as a long standing customer it certainly feels like awful change, tantamount to intentionally hobbling the service to squeeze out extra funds, it seems like anywhere from a 2x - 7x price rise for what has been long standing core functionality.
1 Like
hey nathan, could you share with me the Pro team name that is affected by this, or an API ID of a site in that team? thank you
@perry Can you provide some details on your intention before I provide any account identifying information?
With client sites I’d rather you not do anything that suddenly causes us to pay multiples of our existing fees, or heaven forbid screw anything up.
totally. we’ve identified a gap between who we should have notified and who we did not notify, and if we know the team id of the affected site, we can check in our system to see if we sent or did not send an email notifying the billing admin that these changes were coming.
without knowing the team, we also can’t check and see if the amount of committers is below, at, or above the limit. It seems like we mistakenly did not email people who were slightly below or about to bump up against the limit.
thirdly, I don’t know exactly what we can offer (yet - that is decision above my paygrade) to affected people, but we definitely can’t offer anything if we don’t know who is affected.
totally optional to tell us this info, but it would really help get a complete picture of what happened here (we’re still piecing things together) and who was affected.
It is complete madness that a team member can’t deploy if their email doesn’t match their GitHub email. We even tried:
- Create Netlify account with company email address
- User logs in and links their GitHub account
- User tries to deploy using that GitHub account
- User can’t deploy (same “Heads up – you have a deploy request…” email)
If you know the user’s GitHub account, and they’ve linked it to their Netlify account, why wouldn’t you let them deploy? Why do we have to invite their personal email addresses?
Madness. As usual, revenue incrementality trumps developer experience.
hey @rbruels, can you share with me which team is affected? thank you.
@perry Thanks for the explanation. Unfortunately I don’t believe any of that is of assistance to me (or really anyone else in this thread), as you’re just performing a post-mortem on poor communication.
We actually were aware that “a change was coming”, (probably from this post), and had noted as a business that it had a hidden dagger in it buried underneath the positive messaging. It’s just come upon us very quickly and has turned out to be more of a kick in the teeth than anticipated.
The original update probably should have lead with the negative impact on long standing functionality, perhaps drawing attention to the potential for a 200% - 10,526% price increase with no real change in service.
I understand that Netlify don’t see themselves as a “hosting provider”, but that’s ultimately what you are for most people, and when you’re trying to get real work done it’s annoying to have additional “unnecessary work” get generated for you by the host.
5 Likes
The per seat pricing model for Netlify is so backwards and antiquated. This strikes me as a totally lazy cash grab to avoid fixing your pricing model.
Not only that, but it has been completely mismanaged! Like so many in this thread, my company’s processes have been disrupted because we were not notified until things broke. It’s an absolute tire fire for your support people in here.
As for your customers, we’re being forced to buy seats for team members who don’t use Netlify. Those of us who can afford that might today, but those accounts are only around for however long it takes to jump ship.
Charge for build minutes and bandwidth or get out of town.
4 Likes
Here’s an ID for one of our sites: 5c37f959-c7ac-40bd-ab51-beb93179525c
1 Like
This change is simply so predatory and in our current use case eliminates all the value of the product immediately. Charging pricing per contributor doesn’t make any sense but literally seems like a greedy way to trap us as current customers trusting the platform. In my case I needed to deploy a change to production today then had to match the Github account of the developer creating the Pull Request to the current account owner and now I am stuck since at least I don’t see a way to change that linking to my original account, In other words that developer is the only one who can deploy unless I start paying now for more members. Seems simply like a trap designed to pay or go away.
This messed up all our deployment workflows and moving away seems like the only viable alternative.
2 Likes
I’ve just been burnt by this whole change too. Question is WHERE do you actually disconnect a Netlify user from their GitHub Account? Netlify claim that the Netlify account email address which is tied to my GitHub account is connected to some other GitHub user, but I have no idea what account they think it is. I don’t see an explicit setting for this anywhere?
Overall though, this change feels like madness and doesn’t take into account that there are many types of business setups where you’ll use multiple Git accounts to commit to Netlify projects.
Our setup is even very simple where I’ve setup a generic account on GitHub for a “DevOps Admin” which is used to connect things like Netlify and Heroku etc, but I don’t use that account to commit, I use my own personal developer account. That setup is now broken, and for me it’s broken even if I accept that we now need to pay an extra $19/month just so I can use a different Git user.
Netlify has always been a wonderful company with a wonderful service. But one big reason you guys succeed is because you make Continuous Deployment feasible for those of us who don’t have armies of developers to throw at setting up CD pipelines while they do all their other work. This change goes completely against that, and I hope you can unwind it.
In the meantime, my deploys are broken, and I already had a busy day ahead 
2 Likes
When I enquired about getting “anything faster than 48+ hour support” (similar to what regular hosting providers supply), I was quoted that the enterprise plans start at $2000 USD a month (on an annual plan).
That’s our position too, as in our case it’s a 400% price increase for “nothing new” and certainly nothing that we require or asked for.
It’s easier for businesses to just “pay the fee” though than to perform migration work, but it does leave a sour taste in your mouth and get you to reevaluate the providers.
We’re big Netlify fans and have championed the company for years, having been paying customers since Bitballoon, and now we’re going to start testing migrating to Cloudflare Pages, which was comparable before but would now get us increased limits at 1/4 the cost.
I understand that Netlify is VC backed and needs to find an appropriate way to squeeze customers to get a return on investment, but if you want people to “have more Netlify accounts” maybe you should give them a positive reason to need them, rather than just implementing artificial restrictions.
5 Likes
Yeah, I’m starting to get this feeling as well. Without an immediate rollback, I’m going to go to the other stakeholders in our agency and recommend we move to another provider asap due to the complete fiasco of this rollout. There’s too many things to figure out or consider and the ability for us to maintain our clients’ websites is essentially impossible currently. Uncertainty is the last thing you want from a CI/CD.
The piece that is truly perplexing to me is that the support team keeps asking for individual teams’ accounts as if they didn’t notify the right people – this change affected literally every customer, it’ shouldn’t matter. Maybe not to the same extent across the board, but these pricing changes are changes to the terms we agreed to upon signing up and, unlike nearly every other company we work with, we didn’t get one notice prior to today. Not one of the several dozen accounts I manage or help manage were notified in advance. Many of them still haven’t received the post-implementation email. The fact that it is a question whether or not we should have gotten a warning that breaking changes were coming without any phase-in or phase-out period is, frankly, inexcusable. How was there not a notice sent out to all customers that this was changing? How was it not considered that someone might need to have access to multiple teams under different accounts using one github account? I get an email once a year from nearly every vendor – and not from the marketing email – notifying us of what changes are coming down the pike.
I’m dumbfounded. Up until this point, while there have been a few things that didn’t seem to make sense (as there are with any vendor I work with) Netlify pretty much checked every box. Now, I have zero confidence in Netlify as a CI/CD provider if the basic function of the platform can be so carelessly modified this way. I appreciate the support team and engineers often don’t have much agency in such internal matters so @perry I’m sorry you’ve been stuck listening to us all rant today, but if the Netlify leadership can’t come up with a single remedy in a business day, I don’t know what would convince us to stay at this point.
3 Likes