# Choose the development source

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

A gadget’s SDK identifiers still use @activepieces/*. That does not mean the current upstream branch is the source for your Sydekyks deployment.

## ​Develop for a Sydekyks deployment

Obtain the supported repository or source bundle and full revision from your deployment administrator. Match the SDK, lockfile and application build to that release. Make changes on a development branch, build the package, and test it against the matching application before distribution.

The local documentation reference uses the renamed product-language checkout. It includes working changes and is not an immutable public release. Do not assume a fresh clone of upstream reproduces its interface or independently authored modules.

If no supported source revision has been supplied, request it before following the development setup (https://docs.sydekyks.com/build-pieces/building-pieces/development-setup). Keep your source, changes and test evidence reviewable.

## ​Contribute to upstream

For an upstream Activepieces contribution, fork the upstream repository (https://github.com/activepieces/activepieces), follow its contributor instructions, and open the contribution there. Test against the upstream revision required by that project.

An upstream contribution and a Sydekyks release patch have separate review and release destinations. A private Git repository is a source-management choice; it does not enable native paid private-piece upload controls.