If you use Netlify in the free tier you cannot automatically go to pro tier either. Yet they will charge you for bandwidth > 100GB, and THERE IS NO WAY FOR YOU TO SWITCH THAT OFF, even in the free tier.
"Should be fine" is exactly what is not the case here. Better check your Vercel terms again.
Would be for a new business. Not a fan of introducing this sort of tail risk & whatever other risks I don't even know about for their managed service, when there are simpler ways to host I've done for years.
That sounds like a company that is happy to ignore customer pain. Agree, default-on telemetry that cannot fully be disabled is a red flag that on their side, the people with development experience have no say.
This seems like a lot of brouhaha about nothing. They just recorded the fact that a user opted out of telemetry, they didn't stealthily send telemetry against user wishes.
Doesn't make me feel great about Vercel either (which I was looking at)
Id recommend avoiding Vercel like the plague. Their entire business model is poorly aligned with your interests as a customer.
Vercel has spend management controls, setting limits and SMS alerting: https://vercel.com/blog/introducing-spend-management-realtim...
Why? If you use Vercel in the Free Tier you cannot automatically go to the Pro tier.
You need to manually upgrade.
Unless you need more than the Free-Tier Vercel should be fine.
If you use Netlify in the free tier you cannot automatically go to pro tier either. Yet they will charge you for bandwidth > 100GB, and THERE IS NO WAY FOR YOU TO SWITCH THAT OFF, even in the free tier.
"Should be fine" is exactly what is not the case here. Better check your Vercel terms again.
3 replies →
Would be for a new business. Not a fan of introducing this sort of tail risk & whatever other risks I don't even know about for their managed service, when there are simpler ways to host I've done for years.
There are lots of reasons to avoid Netlify.
https://github.com/netlify/cli/issues/739
That sounds like a company that is happy to ignore customer pain. Agree, default-on telemetry that cannot fully be disabled is a red flag that on their side, the people with development experience have no say.
This seems like a lot of brouhaha about nothing. They just recorded the fact that a user opted out of telemetry, they didn't stealthily send telemetry against user wishes.
They removed this call in the meantime [0].
[0] https://github.com/netlify/cli/pull/740/files