Toolset · PHP, Eloquent, Horizon, Octane
Laravel
- PHP
- Laravel
- Redis
Laravel is our default PHP backend. The framework already supplies a strong container, ORM, and queue system — the toolset here is mostly about using them correctly under concurrency and scale.
Where two tools compete, the one marked our default is what we reach for.
Dependencies
1 toolPHP's dependency manager. Our default — commit the lock file, audit packages.
Dependency injection
1 toolLaravel's built-in IoC container with autowiring. Bind scoped, not singleton, for request state under Octane (see the Octane runbook). Our default — no library needed.
// Register in a service provider:
$this->app->bind(PaymentGateway::class, StripeGateway::class);
$this->app->scoped(TenantContext::class); // per-request under Octane
// Resolve (autowired via constructor injection, or):
$gateway = app(PaymentGateway::class);ORM & database
1 toolActive-record ORM. Use global scopes for tenant isolation and lockForUpdate for concurrent writes (see the isolation spec and deadlock runbook). Our default.
HTTP client
2 toolsGuzzle-backed fluent client with retries and pooling. Our default.
The underlying HTTP client for advanced control.
Queues & async
1 toolRedis queue dashboard and supervisor. Deploy workers with bounded lifetimes and graceful restart (see the workers runbook). Redis is our default queue driver — significantly faster and more scalable than the database driver, which matters for high-throughput, low-latency job processing. The database driver is acceptable only for prototypes or extremely low-traffic apps. Our default.
Auth & performance
3 toolsLightweight token/SPA auth. Our default for API and first-party clients.
Full OAuth2 server when you need third-party grants.
Persistent-worker runtime (Swoole/FrankenPHP) that keeps the application in memory for dramatically higher throughput. The catch is rigorous state management: never hold request-specific state in singletons (use scoped bindings) and clean up any static state that could leak across requests. Reach for it on high-traffic APIs; for low-to-moderate-traffic web apps the standard PHP-FPM model is simpler and often sufficient.
Testing
2 toolsExpressive testing on top of PHPUnit. Our default.
The foundational PHP test framework — a solid choice for teams with established PHPUnit suites or a preference for traditional syntax, though more verbose than Pest. Decision rule: start with Pest for its modern, expressive syntax that encourages test-driven development; stick with PHPUnit only for legacy codebases where migration overhead isn't justified.
Monitoring & observability
4 toolsException and performance monitoring with a first-class Laravel integration. Our default.
First-party production dashboard — slow queries, slow jobs, usage, and exceptions at a glance. Our default for prod insight.
Local/staging debug assistant — requests, queries, jobs, cache, and mail. Not for production.
Hosted error tracking from the Laravel team, powered by Ignition.
CI/CD
4 toolsRun Pest and static analysis, then trigger the deploy. Our default CI.
Server provisioning and push-to-deploy on your own VPS. Our default for deployment.
Zero-downtime, atomic deployments with health checks and rollback.
Managed and serverless hosting when you'd rather not run servers.
Linting & formatting
3 toolsZero-config PHP code-style fixer (PHP-CS-Fixer under the hood). Our default.
Static analysis tuned for Laravel — catches type and logic errors before runtime. Our default.
Automated refactoring and framework/PHP-version upgrades.
Building on Laravel?
We ship production Laravelwith exactly this stack. Tell us what you're building.
Start a conversation