M3O seems to be more like an API aggregator with its core available as open source. Not an AWS alternative at all. Ultimately it looks like it is hosted on DigitalOcean if you let them run it for you: https://github.com/m3o/platform/blob/39b5d04a933ae3b63490081... for example. If it is meant to be an AWS alternative, then it will grow as big and complex as AWS if it gets popular and used by many.
Some of the API-wrapped services require you to get separate accounts for them like weather, sms, email, etc. Don't see a value unless they have multiple providers for each service to pick from. And then you may be in the situation of wanting a feature available for only one of the providers... in which case you'll end up having them to wait to support the feature, or support tacking on info to API calls not unlike Kubernetes metadata annotations. Or in the UI world waiting on features being added to a cross-platform API.
Some of the API-wrapped services require you to get separate accounts for them like weather, sms, email, etc. Don't see a value unless they have multiple providers for each service to pick from. And then you may be in the situation of wanting a feature available for only one of the providers... in which case you'll end up having them to wait to support the feature, or support tacking on info to API calls not unlike Kubernetes metadata annotations. Or in the UI world waiting on features being added to a cross-platform API.