Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
ask-netlify
Discontinued A place to submit questions for Netlify to answer in tutorials, podcasts and blog posts
-
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
Hetzner or DigitalOcean with Coolify [0] works great, it's like an open source Heroku that runs on any host, you get git push to deploy, and a bunch of other features built in. It only works on one machine at a time though so it's not like a CDN but for small sites, it's great.
[0] https://coolify.io
been happy with https://render.com/ free static hosting with custom domains.
used to use s3 doe the longest time, but aside from costing a nominal fee, it's so unnecessarily complicated in this day and age.
There are lots of reasons to avoid Netlify.
https://github.com/netlify/cli/issues/739
Does this issue only occur if you have billing info on file?
I'm using the free tier and have no billing info set. According to this https://github.com/netlify/ask-netlify/issues/6#issuecomment...
I believe you can replace most cases (static sites) with Cloudflare Workers [1].
[1] https://workers.cloudflare.com/
CloudFlare pricing is indeed positively ridiculous.
At OpenTofu[0] we’re using CloudFlare R2 to host the providers and modules registry[1]. Bandwidth is free, you only pay for requests.
This already would be great, but there’s more - you only pay for requests that actually hit R2. So with an almost 100% cache hit ratio, we barely register any billable requests.
Recently someone decided to load test us and generated ~1TB of traffic over 1-3 days. All but a few of these requests were cached, so the whole situation probably cost us less than a cent.
[0]: https://opentofu.org
[1]: https://github.com/opentofu/registry
CloudFlare pricing is indeed positively ridiculous.
At OpenTofu[0] we’re using CloudFlare R2 to host the providers and modules registry[1]. Bandwidth is free, you only pay for requests.
This already would be great, but there’s more - you only pay for requests that actually hit R2. So with an almost 100% cache hit ratio, we barely register any billable requests.
Recently someone decided to load test us and generated ~1TB of traffic over 1-3 days. All but a few of these requests were cached, so the whole situation probably cost us less than a cent.
[0]: https://opentofu.org
[1]: https://github.com/opentofu/registry
Vegeta worth a look if you want something a bit more sophisticated: https://github.com/tsenart/vegeta
Yeah there are a bunch of selfhostable things:
Caprover (https://caprover.com/)
Dokku (https://github.com/dokku/dokku)
But people still choose Netlify and Vercel for ease of use I think.
Maybe we need something that's just Netlify. The closest I've seen to the "right" UX is Ness:
https://ness.sh
Yeah there are a bunch of selfhostable things:
Caprover (https://caprover.com/)
Dokku (https://github.com/dokku/dokku)
But people still choose Netlify and Vercel for ease of use I think.
Maybe we need something that's just Netlify. The closest I've seen to the "right" UX is Ness:
https://ness.sh
For static sites, I’m quite happy with CloudFlare Pages + Github deploy action. (https://github.com/cloudflare/pages-action)