Weave Code
Framework Laravel Package
spiral/framework
Spiral Framework is a high-performance, long-living full-stack PHP framework built around RoadRunner. PSR-compatible and battle-tested, it keeps your app in memory and supports HTTP, gRPC, queues, WebSockets, and background workers.
Spiral Framework is a high-performance, long-living full-stack PHP framework built from 60+ PSR-compatible components. It runs on a hybrid runtime with RoadRunner, keeping your app kernel in memory for fast requests while providing tools to prevent memory leaks and support persistent services.
Designed for production workloads since 2013, Spiral pairs modern PSR standards with an application-server model for HTTP, queues, gRPC, and more.
- RoadRunner-powered resident memory runtime
- Broad PSR compliance (3/4/7/11/12/14/15/16/17)
- Built-in queues & background workers (AMQP, SQS, Kafka, etc.)
- gRPC server/client via RoadRunner bridge
- Queue supervision and long-running service support
Frequently asked questions about Framework
- Can Spiral Framework replace Laravel in a production environment, or is it better suited for microservices?
- Spiral is designed for high-performance workloads and microservices, not direct Laravel replacement. Its RoadRunner-based runtime excels in persistent services, gRPC, and background workers, but lacks Laravel’s ecosystem (e.g., Eloquent ORM, Blade). For Laravel apps needing queues/gRPC, consider incremental adoption via Spiral components instead of full migration.
- How does Spiral’s dependency injection (DI) container compare to Laravel’s?
- Spiral’s DI container is PSR-11 compliant but differs structurally from Laravel’s. It’s optimized for persistent services and RoadRunner integration, while Laravel’s is tightly coupled with its ecosystem. Migrating existing Laravel services may require refactoring, though PSR-11 ensures compatibility with many middleware and service providers.
- Is Spiral Framework compatible with Laravel’s service providers and middleware?
- Partial compatibility exists due to PSR-15 (HTTP middleware) and PSR-11 (DI) standards, but Laravel’s service providers rely on framework-specific features. You can integrate Spiral’s HTTP layer with Laravel middleware via adapters, but full interoperability isn’t guaranteed. Test critical components before adoption.
- What Laravel versions can Spiral Framework integrate with, and how?
- Spiral isn’t a Laravel plugin but can coexist via API boundaries (e.g., HTTP endpoints, queues). For shared infrastructure, use Spiral’s PSR-compliant components (like queues) alongside Laravel. Direct integration isn’t supported, but you can route traffic between them via RoadRunner or reverse proxies like Nginx.
- How do I install Spiral Framework alongside an existing Laravel project?
- Spiral isn’t designed for side-by-side use with Laravel. Instead, adopt Spiral components incrementally (e.g., RoadRunner for queues) or migrate services to Spiral’s kernel. Use API contracts (OpenAPI/gRPC) to decouple systems. Avoid mixing frameworks in the same process to prevent conflicts in DI containers or event systems.
- What are the production risks of using Spiral Framework with RoadRunner?
- RoadRunner’s resident memory model reduces latency but requires careful monitoring for memory leaks. Spiral includes anti-leak tools, but production workloads must validate stability under load. Ensure your infrastructure supports RoadRunner’s process model (e.g., Docker/Kubernetes) and test failure recovery scenarios.
- Does Spiral Framework support Laravel’s Eloquent ORM, or should I use its own database layer?
- Spiral has its own database layer (Spiral Database) with active record and query builder patterns, but it’s not Eloquent-compatible. Migrating Eloquent models requires rewriting queries or using a compatibility layer. For new projects, Spiral’s layer is optimized for performance and RoadRunner integration.
- How does Spiral handle background jobs and queues compared to Laravel’s queue system?
- Spiral’s queue system (via RoadRunner) supports AMQP, SQS, Kafka, and more with built-in supervision and persistent workers. Unlike Laravel’s queue workers (which restart per job), Spiral keeps workers in memory, reducing overhead. For Laravel apps, this means faster processing but requires adapting to Spiral’s worker lifecycle model.
- Is Spiral Framework actively maintained, and what’s the status of the ‘2026 release’ mentioned in some reviews?
- Spiral is actively maintained with regular updates (check GitHub releases and Discord). The ‘2026 release’ likely refers to long-term roadmap planning, not a pause in development. Contributor activity is steady, with responsive issue resolution. For critical projects, review recent commits and the [Discord community](https://discord.gg/TFeEmCs) for real-time updates.
- Can I use Spiral Framework for a Laravel-like full-stack app with Blade templates and authentication?
- Spiral doesn’t include Blade or Laravel’s auth system, but you can integrate third-party templating engines (e.g., Twig) and libraries like Spiral Security for authentication. For a Laravel-like experience, focus on Spiral’s HTTP layer and build UI components separately. The framework prioritizes backend performance over full-stack convenience.
Weaver
How can I help you explore Laravel packages today?