Serverless PHP Market Analysis

2. 1. PHP Market Context

Market Share & Usage

PHP remains the dominant server-side language on the web by a wide margin, despite years of “PHP is dead” narrative:

• 74.5% of all websites with a known server-side programming language use PHP (W3Techs, early 2025). Some sources report 73–77% depending on methodology.
• WordPress alone powers 42.8% of all websites (February 2026) — 64.3% of the CMS market. Every WordPress site runs on PHP.
• PHP powers 90%+ of CMS-based websites, including Joomla (1.5%), Drupal (0.9%), and hundreds of smaller platforms.
• 455+ million websites worldwide run on WordPress alone (based on 1.2B total websites).
• 33+ million live websites run PHP directly.

The “PHP Is Dead” Narrative vs. Reality

The disconnect is real: PHP dominates web infrastructure but has declining mindshare among new developers.

• Only 18.2% of developers reported using PHP in the Stack Overflow Developer Survey 2024 (18.7% among professional developers).
• Only 15.2% of new programmers choose PHP as their starting language.
• PHP’s W3Techs market share has declined from ~82% (2017) to ~74% (2025) — a slow erosion, not a collapse.
• The gap reflects that PHP runs infrastructure (WordPress, legacy apps, CMS sites), while developers building new projects increasingly choose Node.js, Python, or Go.
• Companies like Facebook (Meta), Slack, Etsy, Tumblr, and Wikipedia still run PHP at massive scale.

PHP Version Adoption

• PHP 7.x: 45.3% of PHP websites (still huge legacy)
• PHP 8.x: 43.1% and catching up fast
• PHP 8.5 slated for November 2025 release

PHP 8.x Performance Improvements

• JIT compiler (introduced PHP 8.0): 5–15% improvement in arithmetic-heavy workloads. PHP 8.4 refines JIT to trace longer code paths. Real-world web apps see modest 2–5% gains from JIT alone.
• Fibers (PHP 8.1): Cooperative multitasking enabling async I/O — 2–10x improvement for I/O-bound operations, more significant than JIT for typical web applications.
• PHP 8.5 opcache.file_cache_read_only: Major improvement for containerized/serverless environments, enabling OPcache file cache on read-only filesystems (100ms cold start reduction on AWS Lambda).
• Across 13 CMSs and frameworks benchmarked, performance between PHP 8.2–8.5 doesn’t shift dramatically for most workloads.

Laravel’s Dominance in PHP Frameworks

• 60–64% market share among PHP frameworks (JetBrains State of PHP 2025 survey: 64%)
• 75,800+ GitHub stars (vs. Symfony’s 25,400+)
• 1.5+ million websites powered by Laravel globally
• 149,905 companies using Laravel worldwide
• Top geographies: USA (31.4%), India (14.4%), Brazil (12.5%)
• 40% of startups in tech/digital fields use Laravel

Symfony’s Position

• 14% market share among PHP frameworks
• 25,400+ GitHub stars
• 10,633 websites currently using Symfony (vs. 80,144 for Laravel)
• Known for flexibility, extensibility, adherence to best practices, used in complex enterprise applications
• Many Laravel components are built on Symfony components

PHP Developer Salary Data

3. 2. The Serverless Computing Market

The serverless computing market is growing rapidly, though estimates vary significantly across research firms:

Conservative estimate: The serverless computing market is roughly $25–32B in 2025, growing at 15–25% CAGR. Even the most conservative estimate puts it at $90B+ by the early 2030s.

PHP’s slice: If PHP powers 74% of server-side web, even capturing 5–10% of the serverless market would represent a $1.3–3.2B opportunity. Today, the PHP serverless ecosystem is a tiny fraction of this.

4. 3. Bref Deep Dive

Overview

Bref is an open-source framework to write and deploy serverless PHP applications on AWS Lambda. Created in 2018 by Matthieu Napoli, an AWS Serverless Hero, Bref provides PHP runtimes for Lambda distributed as Lambda layers and Docker images.

Key Statistics

