secureflow-api-rate-LIMITER 1.0.5

Open-source API rate limiting and protection toolkit with dynamic configuration

API Rate Limiter

Open-source, self-hosted API rate limiting service with JWT authentication, dynamic rate limit configuration, API key management, admin controls, SDK integration, and optional load balancer support.

100% Free & Open Source - No subscription system, no billing, just pure rate limiting protection!

Features

✅ Dynamic Rate Limiting - Configure rate limits at startup and adjust per API key
✅ Zero Subscription System - Completely free and open-source
✅ JWT Authentication - Secure user registration, login, and token refresh
✅ API Key Management - Generate and manage API keys with custom rate limits
✅ Admin Controls - Dashboard to manage users, set custom rate limits, block/unblock keys
✅ SDK Integration - JavaScript SDK for frontend rate limit checking
✅ Real-time Monitoring - WebSocket-based live dashboard
✅ Multi-deployment - Docker, Kubernetes, or standalone Python
✅ Distributed via npm & pip - Easy installation for all developers

Quick Start

You can run this project three ways:

Option A: Docker Compose (fastest)

1. Create your env file:

• Copy .env.example to .env
• Set JWT_SECRET_KEY and ADMIN_TOKEN to strong secrets

2. Start everything:

docker compose up --build -d

3. Open:

• API: http://localhost:8000/health
• Dashboard: http://localhost:8000/dashboard
• SDK demo: http://localhost:8000/sdk
• (Optional gateway) Load balancer dashboard: http://localhost:8080/dashboard

Data persistence:

• SQLite DB is stored at ./data/ratelimiter.db on your host.

Option B: pip install (clean install)

pip install secureflow-api-rate-LIMITER
api-rate-limiter start --host 0.0.0.0 --port 5000

Optional extras:

# WebSocket realtime dashboard support
pip install "secureflow-api-rate-LIMITER[realtime]"

# Advanced gateway/load balancer support
pip install "secureflow-api-rate-LIMITER[loadbalancer]"

Quick checks:

api-rate-limiter --version
api-rate-limiter health-check --url http://127.0.0.1:5000/health

Option C: Local dev (from source)

pip install -r requirements.txt
python app.py

Interactive setup is optional:

• api-rate-limiter start --interactive (or python app.py --interactive)
• or RATE_LIMITER_INTERACTIVE=true

Option D: Kubernetes

1. Build/push the image (or load it into your cluster) and update k8s/deployment.yaml to point to it.

2. Set secrets in k8s/secret.yaml, then apply:

kubectl apply -f k8s/pvc.yaml
kubectl apply -f k8s/configmap.yaml
kubectl apply -f k8s/secret.yaml
kubectl apply -f k8s/deployment.yaml
kubectl apply -f k8s/service.yaml

3. Access it (example):

kubectl port-forward svc/api-rate-limiter-service 8000:80

Then use http://127.0.0.1:8000/health.

First Run (API Keys)

The API server has two auth layers:

