# Maintain the source fork

Sydekyks user and operator guide. Check feature availability and release-specific installation requirements.

A private Git repository is a source-management choice. It does not activate the upstream paid private-piece upload feature.

## ​Create and maintain the fork

Keep an upstream remote for the Activepieces repository and a separate origin for the Sydekyks fork. Fetch upstream updates into a review branch, reconcile our branding and independently authored modules, then run the relevant checks before release.

Preserve applicable copyright/license notices and keep package names/import paths stable unless the implementation changes them. A global brand-name replacement in source code can break SDK imports, environment keys and API contracts.

## ​Custom integrations

Use the piece development guide (https://docs.sydekyks.com/build-pieces/building-pieces/overview) to build and test an integration. Public npm distribution and source-built bundles are separate from the native paid tarball-upload and private-piece-management workflow.

Choose the supported deployment path for the custom bundle and verify that the runtime can resolve the exact piece name and version.