The migration is the lock-in, so we skipped it
eQuantic Space reads the pipeline files already in your repository, on GitHub, GitLab, Bitbucket or Azure DevOps.
Teams rarely stay on tooling they dislike because of the tooling. They stay because moving means rewriting everything they already have: dozens of pipeline files, the small fixes nobody remembers making, and the one job that only works because of an old workaround.
That rewrite is the real lock-in.
Read the files that are already there
So eQuantic Space reads the workflow files already sitting in your repository, as they are. It works with all four places those files live today: GitHub, GitLab, Bitbucket and Azure DevOps. Half a migration is still a migration.
Leaving stays easy too
Because nothing is rewritten, nothing is trapped. If you ever leave, your pipelines still work exactly where they came from.
Start with Repositories & CI/CD in the docs.