logo
  • Core Gateway
  • Documentation
  • Blog
  • Pricing
  • About
  • Sign In
    Start your project
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.

Sign up

Related Posts

What I’ve learned from talking to users as a Technical Founder

April 23, 2025

It’s widely accepted that the two most important things a startup needs to get right are building a great product and talking to users. As a technical founder, building has always come naturally to me. Talking to users? Not so much. In this post, i’ll share some of the misconceptions I had about talking to users—and the surprising benefits I’ve discovered from doing it consistently.

Subomi Oluwalana
Subomi Oluwalana

Co-Founder & CEO

Transactional Outbox: How to reliably generate webhook events

April 17, 2025

In the world of distributed systems, ensuring reliable event delivery is crucial, especially when dealing with webhooks. The transactional outbox pattern has emerged as a robust solution to this challenge. In this post, we'll explore how to implement this pattern to guarantee reliable webhook delivery, even in the face of system failures.

Subomi Oluwalana
Subomi Oluwalana

Co-Founder & CEO

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

Cloud

Convoy Playground

Resourcesaccordion icon

API Reference

Documentation

Status Page

Roadmap

What are Webhooks?

Convoy vs. Internal Implementation

Speak to usaccordion icon

Slack

Follow Us

Copyright 2025, All Rights Reserved

soc stamp