• 44.3 billion invocations handled in the last 30 days (as of February 2026) — that is roughly 1 in every 1,000 AWS Lambda invocations worldwide
• 300% year-over-year growth in invocations
• 9.2 million Packagist installs (bref/bref package)
• 3,347 GitHub stars, 373 forks, 47 watchers, 68 open issues
• bref/extra-php-extensions: 4.0M installs, 224 stars
• bref/laravel-bridge: 3.7M installs, 337 stars
• 8 years old (since 2018), open-source, battle-tested — banks run on Bref

Architecture

Bref provides two main runtime approaches:

FPM Layer (php-8x-fpm)

Uses PHP-FPM to run web applications on AWS Lambda. Best for existing web apps, WordPress, Laravel, Symfony. The most common approach for lift-and-shift migrations.

Function Layer (php-8x)

Runs PHP as a Lambda function handler. Best for event-driven workloads, queue processing, cron jobs, and API endpoints. More “serverless native.”

Supports PHP 8.2–8.4 via Lambda layers, with PHP 8.5 support coming. Supports both x86 and arm64 platforms on Amazon Linux 2023.

Cold Start Performance

• Base cold start: ~250ms on average (Bref runtime alone)
• Application size adds to this — a typical Laravel app adds 200–500ms
• PHP 8.5’s opcache.file_cache_read_only drops cold starts by ~100ms on Lambda
• OPcache preloading does not help on Lambda — it just shifts cold start time into boot time with no net gain
• Container image deployments leverage Lambda’s filesystem streaming optimization, loading only files actually read

Pricing & Business Model

Bref (open source): Free. MIT licensed. Bref itself costs nothing — you pay only for AWS Lambda, API Gateway, and other AWS services consumed.

Bref Cloud: A managed dashboard/deployment tool that deploys to your AWS account with zero markup on AWS prices. Bref Cloud handles deployment, monitoring, and permissions management. With serverless pay-as-you-go pricing, your hosting bill from AWS could be as low as $0 if your app has no traffic.

Consulting & Training: Matthieu Napoli created a company called Null to provide consulting services and training around Bref and serverless PHP.

Matthieu Napoli Background

• Open-source developer, consultant, and AWS Serverless Hero
• Previously Senior Product Manager at Serverless Framework (Serverless, Inc.)
• Founded a company called Null for open-source work, consulting, and training around Bref
• Active in the PHP community, prolific open-source contributor

Companies Using Bref in Production

Treezor (banking-as-a-service)

Serves millions of transactions daily for neobanks, employee benefit cards, travel cards. Migrated legacy PHP to Lambda via Bref. Results: 2.5x faster response times, 3x fewer production alerts, 10x fewer transaction timeouts.

MyBuilder (marketplace)

Online marketplace matching tradespeople with homeowners. Uses Lambda + Bref for scalable PDF generation microservice.

Voxie

Sponsors Bref; uses it as the foundation for building scalable products on AWS Lambda.

5. 4. Laravel Vapor Deep Dive

Overview

Laravel Vapor is an auto-scaling serverless deployment platform for Laravel, powered by AWS Lambda. Launched in 2019 by Taylor Otwell / Laravel LLC. It provisions and manages the full AWS infrastructure (VPCs, security groups, IAM roles, Lambda, API Gateway, S3, RDS, ElastiCache, DynamoDB) through an intuitive dashboard.

Pricing

• Sandbox plan: Free — allows provisioning networks, databases, caches, and one project. No custom domains, API Gateway, load balancers, or firewalls.
• Paid subscription: $39/month (save 14% with annual billing) for full features. Includes unlimited projects and deployments.
• AWS costs are separate and passed through at cost with zero markup.

Key Features

• Auto-scaling: Powered by AWS Lambda — scales automatically with traffic
• Atomic deployments: Deploys to a new Lambda version and atomically switches traffic only after successful deployment. Failed deployments never affect production.
• Database management: Create, manage, scale, and restore traditional and serverless databases from the dashboard
• Cache management: DynamoDB and ElastiCache Redis clusters
• Automatic handling: Asset compilation, environment variables, database migrations, queue configuration
• Infrastructure management: VPCs, security groups, IAM roles, service connections — all managed automatically

Vapor vs. Bref Comparison

6. 5. Laravel Cloud

Timeline

