Whereby Bundle Laravel Package

Product Decisions This Supports

• Build vs. buy for real-time video. The decision that matters is Whereby-as-a-service vs. Twilio/Daily/Agora vs. in-house WebRTC. This package doesn't make that decision for you; it only lowers the cost of testing it in a PHP codebase.
• Feature validation before roadmap commitment. Lets you run a time-boxed spike ("do our users actually join video calls?") in days rather than a quarter, with a disposable integration surface.
• Candidate use cases worth scoping: telehealth/intake calls, live tutoring, remote interviews, premium-support escalation, marketplace consultations. The common thread is a scheduled, two-to-few-party call embedded in an existing workflow — not webinars or broadcast.
• Roadmap sequencing insight. Meeting provisioning (create/expire rooms, host vs. participant roles, join links) is thin backend work. If that's all this is, the real roadmap cost sits in the surrounding product — scheduling, reminders, consent/recording policy, per-session billing — and should be planned there.
• What it does not support: any decision that assumes a maintained dependency. Zero stars, zero dependents, last release 2020-10 means adopting this is adopting a fork you now own.

When to Consider This Package

Consider it only when all of these hold:

• You are on Symfony. Note the mismatch: this is a bundle, not a Laravel package — no service provider, facade, or publishable config. If your stack is Laravel, the due-diligence answer is "not applicable as packaged."
• You need a throwaway prototype to demo Whereby rooms in a staging app this week.
• You are already commercially committed to Whereby and want a starting point to read and copy from.

Look elsewhere when:

• Production SLA, security patching, or a compliance review (GDPR/DPA, HIPAA/BAA) is in scope. An unmaintained 2020 wrapper around a vendor API that has since evolved is a liability; call the current REST endpoints directly.
• You're on Laravel — a config file, a small HTTP client, and a facade is roughly a day of work and yours to maintain.
• Your requirements include recording, transcription, PSTN dial-in, or large sessions; validate the vendor's current capabilities before designing around this wrapper's older assumptions.

How to Pitch It (Stakeholders)

Video is table stakes in a few of our segments and a distraction in the rest. The question isn't whether we can build WebRTC — it's whether we can put a credible video surface in front of users in one sprint and measure whether they use it. Whereby Embedded gets us there: rooms and join links provisioned via API, an embeddable client, no media infrastructure to operate, and usage-based cost that only scales if the feature earns its place.

The PHP package itself is a reference implementation, not a dependency we should ship — it's unmaintained and predates the vendor's current API, and it targets Symfony rather than our stack. Recommendation: fund a two-week spike using it as a starting point, fork the small amount of glue code into our own service layer behind an interface, and gate the roadmap on a measurable threshold (e.g., a target percentage of eligible accounts starting at least one call in month one) before committing to a paid tier or a multi-vendor evaluation. Engineering gets a clean abstraction to swap vendors behind; finance gets a usage-shaped cost curve instead of a build.