Sendinblue Laravel Package

Product Decisions This Supports

• Build vs. buy for marketing/CRM integration. This bundle is a pre-built, MIT-licensed connector between the Splash Sync middleware and Brevo (formerly Sendinblue). It supports the decision to buy the integration layer (Splash + connector) instead of building Brevo contact/list/campaign sync logic in-house — but only if Splash is already (or will be) part of the stack.
• Feature and roadmap scoping. If the roadmap includes two-way sync of contacts, lists, segments, or transactional events between our product and Brevo, this bundle is a concrete reference for what a Brevo connector must cover and how it plugs into a sync framework. It can inform estimates and the connector contract we'd need.
• Integration architecture choice. Because it is an embedded Symfony bundle (not a Laravel package or a standalone SDK), it forces an early architectural decision: adopt Splash's connector model, or go direct to Brevo's own API/SDK.
• Use cases where it applies: running Splash Sync and needing Brevo as a connected app; building a Splash-compatible server; standardizing B2B SaaS connectors on Splash; prototyping Brevo sync without writing the connector from scratch.
• Vendor and lock-in decisions. MIT licensing plus the tiny, self-contained surface means low legal friction and easy forking — a plus for a buy decision, with the caveat that the surrounding ecosystem is small.

When to Consider This Package

Consider it only if all of the following hold:

• You already run, or are deliberately adopting, Splash Sync (or a Splash-compatible server) as your integration/middleware layer.
• Brevo is a required connected app, and you want an existing connector rather than building the mapping yourself.
• Your host application is Symfony/PHP and can install an embedded bundle.
• You are comfortable treating it as a reference implementation or fork candidate, not a supported, high-availability dependency.

Look elsewhere when:

• You have a Laravel app that just needs Brevo transactional email or contacts — use Brevo's official API/SDK or a purpose-built Laravel package instead. This bundle is the wrong tool for that job.
• You are not on Splash — the connector is tightly coupled to Splash's connector framework; its value collapses outside that ecosystem.
• You need SLA, active support, or a large community — 0 stars and 0 dependents is a clear adoption/support red flag; treat maintenance as an internal responsibility if you adopt it.
• You want a generic iPaaS with broad, actively maintained connectors — a mainstream integration platform will beat a single-vendor niche bundle on longevity.

How to Pitch It (Stakeholders)

For executives: This is a free, open-source (MIT) connector that lets us plug the Brevo marketing/CRM platform into a synchronization layer without building that integration ourselves. It is ecosystem-specific — it only adds value if we adopt Splash Sync as our middleware — and it has essentially no public adoption, so we should position it as an optional reference or forkable starting point, not a core dependency. The recommendation is to validate it only if we commit to Splash; otherwise we should integrate Brevo directly via its official SDK.

For engineering: An embedded Symfony bundle implementing Splash's connector interface for the Brevo API — small surface, MIT, easy to read and fork. It is not a Laravel package and not a standalone Brevo client. Adopt only inside a Splash-based stack; otherwise use Brevo's official SDK. Assume we own maintenance and testing, since the project has no dependents or community to lean on.