Server Laravel Package

Product Decisions This Supports

• Self-hosted tunneling as a build-vs-buy decision. Expose (server component) is the open-source backbone for an ngrok-style tunnel service. This release is a signal that the project is maturing the operational edges of self-hosting, not just the tunnel protocol — relevant if you're weighing "run Expose ourselves" against per-seat SaaS tunnel subscriptions.
• TLS/HTTPS posture for internal infrastructure. 3.2.0 extends on-demand certificate issuance to the server's own infrastructure hosts. Product-wise this means the shared endpoint domain, dashboard/admin hosts, and other first-party hostnames can get automatically provisioned certs through the same ACME flow as customer tunnels — removing a manual cert-management chore and reducing the chance of browser warnings on surfaces your own team and customers hit first.
• Roadmap input for a hosted/shared offering. If you plan to resell or internally operate tunnels under a single wildcard-ish domain, automatic cert coverage of infrastructure hosts is a prerequisite for a polished branded experience (no mixed HTTP/HTTPS, no "not secure" interstitial on the landing/dashboard).
• Operational use cases it unblocks: ephemeral preview environments, webhook receivers for third-party integrations (Stripe, GitHub, Slack), demoing local builds to stakeholders, and IoT/edge devices dialing home — all where TLS trust is non-negotiable.
• Lower toil budget. Each manual cert renewal you retire is ongoing ops cost avoided; this is a small release with a disproportionately useful operational payoff.

When to Consider This Package

Adopt when:

• You need tunnels you control — data residency, compliance, or air-gapped/private-network constraints rule out third-party SaaS relays.
• You already run a PHP/Laravel-adjacent stack and want an operational surface your team can read and patch without learning a new language runtime.
• You want automatic TLS via ACME for both customer-facing tunnel hosts and your own infrastructure hosts (the 3.2.0 capability).
• You're building an internal developer platform where preview URLs and webhook endpoints are a first-class feature.

Look elsewhere when:

• You need a fully managed, zero-ops solution — Expose is self-hosted; you own uptime, certs, DNS, and scaling.
• You require enterprise SLA, SSO/RBAC depth, or audited support contracts out of the box.
• Your throughput/concurrency profile is high-volume production ingress — evaluate whether a ReactPHP-based tunnel server meets your latency and scale targets before committing.
• Your platform is polyglot-first (Go/Node/Rust) and PHP runtime familiarity is not in-house — the tunnel clients are cross-language, but the server's operational footprint is PHP.

Note this release is a narrow, additive change (no breaking changes, no deprecations indicated in 3.2.0). Treat it as a confidence-builder for the TLS story rather than a reason to re-platform.

How to Pitch It (Stakeholders)

For executives: Expose is an open-source, self-hostable alternative to commercial tunneling services. Release 3.2.0 closes a small but visible gap: the server can now automatically issue trusted TLS certificates for its own infrastructure hosts — the dashboard, shared endpoint domain, and admin surfaces — not just for customer tunnels. Translation: fewer manual cert renewals, fewer browser security warnings on your own pages, and a cleaner path to a branded, hosted tunnel offering if we go that route. No breaking changes; low-risk upgrade.

For engineering: 3.2.0 (exposedev/server PR #15) allows on-demand certs for the server's own infrastructure hosts within the existing ACME flow. Additive only — no migration, no config breakage expected. Worth validating that your infrastructure host list is correctly enumerated so cert issuance covers the intended hostnames, and that ACME rate limits/CA policy still hold at your expected host count. Recommend upgrading in staging first to confirm cert issuance behavior for first-party hosts before rolling to production.