VDP uses multiple licenses.

  • VDP Protocol: open-source and available under the MIT License
  • VDP Connectors (including data connectors, AI connectors and Blockchain connectors): open-source and available under the MIT License
  • VDP Operator: open-source and available under the MIT License
  • UI, API and services of Base and VDP: source available under the Elastic License 2.0 (ELv2)
  • Instill Cloud (fully-managed public cloud service for Base, VDP and Model): closed-source
VDP license overview
VDP license overview

The VDP project uses a polyrepo structure. The license for a piece of source code in a VDP-related repository is defined with the following prioritized rules:

  1. LICENSE present in the file
  2. LICENSE file in the same directory as the file
  3. First LICENSE file found in the parent directories up to the top level
  4. By default to the Elastic License 2.0 (ELv2)

Please read the FAQ section below regarding the license details. In short, unless you want to host VDP and sell it as an unstructured data pipeline service, or to sell a product that directly uses the UI or API of VDP, you are all set to go to use VDP in your project.

#About ELv2

The Elastic License v2 (ELv2) is a very simple, non-copyleft license, allowing for the right to "use, copy, distribute, make available, and prepare derivative works of the software”. The license allows the free right to use, modify, create derivative works, and redistribute, with three simple limitations:

  • You may not provide the products to others as a managed service
  • You may not circumvent the license key functionality or remove/obscure features protected by license keys
  • You may not remove or obscure any licensing, copyright, or other notices

If you want to use VDP without these limitations, please contact us at:

#License FAQ

#Why did VDP services adopt ELv2?

Our mission is to make AI accessible to everyone. The best way to achieve this is to make VDP free to use and source available to everyone, while ensuring we safely create a sustainable business. Therefore, we chose ELv2 since it is very permissive. On one hand, this allows us to provide users with free access to our source code, the permission to modify it. On the other hand, we've released Instill Cloud, a fully-managed public cloud service built upon VDP that offers additional features. With the license, we don't have to worry about our project being taken by some other companies for monetization.

#Why are VDP connectors open source?

We want to build VDP as an open platform that integrates with other awesome tooling and services. And we think the best way to build these integrations is via open source, no matter it is a data connector that connects data to a warehouse, application, or database, or a AI connector that connects AI models from self-hosted or 3rd party platforms. This also benefits the projects that want to integrate with these connectors.

#How do I contribute to VDP?

Anyone can contribute to any repositories of VDP (including VDP services under ELv2). We are introducing a Contributor License Agreement that you will have to sign with your first contribution.

#My company has a policy against using code that restricts commercial use - can I still use VDP?

You can use any software under ELv2 for your commercial business, as long as you don't offer it as a managed service.

#I'm building an application on top of VDP, how does it work for me?

You can freely use VDP inside your SaaS and internal applications, and redistribute it with your application, as long as you follow the three limitations outlined above.

#Can you provide some examples of what isn't allowed under the VDP license?

There aren't many you can't do with VDP that is under ELv2. Here are some examples:

  • Self-host VDP and charge people money to access it.
  • Sell a product that directly exposes the UI or API of VDP.
  • White-label VDP and sell it as a product.

If you are still not sure whether your use cases are permitted or not, please email us at

Last updated: 9/7/2023, 6:02:58 AM