• July 2024: Announced by Taylor Otwell at Laracon US 2024
• September 2024: Laravel raised a $57M Series A from Accel — the company’s first VC funding in its 13-year history. Accel pursued Otwell for over a year before he took the call.
• February 24, 2025: Official launch alongside Laravel 12

How It Differs from Vapor

Laravel Cloud is not serverless. It’s a fully managed container-based platform:

• No cold starts — unlike Vapor/Lambda, Cloud uses persistent containers
• No AWS account required — Cloud manages everything, while Vapor deploys to your AWS
• Container-based deploys with Laravel YAML configurations and built-in CI/CD
• No IAM/Lambda constraints — no need to understand Lambda limits, VPC configurations, or supporting AWS services
• Serverless Postgres powered by Neon with hibernation, autoscaling, and point-in-time recovery
• Auto-scaling with control: Set max replicas, Cloud scales within limits based on CPU. You only pay when replicas are running.

Pricing

Competitive Positioning

Laravel Cloud is the evolution of Forge, not Vapor. Where Forge lets you bring your own infrastructure, Cloud runs everything for you. Where Vapor is serverless on Lambda, Cloud is containers with auto-scaling. The positioning is: simpler operational model, predictable performance, clearer pricing.

Early traction: PyleSoft reported cutting infrastructure costs 50% migrating from Vapor to Cloud.

7. 6. The Laravel Ecosystem & “Laravel Tax”

Taylor Otwell’s Business Model

Taylor Otwell built one of the most successful open-source business models in PHP history. Key facts:

• $57M Series A from Accel (September 2024) — first VC funding in 13 years
• 90 employees (up from 8 at the start of 2024, 35 by July 2024)
• Based in Little Rock, Arkansas
• Every product besides Vapor has made over $1 million in its lifetime
• Forge: “A couple million dollars a year”
• Envoyer: ~$500K/year
• Nova and Spark: Each made over $1M lifetime

Product Portfolio & Pricing

The “Laravel Tax”

The Laravel ecosystem charges for almost every layer of the development lifecycle. A typical Laravel project’s monthly “tax”:

• Forge or Cloud: $12–$20+/month for hosting management
• Vapor: $39/month if going serverless
• Envoyer: $10–$50/month for zero-downtime deploys
• Nova: $99–$299 one-time for admin panel
• Spark: $99–$299 one-time for SaaS billing
• Herd Pro: $99/year for enhanced local development
• Total: A fully loaded Laravel project could easily pay $100–$200+/month to Laravel LLC before any infrastructure costs

NativePHP

NativePHP, developed by Simon Hamp and Marcel Pociot, transforms Laravel applications into native desktop (Windows, macOS, Linux) and mobile apps. In 2025, it expanded to iOS, with a published App Store application powered by Laravel, Livewire, Tailwind, and PHP — running the PHP engine compiled in C, embedded directly in the app (not a WebView or PWA).

8. 7. FrankenPHP Deep Dive

Overview

FrankenPHP is a modern PHP application server built on top of the Caddy web server. Written in Go, it embeds the PHP interpreter as a Caddy module, delivering a fundamentally different approach to running PHP applications.

Key Statistics

• 10,000+ GitHub stars (reached 10K in August 2025)
• 100+ contributors
• Officially supported by the PHP Foundation (May 2025)
• Current maintainers: Kévin Dunglas, Robert Landers, Alexander Stecher

Kévin Dunglas & Les-Tilleuls.coop

• Kévin Dunglas is the creator of FrankenPHP, API Platform, Mercure.rocks, and Vulcain.rocks
• Part of the Symfony Core Team
• Founder of Les-Tilleuls.coop, a French worker-owned cooperative
• Specialized in critical web applications with high traffic, high availability, and interoperability

Key Features

Worker Mode

Keeps PHP application in memory between requests (like Swoole/RoadRunner). Results: 80% reduction in response times (Sylius benchmark), 6x fewer machines needed for the same traffic, >10x faster than Nginx+PHP-FPM under 1,000 concurrent requests. Laravel, Symfony, and Yii have official worker mode integrations.

103 Early Hints

Send resource hints to the browser before the response is ready — the browser starts loading CSS, JS, and fonts while PHP generates the page. FrankenPHP is one of the first PHP servers to support this HTTP feature.

