logo
  • Core Gateway
  • Documentation
  • Blog
  • Changelog
  • Pricing
  • About
Blog
Announcement

Why we’re adopting the ELv 2.0 License

2 min read September 02, 2024

Written by

Subomi Oluwalana
Subomi Oluwalana

Co-Founder & CEO

Share

Dear Convoy Community,

In our upcoming release, we’re transitioning from the MPL 2.0 License to the ELv 2.0 License, and I wanted to share why we’re making this transition and what you can expect from us in the coming months.

In the past few months, we’ve been working with some of our users who are happy self-hosting Convoy and delivering millions of webhooks monthly; they’re not looking to switch to the Cloud platform. Most of these companies already have a commercial relationship with us, but what’s missing is a mechanism for us to continue delivering proprietary features to these users while keeping the free and open-source offering available. Today, we’re making this available by relicensing Convoy.

Before settling on the Elastic License, we considered several other OSS licenses, but none of them perfectly fit our scenario. Our approach to monetising open source is the buyer-based open core framework, where proprietary features are designed specifically for the user who cares most about them. There are multiple ways to deliver on this promise. For example, GitLab offers a dual license model with an ee directory containing all its paid features. Sidekiq provides a core open-source project with a closed-source pro library with proprietary features built as plugins.

We decided on ELv 2.0 because the other techniques required a slightly more complex software delivery model with multiple repositories and dual licenses. ELv 2.0 enables us to have a more straightforward development workflow—we can maintain one repository and deliver all features via one binary. Users upgrading from the community edition to the business edition will only need a license key to access new features—no new deployment is needed!

Fundamentally, we’ve also learned that our users care about the stability and reliability of Convoy far more than our license choice, and we desire to build the world’s most advanced webhook gateways that users can depend on in production.

If you have any questions, please feel free to email me at subomi at getconvoy dot io or join our Community to share your thoughts.

Getting started with Convoy?

Want to add webhooks to your API in minutes? Sign up to get started.

Related Posts

How Spruce Accelerated Event Delivery with Convoy Fan-Out Functionality

February 02, 2026

Spruce Principal Engineer Michael Raines shares how Convoy fan-out functionality and reliability helped their lean engineering team deliver webhook events to customers efficiently, saving an estimated six to nine months of development time.

Oluwatosin Fatungase
Oluwatosin Fatungase

Business

10 Most common Use Cases of a Webhook Gateway

March 07, 2023

This article considers ten of the most common use cases of a webhook gateway, with emphasis on the features offered by Convoy.

Amarachi Aso
Amarachi Aso

Writer

logo

2261 Market Street, San Francisco, CA 94114

Companyaccordion icon

About Us

Trust Center

Terms of Use

Privacy Policy

DPA

Productaccordion icon

Open Source

Core Gateway

Convoy Playground

Resourcesaccordion icon

API Reference

Documentation

Status Page

Roadmap

What are Webhooks?

Convoy vs. Internal Implementation

Speak to usaccordion icon

Slack

[email protected]

Connect with us

Copyright 2026, All Rights Reserved

soc stamp