Overview

As a developer extending Netlify, you can add on to the Netlify platform in several ways— whether it’s for your own use or something you want to make available to others.

Extensions vs. integrations

You may find resources that use the terms “extension” or “integrations” interchangably.

Generally, the term “extension” refers to artifacts created using the Netlify SDK that extend the Netlify platform, while “integration” can signal two systems coming together and are possibly not made with the Netlify SDK.

Extensions have the following ownership models:

• Official extensions: developed and supported by Netlify or one of our technology partners.
• Community extensions: developed and supported by customers and other third parties.

Framework adapters

If you are a framework author, you can integrate with Netlify using the Frameworks API. Use the API to build a framework adapter and define how a framework deploys sites to Netlify.

General extensions

For all other use cases, we recommend using the Netlify SDK to create an extension. An extension can integrate with other systems, add on to the Netlify platform, or both.

For example, you may develop an extension that renders a configuration form in the Netlify UI and uses the input values to connect to and sync data from a content management system to Netlify Connect.

You can develop an extension that does the following:

• runs logic during the build-deploy lifecycle for a site

Build plugins

You can also create a build plugin to extend the functionality of the Netlify Build process but we recommend you use the updated Netlify SDK to create extensions instead.