HTTP/2 and HTTP/3

Built-in support via Caddy, including QUIC protocol for HTTP/3.

Automatic HTTPS

Caddy’s automatic certificate generation and renewal works out of the box.

Zstandard Compression

Modern compression algorithm support alongside Brotli and gzip.

Hot Reload (v1.11, December 2025)

File monitoring with automatic worker restart in the background.

Thread Autoscaling (v1.6, May 2025)

Automatically spawns additional threads at runtime up to a specified limit.

Standalone Binaries

PHP and Symfony apps can be compiled as standalone static binaries.

Performance Benchmarks

• FrankenPHP 1.3 handles 54% more requests than v1.0 with the same hardware (major thread engine overhaul by Alexander Stecher)
• Worker mode vs. PHP-FPM: 2–4x throughput for framework-heavy apps, 10x+ under high concurrency
• Classic mode vs. PHP-FPM: Comparable or slightly better, worthwhile for FrankenPHP-exclusive features (Early Hints, Go extensions, Mercure)

How FrankenPHP Changes PHP Deployment

FrankenPHP represents a paradigm shift from the traditional Nginx/Apache + PHP-FPM stack to a single-binary application server approach. It enables PHP applications to be:

• Deployed as single Docker containers without web server configuration
• Compiled as standalone binaries for zero-dependency deployment
• Distributed as deb/RPM packages (since v1.6)
• Run with persistent worker processes for dramatically better performance

9. 8. Cloud Provider PHP Support

AWS Lambda

• No native PHP support — PHP is not an officially supported Lambda runtime
• Custom runtimes via Lambda Layers: Bref is the de facto standard, providing PHP 8.2–8.4 runtimes as Lambda layers and Docker images
• Container image support: Build custom PHP Docker images for Lambda
• Lambda supports both x86_64 and arm64 (Graviton2) architectures for PHP runtimes
• The custom runtime approach has been stable and well-supported since 2018

Google Cloud Functions / Cloud Run

• Official PHP support via Cloud Run functions (formerly Cloud Functions)
• PHP 8.3: General Availability (2nd gen functions)
• PHP 8.4 and 8.5: Preview
• Uses the Functions Framework for PHP (open-source, Google-maintained)
• Supports HTTP functions and CloudEvent functions
• Cloud Run: Full container support for PHP applications (FrankenPHP, PHP-FPM, etc.)

Azure Functions

• No official PHP support — PHP is not among supported languages
• Custom handlers: Can implement PHP via Azure Functions custom handlers, which are lightweight web servers receiving events from the Functions host
• Latest supported: PHP 8.2 on App Service Linux instances only (Windows only supports up to PHP 7.4)
• Major limitation: PHP’s built-in web server runs only a single-threaded process, causing stalls under concurrent load
• Cannot use the consumption plan (language runtime not available); may need custom containers
• Overall: Azure’s PHP serverless story is weak and poorly maintained

Cloudflare Workers

• No PHP support — only JavaScript and WebAssembly runtimes
• Cloudflare does not plan to add language runtimes beyond JS/WASM because other languages require process-level isolation (containers/VMs), incompatible with their edge distribution model
• Workaround: babel-preset-php transpiles PHP to JavaScript, enabling limited PHP on Workers (proof of concept, not production-ready)
• Theoretical WASM path: PHP compiled to WebAssembly could run on Workers, but the PHP runtime port to WASM is non-trivial

Vercel

• No official PHP support — not a first-party runtime
• Community runtime: vercel-php provides PHP support via custom runtime in vercel.json. Actively maintained with PHP 8.4 (v0.8.0) and PHP 8.5 (v0.9.0) support.
• Handles dependency installation, composer install, and numerous extensions (APCu, bcmath, curl, MongoDB, Redis, etc.)
• Can deploy Laravel and other PHP frameworks
• Limitation: Best for lightweight backend functions, APIs, form handlers — not full-featured PHP application hosting

10. 9. PHP-WASM & Future Directions

WordPress Playground

WordPress Playground runs a complete WordPress installation in the browser via WebAssembly PHP — no server needed. This is the most ambitious and successful PHP-WASM project.

