A GraphQL framework that integrates seamlessly with Laravel applications.
Lighthouse is a GraphQL framework specifically designed for Laravel applications. It enables developers to build GraphQL APIs by integrating GraphQL's powerful query capabilities with Laravel's robust ecosystem. The framework solves the challenge of implementing GraphQL in Laravel projects by providing seamless integration with Eloquent models, authentication systems, and other Laravel components.
Laravel developers who need to implement GraphQL APIs in their applications, particularly those building modern web applications, mobile backends, or microservices that require flexible data querying capabilities.
Developers choose Lighthouse because it provides the most native GraphQL experience for Laravel, with automatic resolver generation, excellent performance optimizations, and a directive system that extends Laravel's capabilities. It offers the perfect balance between convention and configuration, reducing boilerplate code while maintaining flexibility.
A framework for serving GraphQL from Laravel
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Seamlessly maps GraphQL types to Laravel Eloquent models with automatic resolver generation, reducing boilerplate code for database interactions.
Extends functionality through custom directives for authorization, validation, and field manipulation, leveraging Laravel's familiar middleware patterns.
Includes built-in features like query complexity analysis and N+1 query prevention to ensure efficient data loading and API responsiveness.
Full support for GraphQL Schema Definition Language with Laravel integration, enabling robust API design and reducing runtime errors.
Tightly coupled to Laravel, making it unsuitable for projects using other PHP frameworks or requiring framework-agnostic GraphQL solutions.
Only code elements marked with @api are guaranteed compatible; internal changes may break custom implementations without warning, as noted in the versioning policy.
Requires proficiency in GraphQL concepts, which can be a barrier for teams transitioning from REST or new to declarative data fetching.