Feature — Traffic Control

Control Every Request. Protect Every Service.

Rate limiting, load balancing, caching, and access control — applied per service and route from a single panel. No YAML. No restarts.

API traffic control and load balancing

Traffic Policies Applied at the Edge

Every API call passes through apiRuler’s traffic engine before reaching your services. Define exactly who can call what, how often, with what payload size — and let apiRuler enforce it.

  • Access Control (ACL) — Whitelist/blacklist consumers and groups per service and route
  • Rate Limiting — Per-consumer, per-service, and global rate limits with sliding window support
  • Request Size Filter — Block oversized payloads before they reach your backend
  • Proxy Cache — Cache responses at the gateway layer to reduce backend load
  • Load Balancing — Round-robin, least-connections, and consistent-hashing across upstreams

Upstream Health Monitoring

apiRuler continuously checks the health of your upstream services. Unhealthy targets are automatically removed from the load balancer pool and restored when they recover — with zero manual intervention.

Active Health Checks

Configurable HTTP health probes per upstream with custom thresholds and intervals.

Automatic Failover

Failed upstreams removed instantly. Traffic rerouted to healthy targets without downtime.

Proxy Cache

Cache API responses at the gateway to reduce backend load and improve response times.

Take Control of Your API Traffic

Define traffic policies at the gateway. No code changes. No service restarts.