We built updatable starters on Railway by automagically provisioning a database and deploying popular open-source applications, allowing users to easily deploy projects without requiring extensive development knowledge. However, this presented an issue when the original project got updated, as the user's deployment would fall behind. To solve this, we mirrored the original repository, used upstream remotes to keep it in sync with the user's repository, and checked for updates periodically, prompting users to update their repository via email. This allowed us to support scenarios where users wanted to use a starter as is, without requiring extensive development knowledge.