• PHP 8.3 became the default version for Playground (July 2025)
• OpCache enabled by default: Reduced average response times from 185ms to 108ms in WordPress 6.8 benchmarks
• 99% of top 1,000 WordPress plugins install and activate successfully in Playground
• Features: File browser, code editor, phpMyAdmin/Adminer integration, standalone PHP Playground, visual Blueprint editor, Gutenberg branch previews
• XDebug support: Experimental debugging of WordPress Playground on Chrome
• CLI stable release: Auto mode, XDebug support, multi-worker mode for concurrent tasks, runCLI API for embedding in Node.js applications

seanmorris/php-wasm

The original PHP-to-WebAssembly project that WordPress Playground forked and extended.

• Powers WordPress Playground, Drupal Playground, and PlayWithLaravel
• Supports 17 commonly used PHP extensions including LibXML, OpenSSL, Intl, ICU, GD, mbString, oniguruma, zLib
• Can run as a service worker, mimicking a CGI webserver like Apache or nginx
• Full access to JavaScript APIs and the DOM from PHP
• Supports PHP 7.4 through 8.5
• Package split (January 2026): WASM binaries exceeded npm’s 100MB size limit, so packages were separated into dedicated versions (e.g., @php-wasm/node-8.4, @php-wasm/web-8.5)

Implications for Serverless

• Edge computing: PHP-WASM could theoretically run on edge platforms like Cloudflare Workers, though the WASM binary size and startup time are currently prohibitive
• Development tooling: In-browser PHP environments for testing, demos, and education
• Plugin marketplaces: Test WordPress themes/plugins without server infrastructure
• Client-side PHP: Offline-capable PHP applications running entirely in the browser
• Current limitation: Performance is significantly slower than native PHP; primarily useful for development, testing, and demonstration rather than production workloads

11. 10. Managed PHP Hosting Landscape

These platforms are not serverless but represent the competitive landscape for PHP deployment:

Server Management Tools

Traditional Hosting Market Shift

• Shared hosting is declining: 40%+ of businesses transitioning to modern hosts. VPS market growing at 16.2% CAGR through 2026.
• Shared hosting prices: $1.58–$4.99/month (still viable for small sites)
• VPS hosting: $20–$100/month (becoming the standard for serious websites)
• The shift is from “cheap and easy” to “more control and performance”

12. 11. WordPress-Specific Hosting

Market size indicator: WP Engine alone does $400M/year in WordPress hosting revenue. The managed WordPress hosting market is likely $1–2B+ annually when including all players.

13. 12. Container & PaaS Platforms

Platform.sh / Upsun

• Founded: 2010, Paris, France
• Total funding: $187M across 5 rounds (Series D: $140M in June 2022, led by Morgan Stanley, Revaia, Digital Partners)
• 13 institutional investors including Morgan Stanley, Idinvest Partners
• Rebranded to Upsun (September 2024) — AI-augmented workflows, granular resource management, enterprise-scale modernization
• PHP leadership: Chosen cloud solution behind Symfony, Magento, eZ Systems, Drupal Commerce
• Platform.sh pricing: Predictable pricing for monolithic CMS/ecommerce
• Upsun pricing: Usage-based, pay-per-second granular model with vertical autoscaling
• 50% discount for startups on first-year Upsun contracts

Fly.io

• Container-based deployment with multi-region anycast networking
• Official Laravel support: Dedicated documentation, Docker images (fideloper/fly-laravel), Dockerfile generator for Laravel
• Supports both Nginx/PHP-FPM and FrankenPHP/Octane-based deployments
• Extensions: Postgres, Redis, Tigris storage auto-detected from Laravel project
• CLI-first workflow via flyctl

Railway

• Deploys from Docker images or source code via GitHub
• Uses nixpacks to build Docker images by analyzing source code
• Supports PHP/Laravel deployments including WebSocket workers
• Preview environments for pull requests
• Web-based interface with automatic deployments

Render

• Simple apps, workers, cron jobs, managed Postgres with CDN
• Supports PHP via Docker containers
• Predictable pricing, auto-deploys from Git

14. 13. Deployment Tools & Frameworks

Serverless Framework

