Brevo as a Community emailing domain driver?

[m0rdras]

We self-host Twenty in the EU and would like to run campaigns and email groups through Brevo (EU-based; its API covers domain authentication, batch sends, bounce/complaint webhooks and inbound parsing). We'd contribute a complete BREVO driver following the Resend driver from #24202: domain find-or-create and verification, sending, a signed bounce/complaint webhook into the neutral suppression handlers, and an inbound message source for email groups.

Before we start: would you accept it as a Community driver, like Resend, or would it fall under the Enterprise split from #24206?

[twenty-eng-sync[bot]]

This is a feature request/inquiry, not a report of an existing defect: it asks whether a proposed Brevo emailing driver would be accepted as a Community driver or fall under Enterprise. Severity is UNDEFINED because no broken behavior is reported. No root-cause hypothesis applies. No reproduction steps, version, or screenshots are provided; those are not needed to answer the policy question.

[BOHEUS]

@FelixMalfait @neo773

[FelixMalfait]

Hi Stefan, thanks for asking! We're not very clear on the strategy for drivers/licensing yet since emailing is a new product that isn't officially launched yet. I'd say it makes sense to have a EU-only provider in community but brevo seems a bit too "high level" for me, I would have preferred something that overlaps less with Twenty and is more infra-level (and therefore also cheaper). So I would advise to hold on for now, sorry :(