Weave Code
Filament Developer Gate Laravel Package
tomatophp/filament-developer-gate
Filament plugin that protects selected routes, pages, and resources behind a static developer password using a simple middleware or trait. Includes login screens, logout actions and confirmation, plus an optional admin panel plugin.
Secure your selected route by using a middleware with static password for developers only
Frequently asked questions about Filament Developer Gate
- How do I install tomatophp/filament-developer-gate in a Laravel project?
- Install it with composer require tomatophp/filament-developer-gate. Then register the plugin in your Filament panel provider by calling FilamentDeveloperGatePlugin::make() on the panel instance. After that you can apply the middleware to routes or use the InteractWithDeveloperGate trait on pages and resources.
- Does filament-developer-gate support Laravel 12 and Filament v5?
- Version 5.0.0 explicitly supports Filament v5 and declares Laravel 12 and 13 support. The v4 branch continues the Filament v4 line, so choose the package constraint that matches your Filament major. Pin deliberately instead of using a floating version, and confirm whether Laravel 13 support is GA or pre-release in composer.json before adopting it.
- How do I protect a specific Filament resource or page with the developer gate?
- Add the InteractWithDeveloperGate trait to the Filament page or resource you want to protect. The trait integrates the developer gate login flow with Filament's page and resource lifecycle. You can also apply DeveloperGateMiddleware directly to route groups for more granular control.
- Can I use the developer gate middleware on regular Laravel routes without Filament?
- Yes. The DeveloperGateMiddleware can be attached to any Laravel route group, not only Filament routes. This lets you gate debug endpoints, staging dashboards, or other internal routes behind the static developer password. The package's main value is Filament integration, but the middleware concept works for generic Laravel routes.
- Where should I store the static developer password?
- Store the static password in an environment variable or a secrets manager rather than committing it to source control. Rotate the password regularly and restrict access to the configuration values. Because the gate uses a static password, it is best suited to internal developer routes and staging gates, not full user authentication.
- How do I add a logout button or action to a gated page or resource?
- Use the InteractWithDeveloperGate trait to expose a logout action on your gated page or resource. The package includes login screens, logout actions, and a logout confirmation flow. This gives developers a clear way to lock the gate again after unlocking it.
- What changed in filament-developer-gate v5.0.0 and will it affect redirects?
- Version 5.0.0 adds explicit Filament v5 support and fixes the gate page redirect that used the wrong config key. It also adds a fallback to the configured redirect when there is no previous page after unlocking. Validate your redirect configuration before and after upgrading, because environments relying on the broken redirect may navigate differently.
- Is filament-developer-gate secure enough for production use?
- It is appropriate for internal developer-only routes, rapid prototyping, and staging gates where a shared static password is acceptable. It is not a replacement for full authentication and does not include MFA, IP whitelisting, or failed-attempt logging out of the box. For production-sensitive areas, combine it with additional Laravel middleware, network controls, or a proper auth system.
- Does filament-developer-gate support MFA, IP whitelisting, or failed attempt logging?
- No. The package does not provide MFA, IP whitelisting, or attempt logging out of the box. If you have compliance or audit requirements, add logging middleware or use a dedicated authentication and audit package. The static password approach is intentionally simple and should be scoped to developer-only access.
- Should I use the v5 or v4 branch of filament-developer-gate?
- The v5 line targets Filament v5, while the v4 branch continues support for Filament v4. Choose based on your project's Filament major and pin the composer constraint accordingly. Because two lines are maintained, verify that security-relevant fixes such as password comparison and redirect handling are back-ported to your branch.
Weaver
How can I help you explore Laravel packages today?