In terms of the tool's use case, if it is serverless, and if the compute involved is not too high, or if it is a PoC kind of a thing, and you want the microservices kind of architecture to be going and go for a pay as you go model, you can use the tool. With the tool, you know what is happening, so maybe you can cut costs by going with an on-premises model and having a stable system for computing.
The models that the tool has, the libraries, and the ML libraries are rich. That is good, and that is one of the features of the tool. The other feature is how the tool interacts with other components of AWS, like Lambda and S3. It's seamless if you are using AWS architecture.
I was working with Amazon SageMaker Ground Truth. The serverless feature is important and worth it because you don't have to spin up an EC2 instance every time or a server. For us, the main attraction is that it's serverless. You pay only for the compute that you use, and then there is its ecosystem. Whenever you use something in AWS, the ecosystem is very rich.