Ip Access Laravel Package

Product Decisions This Supports

• Feature: IP-based access control – Add whitelisting to admin panels, internal tools, or APIs without building custom middleware.
• Build vs. buy – This package offers a ready-made, configurable solution (middleware, config whitelist, IPACCESS_WHITELIST env) that avoids custom security code and maintenance.
• Roadmap: optional Nova integration – The bundled Nova resource remains available for teams using Laravel Nova, but v2.8.0 makes Nova an optional dependency, so the core middleware works independently.
• Use cases – Restricting staging environments, protecting admin routes, enforcing compliance (e.g., only corporate IPs), and adding a lightweight layer before more complex auth.

When to Consider This Package

• You need simple IP whitelisting in a Laravel app with minimal configuration.
• You already use (or plan to use) Laravel Nova and want an admin UI for managing allowed IPs.
• You prefer environment-driven configuration (IPACCESS_WHITELIST) over database-backed rules.
• Look elsewhere if you need dynamic IP sets, geo-blocking, rate limiting, or full RBAC. This package is focused on static whitelisting via middleware and config.

How to Pitch It (Stakeholders)

• Executives: A low-effort security control that reduces exposure of sensitive routes and helps meet access‑restriction requirements. v2.8.0 removes the hard Nova dependency, lowering adoption cost for teams not using Nova.
• Engineering: Drop-in middleware and config whitelist; works with or without Nova. The Nova resource is now optional (suggest), so you can adopt the core feature without pulling in Nova. Simple to test and deploy via environment variables.