I was not involved in evaluating other options or choosing this solution. 

Yes, considerations were given to open source products (Jenkins/Hudson, go.cd ...).  It did not appear that any of the others considered could provide an equivalent of the remote build feature offered by TeamCity.

We're currently looking at Harness, which seems to have a few more out of the box features that we need, so we are considering either integrating the two together, or switching over entirely.

There are two teams — on-prem and cloud — and the cloud team uses TeamCity. On-prem uses SUSE automation.

We evaluated a few other products. The only product that had was a real contender was Electric Commander.

We did not evaluate other options prior to going with TeamCity. It was the first one we picked for the integration of our CI/CD.

No other options were evaluated.

No other options were evaluated.

Jenkins, but it was not mature enough and did not meet our needs at that time.

I have used all leading CI tools.

We did not evaluate other options but we may consider moving to Jenkins because it's free and has many similar features.

Jenkins.