ness VS registry

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

Use AWS Amplify or https://ness.sh

I think you mean something human-friendly on the marketing page, but if you are comfortable with Cloudformation YAML templates, you can find all the resources here: https://github.com/nessjs/ness/tree/main/static/stacks

Next, I plan to add preview environments for new pull requests on GitHub through an official GitHub Action. I'd love to hear if others are finding this tool useful and what features they'd like to see moving forward. Find me on Twitter and/or GitHub (pull requests are welcome!).

You should just keep using hashicorp providers - there's no changes to your codebase required, generally, as long as you don't specify provider sources in long form (as in, you should specify the source as `hashicorp/aws`, not as `registry.terraform.io/hashicorp/aws`). All providers should be available in our registry, and if you're missing any, just submit it[0]. Though as I said, all should be available.

There's also the migration guide you could take a look at[1].

[0]: https://github.com/opentofu/registry/issues/new?assignees=&l...

[1]: https://opentofu.org/docs/intro/migration/

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

It is, btw, why it was so easy for us to spin up a quick-and-dirty registry for our alpha release[0] that basically contains all providers and modules - almost everything is hosted on GitHub.

Right now we're working on the stable registry[1,2], and that's basically the main blocker left to a full stable release. You can track the progress in our weekly updates[3].

Note: Interim Tech Lead of the OpenTofu project

[0]: https://github.com/opentofu/registry

[1]: https://github.com/opentofu/opentofu/issues/741

[2]: https://github.com/opentofu/registry-stable

[3]: https://github.com/opentofu/opentofu/blob/main/WEEKLY_UPDATE...