Improved workflow and new role for pricing changes
1–10 of 32 posts
Re: Improved workflow and new role for pricing changes
#2I wonder who’s idea it was to charge more based on information that Netlify finds by reading your git commits. Glad I switched to Render.
Re: Improved workflow and new role for pricing changes
#3Wow - these types of changes make it hard to justify using Netlify for static hosting if your contributing team will even possibly grow. Once you get more than 7 contributors for the codebase you have to switch to an enterprise plan ($$) is a scary cliff. What fundamentally changes in hosting costs when I get that extra team member? The pricing structure feels very illogical - are they really adding that much more value in hosting my site just because I have more contributors? Everyone knows exactly what this is - a desperate attempt for cash flow.
Re: Improved workflow and new role for pricing changes
#4Wow - these types of changes make it hard to justify using Netlify for static hosting if your contributing team will even possibly grow. Once you get more than 7 contributors for the codebase you have to switch to an enterprise plan ($$) is a scary cliff. What fundamentally changes in hosting costs when I get that extra team member? The pricing structure feels very illogical - are they really adding that much more va…
Many many SaaS products have a cliff, usually from "free" to "first cost" and that cliff can be pretty substantial.
But going straight from "free" to "enterprise" is steep even for a SaaS. Usually there's a "teams" level between.
Re: Improved workflow and new role for pricing changes
#5I wonder who’s idea it was to charge more based on information that Netlify finds by reading your git commits. Glad I switched to Render.
Render just happens to be on their Series A. What's the difference?
Re: Improved workflow and new role for pricing changes
#6Wow - these types of changes make it hard to justify using Netlify for static hosting if your contributing team will even possibly grow. Once you get more than 7 contributors for the codebase you have to switch to an enterprise plan ($$) is a scary cliff. What fundamentally changes in hosting costs when I get that extra team member? The pricing structure feels very illogical - are they really adding that much more va…
We are actively moving away from netlify for that reason- we have a mostly stable website that maybe sees 10 deploys a month, but usually from 10 different people. I just can’t justify an enterprise account for that.
Too bad, since I actually did like the workflow.
Re: Improved workflow and new role for pricing changes
#7Wow - these types of changes make it hard to justify using Netlify for static hosting if your contributing team will even possibly grow. Once you get more than 7 contributors for the codebase you have to switch to an enterprise plan ($$) is a scary cliff. What fundamentally changes in hosting costs when I get that extra team member? The pricing structure feels very illogical - are they really adding that much more va…
Many many SaaS products have a cliff, usually from "free" to "first cost" and that cliff can be pretty substantial. But going straight from "free" to "enterprise" is steep even for a SaaS. Usually there's a "teams" level between.
Yeah, and they can be stupid expensive for small side projects with a handful of contributors. If you want a Netlify site with a background function that serves 10 visitors a day with 3 people occasionally logging in or pushing code, you pay $57/mo to execute $0.0001 worth of Lambda functions. Maybe it's worth it if things take off, but before then you're paying a lot for very little. So, you host on a DigitalOcean droplet or directly on AWS, and bear a migration cost if you were to choose Netlify as soon as things start growing.
Re: Improved workflow and new role for pricing changes
#8I wonder who’s idea it was to charge more based on information that Netlify finds by reading your git commits. Glad I switched to Render.
Finally a valid use case for git-blame-someone-else
Re: Improved workflow and new role for pricing changes
#9I wonder who’s idea it was to charge more based on information that Netlify finds by reading your git commits. Glad I switched to Render.
I know we like to use new terms to pretend there is innovation but Netlify is a CDN and Render is a shared VM host.
Unless you only host static content, isn’t Render vastly more capabale/different anyway?
Re: Improved workflow and new role for pricing changes
#108 people, at 19 per month, amounts to 8x19x12 = +-1800 a year. adding an 8th person would skyrocket that, if we take the next step up (business) at 99/m, to 8x99x12 = +- 9500 per year.
And that's not even the "enterprise" pricing.
That must be one hell of an improved workflow to increase the price with, probably at least, 400%.