His initial comment describing it: https://news.ycombinator.com/item?id=28504740
I think what they mean is that the data and code itself is libre/free/open [0] [1] but the API access is essentially rate limited for non-paying customers?
[0] https://open-meteo.com/en/licence (CC-BY)
[1] https://github.com/open-meteo/open-meteo/blob/main/LICENSE (AGPL)
I think what they're trying to say is "Our service is completely open source. Our code is open source and our data is open source. We provide reasonable rate limits to our API access for non-paying customers. See our pricing plan if you'd like to become a commercial user and increase your rate limits".
This is not ideal for shared hosting services like cloudflare workers, but is the easiest and privacy-friendly way to limit access to fair-use.
Additionally, weather data is uploaded to a AWS S3 open-data sponsorship and you can run your own API instances (even commercially). The only draw back is, that a lot of data needs to transferred. I am working on a S3 cloud-native approach, but it is still in testing.
The free tier is cross-financed by commercial customers that use the service for energy forecasting, agriculture planing or wild fire prevention. There is no external funding, VCs, or whatsoever, the code is build in public on GitHub and I intent to continue running the free API service as is.
Also, I looked into omfiles for a project recently, I was very impressed with their speed and blown away by the compression ratios!
gnabgib•6h ago