Concepts · 3 min read
What you keep if you leave
Where your Terraform, your state and your workloads live, and why leaving SysJ does not mean starting over.
Your code is already yours
SysJ commits the Terraform it renders and the manifests it writes to a repository in your own source control. It opens changes into that repository rather than keeping a private copy you would need to export.
Your state is in your account
Terraform state lives in a bucket in your cloud account, encrypted with your key. SysJ reads and writes it during a run and holds no copy of its own.
Your workloads run without us
Clusters, databases and applications run in your account, and Argo CD keeps syncing from your repository whether or not SysJ is reachable.
What leaving looks like
Revoke SysJ’s role, and point your team or your next hire at the repository. They find a normal Terraform project and a normal GitOps setup.