client_ruby VS Rack::Attack

Compare client_ruby vs Rack::Attack and see what are their differences.

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.
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
client_ruby Rack::Attack
1 13
503 5,496
0.8% 0.5%
5.4 6.9
13 days ago 21 days ago
Ruby Ruby
Apache License 2.0 MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of client_ruby. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-12-26.


Posts with mentions or reviews of Rack::Attack. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-10-28.
  • Rails Authentication for Compliance
    5 projects | | 28 Oct 2023
    The first line of defense should be to put rate-limiting on your login endpoints. rack-attack can help with that. I recommend to limit the login attempts to 5 per minute for a username and block the IP for 30 minutes. You should also limit the number of login attempts from the same IP address, but this needs to be adjusted to the application you are working on, because if it is a tool used in classrooms, it might be legit to have 50 logins within a few minutes from the same IP. (I have a few post written about rack-attack)
  • 4 Essential Security Tools To Level Up Your Rails Security
    10 projects | | 31 May 2023
  • Huginn’s IP keeps getting blocked by Kickstarter
    2 projects | /r/selfhosted | 17 Dec 2022
  • rack/rack-attack: Rack middleware for blocking & throttling
    1 project | /r/ruby | 17 Dec 2022
  • Rack-attack gem setup to protect Rails and Rack apps from bad clients
    1 project | | 8 Aug 2022
    Rack middleware for blocking & throttling abusive requests. Protect your Rails and Rack apps from bad clients. Rack::Attack lets you quickly decide when to allow, block, and throttle based on the properties of the request. Using this gem you can save your web application from attacks, we can whitelist IPs, Block requests according to requirements, and many more… Install Rack-attack gem: # In your Gemfile gem 'rack-attack' Enter fullscreen mode Exit fullscreen mode Plugging into the application Then tell your ruby web application to use rack-attack as a middleware. # config/application.rb # rack attack middleware config.middleware.use Rack::Attack Enter fullscreen mode Exit fullscreen mode Once you’ve done that, you’ll need to configure it. You can do this by creating the file, config/initializers/rack-attack.rband adding the rules to fit your needs. You can disable it permanently (like for a specific environment) or temporarily (can be helpful for specific test cases) by writing: Usage Safe listing Safelists have the most precedence, so any request matching a safelist would be allowed despite matching any number of blocklists or throttles. safelist_ip(ip_address_string) Rack::Attack.safelist_ip(“”) Enter fullscreen mode Exit fullscreen mode safelist_ip(ip_subnet_string) Rack::Attack.safelist_ip(“”) Enter fullscreen mode Exit fullscreen mode safelist(name, &block) Name your custom safelist and make your ruby-block argument return a truthy value if you want the request to be allowed, and false otherwise. Blocking blocklist_ip(ip_address_string) Rack::Attack.blocklist_ip(“”) Enter fullscreen mode Exit fullscreen mode blocklist_ip(ip_subnet_string) Rack::Attack.blocklist_ip(“”) Enter fullscreen mode Exit fullscreen mode blocklist(name, &block) Name your custom blocklist and make your ruby-block argument return a truthy value if you want the request to be blocked, and false otherwise. Throttling *throttle(name, options, &block) *( provide limit and period as options) Throttle state is stored in a configurable cache (which defaults to Rails.cache if present). Name your custom throttle, provide limit and period as options, and make your ruby-block argument return the discriminator. This discriminator is how you tell rack-attack whether you’re limiting per IP address, per user email, or any other. For example, if we want to restrict requests other than defined routes and display a custom error page. Error page: If we want to restrict requests/IP and if the request limit increases then send a reminder mail. For Example, we want to allow only 300 requests per 30 seconds after that will restrict requests from this IP till the next 30 seconds interval starting. Get error mail if the limit is extended. Performance The overhead of running Rack::Attack is typically negligible (a few milliseconds per request), but it depends on how many checks you’ve configured, and how long they take. Throttles usually require a network roundtrip to your cache server(s), so try to keep the number of throttle checks per request low. If a request is blocklisted or throttled, the response is a very simple Rack response. A single typical ruby web server thread can block several hundred requests per second. Sample rack-attack.rb file For more information: If this guide has been helpful to you and your team please share it with others!
  • Limiting the amount of calls user can make to an api
    1 project | /r/rails | 11 Nov 2021
    Second vote for rack-attack!
  • Devise and email spam?
    1 project | /r/rails | 4 Nov 2021
    You could use something like Rack Attack to mitigate this type of behavior if it becomes an issue.
  • 10 things I add to every Rails app
    9 projects | | 2 Oct 2021
    The final gem I like to include in all projects is rack-attack. This is a rate limiting tool which is great for throttling dangerous actions in your app to prevent bot attacks or other malicious users.
  • Rails application boilerplate for fast MVP development
    63 projects | | 6 Aug 2021
    rack-attack to prevent bruteforce and DDoS attacks
  • How to prevent scraping/copying data?
    1 project | /r/ruby | 23 Jun 2021
    Check out Rack Attack. It lets you block bots that make requests too fast to be real users, or that request obviously-suspect URLs (/phpmyadmin for example). There are lots of other options, but those are the quick wins IMO.

What are some alternatives?

When comparing client_ruby and Rack::Attack you can also consider the following projects:

prometheus_exporter - A framework for collecting and aggregating prometheus metrics

Metasploit - Metasploit Framework

plex-media-server-exporter - A better Prometheus exporter for Plex Media Server

Rack::Protection - NOTE: This project has been merged upstream to sinatra/sinatra

rspec-rails - RSpec for Rails 6+

Rack::UTF8Sanitizer - Rack::UTF8Sanitizer is a Rack middleware which cleans up invalid UTF8 characters in request URI and headers.

BeEF - The Browser Exploitation Framework Project

Gitrob - Reconnaissance tool for GitHub organizations

Brakeman - A static analysis security vulnerability scanner for Ruby on Rails applications

rack-throttle - Rack middleware for rate-limiting incoming HTTP requests.

SecureHeaders - Manages application of security headers with many safe defaults

Devise - Flexible authentication solution for Rails with Warden.