Would you like to put your brand ahead of the Symfony community? Make your Corporate social responsibility (CSR) policy a reality? The-Fast-Track book for v6 or SymfonyWorld Online conference next month are still open for sponsorship!
But in this blog post, I'd like to make a specific call to SaaS providers for whom Symfony has a bridge (aka plugins).
Are you working at Amazon? Or know someone who could help with this? Mailchimp anyone? Mailgun, Mailjet, OhMySmtp, Postmark, Sendgrid or Sendinblue? You work for a translation provider? Crowdin, Loco or Lokalise? Or maybe you're providing notification services, whatever that means? AllMySms, Clickatell, Discord, Esendex, FakeChat, FakeSms, Firebase, FreeMobile, GatewayApi, Gitter, GoogleChat, Infobip, Iqsms, LightSms, LinkedIn, Mattermost, MessageBird, MessageMedia, MicrosoftTeams, Mobyt, Nexmo, Octopush, OvhCloud, RocketChat, Sinch, Slack, Smsapi, SmsBiuras, Smsc, SpotHit, Telegram, Telnyx, TurboSms, Twilio, Yunpian or Zulip?
Symfony has many bridges with SaaS providers for its Mailer, Messenger, Notifier and Translation components. Those bridges are open-source, have been provided for free by volunteers and are maintainted with high-quality standards by the community for the time to come.
But why should the Symfony community maintain those bridges when most of those services are commercial ones in the first place? Instead of answering this question philosophically, we look at it in terms of economic dynamics: because Symfony is a high-impact and high-visibility project, contributing a bridge to it provides maximum value to the community. Yes, maintenance is not cheap. But as with any OSS software, its users are in charge. This means that bridges are provided on a best effort basis.
But we can do better: any specific SaaS provider in the list above is certainly looking for more users, if not for more clients. Did I mention that Symfony is a high-impact and high-visibility project? This also means that Symfony is a great marketing opportunity!
By sponsoring the bridge that integrates with your company's services, you'll get extra visibility that could lead to new clients. You'll also send a message of responsibility to your current clients, and you'll ensure that maintaining this bridge is worthwhile for Symfony.
Please browse our support page, select "Symfony Backers" and send us a message so we can get back to you with all the program details, including pricing and availability. I look forward to hearing from you.
PS: Did you spot it? Notably missing from the list above is the Mercure bridge for Notifier. The reason is that mercure.rocks already sponsors it. Thanks to them!
Sponsor the Symfony project.
Connectez-vous pour ajouter un commentaire
Autres messages de ce groupe

This week, Symfony development focused on improving the IsGranted attribute with a new option, updated the Route attribute to allow setting multiple environments, improved the DomCrawler component to

This week, development activity mostly focused on dealing with the deprecation of sleep/wakeup methods in PHP 8.5 and their replacement by serialize/unserialize methods. In addition, we published more

It’s been only in July that we published symfony/ai and kicked off our AI initiative, but the repository has been busy since day one. Over 500 stars, more than 200 pull requests & issues, trending

🎤 Take the stage at SymfonyCon Amsterdam 2025, on your own terms!
The Unconference track is back and more dynamic than ever!
This unique, participant-driven format invites attendees to shape

This week, Symfony completed the migration to PHPUnit 12 in the 7.4 branch, which required many changes during the past weeks, such as replacing annotations with attributes. In addition, we updated th

🧑💻HACKDAY IS COMING!
Get ready to code, collaborate, and contribute, Symfony Hackday is back!
Join us in Amsterdam on Saturday, November 29th, for a hands-on hackathon designed to bring the

This week, Symfony released the maintenance versions 6.4.24, 7.2.9, and 7.3.2. Meanwhile, we began deprecating the XML configuration format in some components, enhanced the YAML configuration format t