Expose Laravel Package

Product Decisions This Supports

• Build vs. buy for inbound tunneling. Expose gives you a credible open-source (MIT) baseline for "public URL to localhost" capability, which lets you frame the buy decision around ngrok/Cloudflare Tunnel as an ops and SLA purchase rather than a capability purchase. If the only requirement is developer webhook testing, this materially weakens the case for a paid tunneling vendor.
• Embedding "connect your local app" into the product. Because it's pure PHP with a Composer-installable CLI and a self-hostable server, you can ship an artisan expose-style command or a bundled binary inside your own developer tooling, keeping the tunnel experience inside your brand instead of sending users to a third-party dashboard.
• Self-hosted / data-residency tier. Teams that cannot route traffic through a US SaaS vendor become addressable. A private tunnel server is a concrete, low-investment differentiator for regulated, on-prem, or air-gapped-adjacent customers.
• Roadmap input for webhook and integration testing. Adoption surfaces real usage patterns — persistent URLs, custom subdomains, request inspection, replay — which are the same primitives behind a "webhook debugger" or "integration sandbox" feature. Use pilot telemetry to decide whether that becomes a first-class product surface.
• Cost and vendor-risk reduction. Replacing per-seat tunneling subscriptions with an internally hosted service is a defensible line item in infra spend reviews, and removes a dependency risk if a vendor changes pricing or terms.
• Developer onboarding and demo workflows. Faster time-to-first-successful-integration for customers whose setup requires a callback URL, plus a low-friction way for Sales/Solutions to share a live local demo.

When to Consider This Package

Adopt when most of the following hold:

• Your stack is PHP/Laravel-centric and the team is comfortable operating ReactPHP-based services and a CLI distribution.
• The need is developer-facing or internal: webhook testing, local integration development, staging/demo links — not customer-facing production ingress.
• You want self-hosting or on-prem distribution and can own TLS termination, authentication, rate limiting, and abuse prevention around it.
• Licensing matters: MIT is compatible with closed-source embedding and commercial redistribution, unlike some tunneling competitors.
• Traffic expectations are modest and bursty — a handful to low hundreds of concurrent tunnels, HTTP/HTTPS dominant.
• You need a reference implementation to evaluate build-vs-buy quickly rather than a hardened, supported platform.

Look elsewhere when:

• You need production-grade ingress with SLAs, global points of presence, DDoS absorption, or anycast routing — that is a managed-vendor problem, not a PHP package.
• You require non-HTTP protocols or complex L4 use cases at scale.
• You have no appetite for operating a public-facing relay: an open tunnel endpoint is an abuse and phishing magnet, and the security/trust-and-safety burden lands entirely on you.
• You need commercial support, indemnity, or compliance attestations (SOC 2, ISO 27001) — MIT OSS provides none of that.
• Your platform is not PHP and adding a PHP runtime purely for tunnels is disproportionate; a Go-based or vendor solution is simpler.

How to Pitch It (Stakeholders)

For executives. We currently depend on a third-party tunneling SaaS for developer webhook testing, integration onboarding, and demo links — a recurring cost and an availability/terms risk we do not control. Expose is a mature, well-adopted (4.5k+ stars), MIT-licensed tunneling service written in PHP that we can host ourselves. It lets us (a) remove or downgrade a paid vendor line item, (b) offer a self-hosted option that unlocks security-sensitive customers who refuse third-party traffic routing, and (c) keep the developer experience inside our own product. The recommendation is a time-boxed pilot scoped to internal developer tooling, with a go/no-go gate on operational effort and abuse-handling burden before any customer-facing commitment. This is not a replacement for production ingress infrastructure.

For engineering. Expose is a pure-PHP CLI client plus a server component built on ReactPHP, distributed via Composer, with custom-domain and self-hosted server support. Practically: install it as a dev dependency, wrap the client in an Artisan command, and stand up the server behind our existing load balancer. It is small, readable, and easy to fork if we need auth hooks or request logging. The real work is not integration — it is operations: TLS, authentication, rate limits, abuse prevention, and log hygiene for a publicly reachable relay. Treat the pilot as an ops exercise, not a coding exercise, and budget accordingly.