I love building and solving problems, rlimit is not just a wrapper over some library, and I believe it fits perfectly into many application stacks.
Most of the comments are about misunderstanding the value - which is completely on me, and I will iterate. I am learning on the way, and I will get better at this, stay tuned.
That is the reason I included the pricing already. I did not want to give "free" vibes. I launched a couple of other products in the past without pricing and it just made sad anyone who started using the product during the beta.
I am not charging for rlimit, it is not even implemented yet. It is free to use while it is in beta, but there will be limits soon-ish, and I want to be upfront about future costs.
Adam here, the author of rlimit, great to see some discussion and pointers on what I need to work on when it comes to pitching the project.
rlimit is a distributed counter, keeping counters in sync in several regions, allowing you to have consistent rate limiting, everywhere.
If you run on a single machine, there are low to no benefits for you in using rlimit. If you use multiple machines (or serverless runtime), you will likely need something to sync counters - this can be Redis, or you could just sign up for rlimit, and have the counter replicated globally out of the box.
This is exactly why I am building https://repeat.dev, create a scheduled task (cron) and do whatever you want quickly and easily. For a cron, we got a https://repeat.new/cron template.
Terraform configuration to deploy HashiCorp Vault to GCP and protect it using Cloudflare for Teams zero-trust products. (Tunnels, Access, SSH Web Terminal)
Most of the comments are about misunderstanding the value - which is completely on me, and I will iterate. I am learning on the way, and I will get better at this, stay tuned.