(for technical builders)
External 'X as a service' tools, especially large ones are created for typical use cases (even if the blurb does not say so explicitly): they are in the end products and thus 'packages of emphasis' and highly opinionated.
However, your use case, especially if you are at a startup, is unlikely to be typical. So even if a product promises to 'solve X' for your stack, it is worth considering whether you would be better off solving X yourself; with the aid of more granular, technically focussed packages/services, rather than a larger, business focussed one.
Maybe this is one more reason to learn to code!
Thoughts?
Stackradar