• The most widely used serverless deployment framework, platform-agnostic across AWS, GCP, Azure
• Supports PHP through Bref integration
• Serverless Framework v4 (December 2025): AI-assisted workflows, Serverless MCP for IDEs, resource/log mapping for AI tooling
• Pricing change concern: v4 introduced commercial licensing that caused friction in the Bref community (GitHub issue #1749)

AWS SAM (Serverless Application Model)

• Official AWS serverless deployment framework
• SAM CLI for local development, testing, and debugging
• Bref provides first-class SAM support
• Free and open-source

AWS CDK (Cloud Development Kit)

• Infrastructure-as-code using programming languages (TypeScript, Python, etc.)
• Bref provides CDK constructs for PHP Lambda deployments
• Most flexible option for teams already using CDK

Terraform

• Bref supports Terraform for infrastructure provisioning
• Multi-cloud capable, though PHP serverless primarily targets AWS

15. 14. Technical Challenges of Serverless PHP

Cold Starts

PHP bootstrap time

Bref base cold start: ~250ms. Laravel adds 200–500ms. Total: 450–750ms for a typical Laravel app. By comparison, Node.js cold starts are 100–300ms.

OPcache

PHP 8.5’s opcache.file_cache_read_only is a game-changer for Lambda, enabling file-based opcode caching on read-only filesystems. ~100ms improvement.

Preloading

OPcache preloading does NOT help on Lambda — it shifts cold start time to boot time with no net gain. This is a common misconception.

Provisioned concurrency

AWS Lambda’s provisioned concurrency can eliminate cold starts but adds cost (~$0.015/GB-hour).

Database Connections

Connection exhaustion

Each Lambda invocation can create a new database connection. 1,000 concurrent users means 1,000 database connections — most databases cannot handle this.

Connection pooling

RDS Proxy ($0.015/vCPU-hour) pools connections between Lambda and RDS. Essential for serverless PHP at scale.

Connection leaking

Pool client idle timeouts don’t fire while Lambda is suspended between invocations, causing “leaked” connections. Aurora cold starts add 100–300ms for new connections.

Serverless databases

Neon (serverless Postgres, used by Laravel Cloud), PlanetScale (serverless MySQL), and DynamoDB avoid connection pooling issues entirely with HTTP-based protocols.

Stateless Constraints

Sessions

No local session storage. Must use DynamoDB, Redis (ElastiCache), or database-backed sessions.

File uploads

Lambda has a 6MB payload limit for synchronous invocations. Large uploads must go directly to S3 via pre-signed URLs.

WebSockets

Lambda doesn’t maintain persistent connections. Use API Gateway WebSocket API with Lambda handlers for pseudo-WebSocket support.

File system

Read-only filesystem except /tmp (512MB by default, configurable up to 10GB). All persistent storage must use S3 or EFS.

Execution Limits

• Timeout: 15 minutes maximum (API Gateway further limits to 29 seconds for HTTP)
• Memory: 128MB to 10,240MB
• Package size: 50MB zipped, 250MB unzipped (container images: 10GB)
• Concurrency: 1,000 default per region (can be increased)

PHP Extensions

• Bref includes common extensions by default (JSON, XML, cURL, mbstring, etc.)
• bref/extra-php-extensions (4M+ installs) adds: ImageMagick, GD, Intl, SOAP, PostgreSQL, Redis, MongoDB, AMQP, and more
• Custom extensions require building a custom Lambda layer

Vendor Lock-in

• Bref: Locked to AWS Lambda, but application code is standard PHP — relatively easy to migrate to containers
• Vapor: Locked to both AWS and Laravel’s proprietary deployment platform
• Google Cloud Functions: Uses Google’s Functions Framework, but the framework is open-source and portable
• FrankenPHP: No lock-in — standard PHP-FPM applications work in classic mode, worker mode requires minor code changes

16. 15. Master Comparison Table

17. 16. Market Opportunities & Bootstrapper Plays

Gap Analysis: What’s Missing

1. No framework-agnostic managed serverless PHP platform. Vapor is Laravel-only. Bref Cloud is nascent. There’s no “Vercel for PHP” that supports Symfony, WordPress, CakePHP, and custom PHP apps with a polished UI.
2. No edge computing for PHP. PHP cannot run on Cloudflare Workers, Vercel Edge Functions, or Deno Deploy. The WASM path exists but is immature. This is a fundamental gap.
3. No serverless WordPress hosting. WordPress is 42.8% of all websites but has zero true serverless hosting options. WP Engine ($400M revenue) runs traditional containers. Bref can technically run WordPress on Lambda, but it’s not turnkey.
4. Weak Azure and multi-cloud story. PHP serverless is almost exclusively an AWS story. Azure’s PHP support is poor. No good multi-cloud serverless PHP solution exists.
5. Connection pooling is still painful. RDS Proxy helps but adds cost. There’s no purpose-built connection pooler for serverless PHP (like Neon’s pooler for Postgres or PgBouncer).
6. No good monitoring/observability for serverless PHP. Lambda monitoring tools are generic. There’s no Datadog/New Relic specifically optimized for PHP on Lambda (cold start tracking, OPcache metrics, extension performance).

Bootstrapper Opportunities

Revenue Benchmarks

• Ramen profitable ($5–10K MRR): 6–12 months with 250–500 customers at $20–40/month
• Sustainable ($50–100K MRR): 18–36 months. This is where Ploi and smaller Forge alternatives likely sit.
• Growth ($1M+ ARR): 2–4 years. Forge’s trajectory shows this is achievable in PHP tooling.
• Acquisition target: At $2–5M ARR, you’re interesting to Laravel LLC (who acquired Herd), Platform.sh/Upsun, or hosting companies looking to add serverless.

18. 17. Conclusions

Key Takeaways

1. PHP is not dying, but its growth is in infrastructure, not adoption. 74% of server-side web runs PHP, but only 18% of developers actively choose it. The opportunity is in modernizing how existing PHP runs, not in convincing new developers to adopt PHP.
2. Laravel has won the PHP framework war and is building an empire. With 64% framework market share, $57M in VC funding, 90 employees, and a product portfolio generating $10M+/year, Laravel LLC is the dominant commercial force in PHP. Laravel Cloud’s launch signals a shift from tools (Forge, Vapor) to platform (Cloud).
3. Bref is the quiet giant of serverless PHP. 44 billion Lambda invocations per month (1 in every 1,000 AWS Lambda invocations worldwide) with 300% YoY growth. Open-source, framework-agnostic, and increasingly the de facto standard for PHP on Lambda — even Vapor uses similar underlying AWS infrastructure.
4. FrankenPHP is changing the PHP runtime landscape. PHP Foundation backing, 10K+ GitHub stars, worker mode delivering 10x performance improvements, and an approach that could make Nginx+PHP-FPM obsolete. The single-binary deployment model is particularly compelling for containerized environments.
5. The serverless PHP market is AWS-centric with major gaps elsewhere. Google Cloud has decent PHP support. Azure’s is poor. Cloudflare Workers doesn’t support PHP at all. Edge computing for PHP is effectively non-existent. Multi-cloud serverless PHP is not a solved problem.
6. WordPress is the elephant in the room. 42.8% of all websites, $400M+ in managed hosting revenue (WP Engine alone), yet zero true serverless offerings. PHP-WASM/WordPress Playground proves PHP can run in novel environments, but the gap between “runs in a browser” and “production-grade serverless WordPress” is enormous.
7. The bootstrapper opportunity is real but narrow. The “Laravel tax” creates pricing room for alternatives (Ploi and RunCloud proved this). The serverless layer adds new niches: framework-agnostic managed serverless, PHP-specific monitoring, connection pooling services, FrankenPHP managed hosting. Revenue ceilings may be lower than pure SaaS plays — PHP developer tooling is a $10M–$100M market, not a $1B one.
8. The future of PHP deployment is converging on containers + auto-scaling, not pure serverless. Laravel Cloud (containers), FrankenPHP (worker mode), and Google Cloud Run all point to a future where PHP apps run in optimized containers with auto-scaling — rather than the Lambda/cold-start model. Serverless (Lambda) may be a transitional architecture for PHP, with FrankenPHP worker mode in containers delivering better performance characteristics.

The Numbers That Matter