Yes, it is possible to build a local version of a connector and use it in your own production instance. Here are the steps you can follow: 1. Make the necessary changes to your connector. 2. Build the connector using the following command: ./gradlew :airbyte-integrations:connectors:source-custom-name:build This command is run from the root of the Airbyte repository[^1^]. 3. Once the build process is complete, you can tag the image[^1^]. 4. Add it as a custom connector in the Airbyte UI. You can do this by going to Settings → Source → Custom Connector[^1^]. 5. If you’re running Airbyte locally, it will have access to any Docker images available to your local docker daemon[^4^]. 6. You can verify the image was built by running: docker images | head[^4^]. 7. In your browser, visit http://localhost:8000/, log in with the default user airbyte and default password password. Go to Settings (gear icon in lower left corner), go to Sources or Destinations (depending on which connector you are testing), update the version number to use your docker image tag (default is dev), and click Change to save the changes[^2^]. 8. Now when you run a sync with that connector, it will use your local docker image[^2^]. Please note that for real production connectors to be available on Airbyte Cloud, you’d need to publish them on DockerHub[^4^]. [^1^]: Forum Post: How do I locally switch to a modified version of a connector? > Answers [^2^]: Documentation > Contributing-to-airbyte > Resources > Developing Locally > Add a connector under development to Airbyte [^3^]: Documentation > Connector-development > Tutorials > Building a Source Connector: The Hard Way > Our connector: a stock ticker API > Use the connector in the Airbyte UI > 1. Publish the Docker image [^4^]: Github Issue (closed): Optionally build python connector with the local CDK > Original post