• JWT for user accounts (/auth/*)
• API keys for protected endpoints like /data

1) Register a user

Send a request to create a new account:

curl -X POST http://localhost:5000/auth/register \
  -H "Content-Type: application/json" \
  -d '{"email":"[e-mail]","password":"Secret123"}'

3) Login and receive tokens

curl -X POST http://localhost:5000/auth/login \
  -H "Content-Type: application/json" \
  -d '{"email":"[e-mail]","password":"Secret123"}'

4) Create an API key

Use the returned access token:

curl -X POST http://localhost:5000/auth/create_api_key \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "Content-Type: application/json"

5) Call protected data endpoint

curl "http://localhost:5000/data?api_key=<YOUR_API_KEY>"

If you are running via Docker Compose, replace http://localhost:5000 with http://localhost:8000.

Examples

Example 1: Health check

curl http://localhost:5000/health

Example 2: Fetch usage data

curl "http://localhost:5000/usage?api_key=<YOUR_API_KEY>"

Example 3: SDK check

curl -X POST http://localhost:5000/sdk/check \
  -H "Content-Type: application/json" \
  -d '{"api_key":"<YOUR_API_KEY>","endpoint":"/data","method":"GET"}'

Example 4: SDK tracking

curl -X POST http://localhost:5000/sdk/track \
  -H "Content-Type: application/json" \
  -d '{"api_key":"<YOUR_API_KEY>","endpoint":"/data","method":"GET","status_code":200,"response_time_ms":123}'

Dynamic Rate Limiting Configuration

Startup Configuration

By default, python app.py now starts with the built-in defaults:

• Requests per window: 100
• Time window: 60 seconds

To override defaults with environment variables, set:

RATE_LIMIT_REQUESTS=200 RATE_LIMIT_WINDOW=80 python app.py

To enable interactive startup prompts, use either:

python app.py --interactive

or

RATE_LIMITER_INTERACTIVE=true python app.py

If interactive mode is enabled, the app will prompt for rate limit values before starting.

These values become the default rate limits for all new API keys.

Per-Key Rate Limit Configuration

Use the admin endpoint to set custom rate limits for specific API keys:

curl -X POST http://localhost:5000/admin/set_rate_limit \
  -H "Authorization: Bearer <ADMIN_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "api_key": "<YOUR_API_KEY>",
    "requests": 100,
    "window": 60
  }'

Parameters:

• api_key - The API key to configure
• requests - Maximum requests allowed per window (required)
• window - Time window in seconds (required)

Response:

{
  "status": "success",
  "rate_limit_requests": 100,
  "rate_limit_window": 60
}

Check Rate Limit Usage

curl "http://localhost:5000/usage?api_key=<YOUR_API_KEY>"

Response:

{
  "requests_left": 45,
  "requests_limit": 100,
  "window_seconds": 60,
  "total_requests_lifetime": 5000
}

Admin Endpoints

Set Custom Rate Limit

POST /admin/set_rate_limit
Authorization: Bearer <ADMIN_TOKEN>
Content-Type: application/json

{
  "api_key": "rk_live_...",
  "requests": 100,
  "window": 60
}

Get All Users

GET /admin/users
Authorization: Bearer <ADMIN_TOKEN>

Block API Key

POST /admin/block_key
Authorization: Bearer <ADMIN_TOKEN>
Content-Type: application/json

{
  "api_key": "rk_live_..."
}

Unblock API Key

POST /admin/unblock_key
Authorization: Bearer <ADMIN_TOKEN>
Content-Type: application/json

{
  "api_key": "rk_live_..."
}

Gateway (Kong-lite)

This repo also includes an advanced reverse-proxy load balancer (health checks, multiple routing strategies, caching, rate limiting, circuit breaker) in api_shield/load_balancer.py.

• Docker Compose starts it automatically at http://localhost:8080/dashboard.

• Configure backends via env var LB_BACKENDS:

  • Format: host:port[:weight],host:port[:weight]
  • Example: LB_BACKENDS=mock_backends:5001:2,mock_backends:5002:1,mock_backends:5003:1

Install and run load balancer via pip:

pip install "secureflow-api-rate-LIMITER[loadbalancer]"
python -m api_shield.load_balancer

Features & Benefits

• ✅ 100% Free - No subscription, no licensing fees
• ✅ Open Source - MIT License, fully customizable
• ✅ Production Ready - Used in real-world deployments
• ✅ Dynamic Configuration - Change rate limits without restarting
• ✅ Multiple Deployment Options - Docker, Kubernetes, or standalone
• ✅ Comprehensive Admin Panel - Manage users and limits from web UI
• ✅ Real-time Monitoring - WebSocket dashboard with live metrics
• ✅ SDK Integration - Browser-ready rate limiting checks
• ✅ Secure - JWT authentication, API key hashing, IP protection

Environment Variables

Create a .env file in the project root:

FLASK_ENV=development
SECRET_KEY=your-secret-key-here
ADMIN_TOKEN=your-admin-token-here
DATABASE_URL=sqlite:///ratelimiter.db
CORS_ORIGINS=http://localhost:5000,http://localhost:3000
EMAIL_NOTIFICATIONS=false

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Support

• 📖 API Documentation
• 📧 Email: [e-mail]
• 🐛 Report Issues

Made with ❤️ by Samad Rehman

SDK Usage

The repository includes a browser SDK demo page and two SDK API endpoints.

• Demo page: http://localhost:5000/sdk
• Browser SDK script: http://localhost:5000/sdk.js

SDK flow

1. Call /sdk/check before the real request to verify allowance.
2. Send the actual request if allowed.
3. Report request telemetry to /sdk/track.

Example: browser-like flow

curl -X POST http://localhost:5000/sdk/check \
  -H "Content-Type: application/json" \
  -d '{"api_key":"<YOUR_API_KEY>","endpoint":"/data","method":"GET"}'

curl "http://localhost:5000/data?api_key=<YOUR_API_KEY>"

curl -X POST http://localhost:5000/sdk/track \
  -H "Content-Type: application/json" \
  -d '{"api_key":"<YOUR_API_KEY>","endpoint":"/data","method":"GET","status_code":200,"response_time_ms":123}'

Deep Example: Full usage flow

This example shows a complete request flow from registration through rate-limited access.

1. Register user.
2. Login and receive access_token.
3. Create an API key.
4. Check rate-limit allowance with SDK.
5. Call the protected endpoint.
6. Inspect usage.

# Register
curl -X POST http://localhost:5000/auth/register \
  -H "Content-Type: application/json" \
  -d '{"email":"[e-mail]","password":"Secret123"}'

# Login
curl -X POST http://localhost:5000/auth/login \
  -H "Content-Type: application/json" \
  -d '{"email":"[e-mail]","password":"Secret123"}'

# Create API key
curl -X POST http://localhost:5000/auth/create_api_key \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "Content-Type: application/json"

# SDK check before request
curl -X POST http://localhost:5000/sdk/check \
  -H "Content-Type: application/json" \
  -d '{"api_key":"<YOUR_API_KEY>","endpoint":"/data","method":"GET"}'

# Make protected request
curl "http://localhost:5000/data?api_key=<YOUR_API_KEY>"

# View usage
curl "http://localhost:5000/usage?api_key=<YOUR_API_KEY>"

Notes

• Use API_DOCUMENTATION.md for endpoint reference and deeper API examples.
• The default rate limit behavior is tier-based and can be adjusted through configuration.
• For production, prefer Docker Compose or Kubernetes deployment.