Nova Aegis Smart Ip Blocker Laravel Package

Product Decisions This Supports

• Abuse and rate-limit roadmap: Informs whether IP-level blocking for login, signup, forms, and lightweight APIs is delivered in-app via this package or deferred to edge/WAF infrastructure.
• Build vs. buy: Provides a credible "buy/adopt" option versus custom Laravel middleware, reducing engineering scope for a commodity security concern.
• Feature scoping: Threshold and time-window behavior (visits counted against a clock) maps directly to product policy decisions such as "block after N attempts in M minutes" per surface.
• Release risk and upgrade planning: v1.2.0 is an internal-only refactor (blocker now takes a Visit and reads time from a PSR clock; disable command delegates to DisableSmartIpBlocker) with explicitly no application-facing change — supports a low-risk upgrade decision and keeps the public contract stable.
• Testability/QA investment: PSR-clock injection makes time-window logic deterministically testable, supporting reliable regression coverage and reducing the cost of tuning thresholds.
• Operational tooling: The disable command and DisableSmartIpBlocker action support incident-response and support workflows (temporarily lifting blocks).

When to Consider This Package

Consider adoption when:

• The product is a Laravel/PHP application and the team wants a composer-installable, framework-native abuse control rather than a new vendor platform.
• Requirements are simple-to-moderate: IP-based blocking driven by visit counts within a configurable time window (e.g., login, forms, low-volume APIs).
• The team values clean architecture and testability (clock injection) and wants deterministic tests for time-based logic.
• Traffic volume and topology allow per-application blocking without a shared distributed store.
• There is a need for operator-facing controls (artisan disable command) during incidents.

Look elsewhere when:

• Protection must be distributed/global across many nodes — use Redis-backed rate limiting, a WAF, or an edge provider (Cloudflare, AWS WAF).
• Requirements include geo-blocking, IP reputation feeds, sophisticated bot/fingerprint detection, or managed DDoS mitigation.
• Compliance-grade audit logging, SIEM integration, or long-retention evidence is required.
• The stack is non-Laravel or polyglot and a framework-agnostic control plane is preferred.
• Adversaries are expected to rotate IPs at scale, where IP-only blocking is structurally insufficient.

How to Pitch It (Stakeholders)

For executives: This is a low-cost, low-risk, framework-native control for a common abuse problem (credential stuffing, form spam, scraping). It avoids building and maintaining bespoke security middleware and requires no new infrastructure. The v1.2.0 release is an internal refactor only — no behavior change for applications — signalling maturing architecture and a safe, low-effort upgrade.

For engineering: The package cleanly separates the blocking decision from the HTTP request (blocker consumes a Visit and a PSR clock), which improves testability and decoupling, and the disable command now routes through DisableSmartIpBlocker for a single, consistent disable path. Integration is standard Laravel; upgrade risk from v1.2.0 is negligible. Caveat: it is IP-based and in-application, so plan to complement it with edge/WAF controls if you need distributed or reputation-based protection at scale.