Powerful
Authentication
for Laravel 12

Tyro Login is a Laravel package that provides beautiful, customizable login and registration pages. It includes multiple layout options, dark/light themes, lockout protection, and seamless integration with the Tyro RBAC package.

Tyro Login requires PHP 8.2 or higher and Laravel 12. It works with any database supported by Laravel (MySQL, PostgreSQL, SQLite, SQL Server).

No, Tyro Login works independently. However, if you have the Tyro package installed, it will automatically integrate with it to assign default roles to new users upon registration.

Ensure you're using PHP 8.2+ and Laravel 12. Run composer update first. Check your minimum-stability in composer.json. If using older Laravel versions, upgrade your framework first.

Tyro Login works seamlessly with Laravel's default authentication system. No migration is required - your existing users and data remain completely unchanged. Simply install Tyro Login and it will integrate automatically. You can optionally disable Laravel's default auth routes in routes/web.php if you prefer to use only Tyro Login's routes.

Yes! Run php artisan tyro-login:publish --views to publish the Blade templates to your application. You can then modify them as needed. You can also customize colors and branding via environment variables without touching any code.

Set the TYRO_LOGIN_LAYOUT environment variable to centered, split-left, or split-right. You can also set a custom background image URL with TYRO_LOGIN_BACKGROUND_IMAGE.

Publish views with php artisan tyro-login:publish --views and modify CSS. You can also override CSS variables or use your own stylesheet.

Check your mail configuration in config/mail.php. Verify SMTP settings and ensure TYRO_LOGIN_DEBUG=true to see logged email URLs during development. Some email providers may require additional configuration.

Yes! Set TYRO_LOGIN_USER_MODEL to your custom User model class. Your model just needs to implement Laravel's Authenticatable contract.

Yes! Use TYRO_LOGIN_ROUTE_PREFIX to add a prefix (e.g., 'auth' makes URLs /auth/login). All routes will be prefixed automatically.

When enabled, users are locked out after a configurable number of failed login attempts (default 5). The lockout is stored in cache (no database required) and automatically expires after a configurable duration (default 15 minutes). A beautiful lockout page shows a countdown timer.

The math captcha displays a simple addition or subtraction problem (e.g., "5 + 3 = ?") on your login and/or registration forms. Enable it with TYRO_LOGIN_CAPTCHA_LOGIN=true or TYRO_LOGIN_CAPTCHA_REGISTER=true. No external APIs required - answers are stored in the session.

Set TYRO_LOGIN_OTP_ENABLED=true in your .env file. After entering valid credentials, users receive a one-time password via email. Configure OTP length (4-8 digits) with TYRO_LOGIN_OTP_LENGTH and expiration time with TYRO_LOGIN_OTP_EXPIRE. All OTP data is stored in cache - no database required.

Yes! It includes CSRF protection, secure password hashing, session regeneration, and uses signed URLs for sensitive operations. Always use HTTPS in production and never enable debug mode.

Debug mode (TYRO_LOGIN_DEBUG=true) logs OTP codes, verification URLs, and password reset URLs to storage/logs/laravel.log. This makes it easy to test email-based features during development without actually sending emails. Never enable this in production!

Both features use secure, time-limited signed URLs stored in cache (no database migrations required). Email verification can be enabled via TYRO_LOGIN_REQUIRE_VERIFICATION=true. Password reset shows a "Forgot Password?" link on the login page. In development, verification and reset URLs are logged to the console for easy testing.

Yes! Tyro Login works with any email service configured in Laravel's mail.php (SendGrid, Mailgun, SES, etc.). Just configure your service and emails will work.

Enable debug mode with TYRO_LOGIN_DEBUG=true. All email URLs, OTP codes, and reset tokens will be logged to storage/logs/laravel.log. For development, you can also use email debugging services like MailTrap or Mailpit to capture and inspect sent emails without affecting real users. These services provide real-time email previews, delivery tracking, and webhook testing capabilities.

Tyro Login supports 8 OAuth providers: Google, Facebook, GitHub, Twitter/X, LinkedIn, Bitbucket, GitLab, and Slack. Each provider can be individually enabled or disabled.

Run php artisan tyro-login:install --with-social to install with social login support. Then set TYRO_LOGIN_SOCIAL_ENABLED=true and enable desired providers like TYRO_LOGIN_SOCIAL_GOOGLE=true. Configure provider credentials in config/services.php.

Yes! When TYRO_LOGIN_SOCIAL_LINK_EXISTING=true (default), if a user signs in with a social account that has the same email as an existing user, the accounts are automatically linked and the user is logged in.

No! Tyro Login uses Laravel's cache system for all temporary data (lockouts, OTP codes, verification tokens, password reset tokens). This means zero database migrations and works with any cache driver (file, Redis, Memcached, etc.).

Minimal impact. It uses cache for temporary data (no database queries) and lazy-loads views. Email operations can be queued for better performance.

Tyro Login uses Laravel's cache system. Ensure your cache driver is properly configured in config/cache.php. File cache works out of the box, Redis/Memcached need proper setup.

Tyro Login uses Laravel's cache system. Ensure your cache driver is properly configured in config/cache.php. File cache works out of the box, Redis/Memcached need proper setup.

Yes! Use TYRO_LOGIN_ROUTE_PREFIX to add a prefix (e.g., 'auth' makes URLs /auth/login). All routes will be prefixed automatically.

Use Laravel's built-in auth middleware or guest middleware for public pages. Tyro Login integrates seamlessly with Laravel's authentication system.

Disable debug mode (TYRO_LOGIN_DEBUG=false), use HTTPS, configure proper email service, set appropriate lockout limits, and consider rate limiting.

Yes! It works with any Laravel setup. For multi-tenant, ensure your cache and session configurations are tenant-aware.