Weave Code
Framework Laravel Package
hypervel/framework
Hypervel is a Laravel-compatible PHP framework built on Hyperf and Swoole coroutines. It brings familiar Laravel APIs—routing, ORM, queues, events, and validation—to a high-performance, coroutine-driven runtime, so Laravel developers can build fast concurrent apps with almost no learning curve.
[READ ONLY] Subtree split of the framework metapackage (see hypervel/components)
Frequently asked questions about Framework
- What is hypervel/framework and is it a drop-in replacement for laravel/framework?
- Hypervel is a Laravel-compatible PHP framework built on Hyperf components and Swoole coroutines, bringing routing, ORM, queues, events, and validation to a long-lived worker runtime. It is not a package you add to a Laravel app: it occupies the same slot as laravel/framework, and hypervel/framework is a read-only subtree split of the framework metapackage. Treat adoption as a platform decision rather than a composer require.
- Can I install Hypervel into an existing Laravel application with Composer?
- There is no supported path to layer Hypervel into a running Laravel application. The realistic options are a greenfield service or a strangler extraction of one bounded context. Anything depending on per-request bootstrap, PHP-FPM, or shared hosting has to be reworked first.
- What PHP version and coroutine extension does Hypervel require (Swoole vs OpenSwoole vs Swow)?
- Expect PHP 8.2 or newer plus a coroutine runtime extension, typically Swoole or OpenSwoole, with Swow discussed as an alternative. Confirm the exact matrix for your Hyperf version before committing, because the extension choice affects deployment images and health checks. Target containers, Kubernetes, or ECS with graceful shutdown rather than PHP-FPM.
- Which Laravel versions and APIs does Hypervel actually support?
- Familiar routing, Eloquent-style ORM, queues, events, and validation APIs are reimplemented on top of Hyperf components. Compatibility is familiar, not identical, so verify the specific APIs your codebase touches against the component docs. There is no documented step-by-step upgrade path from a Laravel 10, 11, or 12 codebase.
- How does Hypervel's request lifecycle differ from Laravel on PHP-FPM?
- Laravel under PHP-FPM is shared-nothing: boot, handle the request, tear everything down. Hypervel runs long-lived workers and handles each request inside its own coroutine, so state can survive across requests unless it is properly scoped. That single architectural shift is the crux of the entire evaluation.
- Will my existing Composer packages work with Hypervel?
- Classify every dependency as pure PHP (usually fine), Laravel-coupled (needs a Hypervel equivalent), or coroutine-unsafe (static caches, blocking SDKs, per-request singletons, $_SERVER and global state). Expect a material fraction to fall into the last two buckets. Budget time for vendoring or patching a handful of packages.
- Does Hypervel support first-party Laravel packages like Horizon, Sanctum, or Passport?
- Do not assume coverage. Hypervel ships its own component set, so each Laravel first-party package you rely on must be checked for a verified equivalent. Build an explicit compatibility matrix before committing to the platform.
- Is Laravel Octane or RoadRunner a safer alternative to Hypervel?
- For most teams, yes. Benchmark Laravel on Octane or RoadRunner against Hypervel on your own workload before deciding, because Octane captures much of the throughput upside with a fraction of the adoption risk. If Octane closes roughly 70 percent of the gap, the remaining delta rarely justifies a framework swap; choose Hypervel only when you need true concurrent IO inside a request.
- What production risks come with Hypervel's coroutine runtime, and how should I test for them?
- The main hazards are data races, container scoping bugs, connection-pool exhaustion, and cross-request memory retention. They are subtle, intermittent, and expensive to reproduce, and they surface in soak tests rather than unit tests. Plan load and soak testing plus per-request context tracing before going live.
- Who maintains Hypervel, and how are releases, LTS, and security fixes handled?
- The repository's low star count is partly an artifact of read-only subtree splits, so weigh Packagist install and download trends, contributor count, commit cadence, and issue-resolution latency instead. Ask for a release and LTS policy, a documented breaking-change cadence, and a named maintainer accountable for CVE response. Also establish who funds the project before you depend on it.
Weaver
How can I help you explore Laravel packages today?