I am not convinced that 'not using yaml' and then show a visual ui to define ci pipelines is a great selling point. I definitely wouldn't want to define that through a UI. Instead I think high level of testability of such CI pipelines would be. At the moment it always commit and push the change and wait how the pipelines acts, rinse and repeat. If you could run it locally and find out the results would be such a time…
Running locally is not a thing though. There’s services that do exactly that though (https://dagger.io/, https://earthly.dev/).