# Source Control Best Practices
**URL:** https://community.tago.io/t/source-control-best-practices/1860
**Category:** Analysis and Actions
**Created:** [February 19, 2026, 5:38am UTC](https://community.tago.io/t/source-control-best-practices/1860 "2026-02-19T05:38:19Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@info1](https://community.tago.io/u/info1)
#### Post date: [February 19, 2026, 5:38am UTC](https://community.tago.io/t/source-control-best-practices/1860/1 "2026-02-19T05:38:19Z")
Greetings,
My TagoIO implementation involves numerous custom payload parsers, analysis scripts and custom widgets. In all of these cases, code is cut & pasted from an external source into the respective Tago editors and saved.
While this works, it’s fairly clunky as any source control must be implemented externally.
Is there a recommended best practice for implementing conventional source control (e.g. git) for custom scripts & code used by TagoIO?
---
### Author:  [@mateus.silva](https://community.tago.io/u/mateus.silva)
#### Post date: [February 19, 2026, 2:50pm UTC](https://community.tago.io/t/source-control-best-practices/1860/2 "2026-02-19T14:50:01Z")
Hello @info1,
You can use any Git-based hosting service such as GitHub, GitLab, Bitbucket, or any other platform you prefer.
As a reference, you can take a look at this public repository that contains a Kickstart RTLS application:
[https://github.com/tago-io/analysis-kickstarter-rtls](https://github.com/tago-io/analysis-kickstarter-rtls)
As you can see, all Analysis scripts are hosted there. You can use this repository as a starting point to structure your own project and manage your code with proper version control.
For running Analyses externally or deploying them to TagoIO, we use the `@tago-io/cli` tool:
[https://www.npmjs.com/package/@tago-io/cli](https://www.npmjs.com/package/@tago-io/cli)
I strongly recommend using this CLI, as it significantly simplifies the deployment and management process.