One suspects the money folks who approved these changes are the same who keep all of Netlify’s tiers other than the very most expensive one on a six-POP CDN for the whole world --- unlike Netlify’s competitors, each of which provides the same CDN for all its tiers. Have never understood the logic behind this on Netlify’s part, since The Power Of The Brand™ can take it only so far in an increasingly competitive marketplace. And doing this particular pricing structure change at this time, when companies are hurrying to cut costs ahead of what appears almost certain to be a slowdown, is equally weird IMHO.
Improved workflow and new role for pricing changes
11–20 of 32 posts
Re: Improved workflow and new role for pricing changes
#12The price changes here are worrying - I just started planning on how I'd like to switch our frontend applications to be hosted on Netlify and now the pricing is changing from under me.
I can understand charging for developers who trigger deploys; but the whole "teams with more than 7 members must upgrade to enterprise" seems ludicrous. When did 7 people become an enterprise? The last thing I want is to get a 10x bill because an intern triggered a build in my 8 man "enterprise".
Re: Improved workflow and new role for pricing changes
#13I 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
#14I 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?
I'm going to look at Render, but Netlify is more than just a CDN. Having an integrated CI/deployment pipeline is one of the features I've come to use a lot; an engineer can now open a PR and get an autogenerated staging link that be reviewed before going to prod.
That said, if Render supports the same workflows I'll be seriously looking at moving.
Re: Improved workflow and new role for pricing changes
#15Earlier quoted context omitted.
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?
I'm going to look at Render, but Netlify is more than just a CDN. Having an integrated CI/deployment pipeline is one of the features I've come to use a lot; an engineer can now open a PR and get an autogenerated staging link that be reviewed before going to prod. That said, if Render supports the same workflows I'll be seriously looking at moving.
[deleted]
Re: Improved workflow and new role for pricing changes
#16Wow - 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…
I think trying to justify their pricing on hosting alone misses their point. Nothing fundamentally changes in hosting, probably in any environment. However, the development workflow does change with extra team members. Netlify's tools for collaborating are fantastic. I think that's the value they're pricing.
Re: Improved workflow and new role for pricing changes
#17Wow - 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…
> are they really adding that much more value in hosting my site just because I have more contributors
... Yes? Netlify removes a lot of DevOps overhead, and the more people you have working on a site the more DevOps overhead it's eliminating. Imagine, for example, you have non-developer contributors like technical writers or marketers. Netlify makes it easy for them to see local and branch previews that exactly mirror production.
I think this disconnect is from thinking of Netlify as just hosting. (And this is a perception they've been fighting for many years -- rather successfully.) When you realize they're a dev workflow and collaboration tool, this pricing starts to make more sense.
> a desperate attempt for cash flow
It's not an unreasonable thing to do in the current market.
Re: Improved workflow and new role for pricing changes
#18Congrats to the Netlify team! Sounds like changing the customer mix will help them focus on more advanced features rather than needing to supporting the most basic of sites and hobbyists.
It's unfortunate if you're in a business where this pricing is actually expensive, but it seems like it is time for the non-business users to restart the cycle by moving onto the next startup's offering.
Re: Improved workflow and new role for pricing changes
#19Wow - 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…
What's to stop you from not connecting git and have a CI pipeline that runs a deploy for you?
Re: Improved workflow and new role for pricing changes
#20Earlier quoted context omitted.
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 d…
If the value proposition isn't for you, then don't use it. You can't focus on a single feature while ignoring all the others. (ie - your 3 people team would pay $300/mo if you wanted SAML)