pip install django-ratelimit-backend

There’s nothing to add to your INSTALLED_APPS, unless you want to run the tests. In which case, add 'ratelimitbackend'.




    If you have a custom backend, see the backends reference.

  • Everytime you use django.contrib.auth.views.login, use ratelimitbackend.views.login instead.

  • Register ratelimitbackend’s admin URLs in your URLConf instead of the default admin URLs.

    In your

    from ratelimitbackend import admin
    urlpatterns += [
        (r'^admin/', include(,

    Ratelimitbackend’s admin site overrides the default admin login view to add rate-limiting. You can keep registering your models to the default admin site and they will show up in the ratelimitbackend-enabled admin.

  • Add 'ratelimitbackend.middleware.RateLimitMiddleware' to your MIDDLEWARE_CLASSES, or create you own middleware to handle rate limits. See the middleware reference.

  • If you use django.contrib.auth.forms.AuthenticationForm directly, replace it with ratelimitbackend.forms.AuthenticationForm and always pass it the request object. For instance:

    if request.method == 'POST':
        form = AuthenticationForm(data=request.POST, request=request)
        # etc. etc.

    If you use django.contrib.auth.authenticate, pass it the request object as well.

Customizing rate-limiting criteria

By default, rate limits are based on the IP of the client. An IP that submits a form too many times gets rate-limited, whatever it submits. For custom rate-limiting you can subclass the backend and implement your own logic.

Let’s see with an example: instead of checking the client’s IP, we will use a combination of the IP and the tried username. This way after 30 failed attempts with one username, people can start brute-forcing a new username. Yay! More seriously, it can become useful if you have lots of users logging in at the same time from the same IP.

While we’re at it, we’ll also allow 50 login attempts every 10 minutes.

To do this, simply subclass ratelimitbackend.backends.RateLimitModelBackend:

from ratelimitbackend.backends import RateLimitModelBackend

class MyBackend(RateLimitModelBackend):
    minutes = 10
    requests = 50

    def key(self, request, dt):
        return '%s%s-%s-%s' % (

The key() method is used to build the cache keys storing the login attempts. The default implementation doesn’t use POST data, here we’re adding another part to the cache key.

Note that we’re not sanitizing anything, so we may end up with a rather long cache key. Be careful.

For all the details about the rate-limiting implementation, see the backend reference.

Using with other backends

The way django-ratelimit-backend is implemented requires the authentication backends to have an authenticate() that takes an additional request keyword argument.

While django-ratelimit-backend works fine with the default ModelBackend by providing a replacement class, it’s obviously not possible to do that for every single backend.

The way to deal with this is to create a custom class using the RateLimitMixin class before registering the backend in your settings. For instance, for the LdapAuthBackend:

from django_auth_ldap.backend import LDAPBackend
from ratelimitbackend.backends import RateLimitMixin

class RateLimitedLDAPBackend(RateLimitMixin, LDAPBackend):


RateLimitMixin lets you simply add rate-limiting capabilities to any authentication backend.

RateLimitMixin throws a warning when no request is passed to its authenticate() method. This warning also contains the username that was passed. If you use an authentication backend that doesn’t take the traditional username and password arguments, set the username_key attribute on the backend class to the proper keyword argument name. For instance, if your backend authenticates with an email:

class CustomBackend(BaseBackend):
    def authenticate(self, email, password):

class RateLimitedLCustomBackend(RateLimitMixin, CustomBackend):
    username_key = 'email'

If your backend does not have the concept of a username at all, for example with OAuth 2 bearer token authentication, set the no_username attribute on the backend class to True.

The RateLimitNoUsernameModelBackend can be used for this purpose if you don’t need any additional customization.