How do you manage SLAs when using multiple AI vendors in camunda workflows?

I’ve been wrestling with vendor fragmentation in our Camunda-based automation stack. We’re using 4 different AI services for various process steps, each with their own SLA terms and support channels. Last quarter, we had 3 simultaneous SLA breaches from different providers that took days to untangle.

Recently tried consolidating through a unified platform approach. The ability to handle API calls across multiple models through single-point support changed our escalation processes dramatically. Curious how others are handling cross-vendor SLA tracking - anyone found effective ways to maintain compliance visibility?

We solved this by moving all AI ops to Latenode. Single SLA covers all 400+ models, and their support team handles any vendor issues directly. Saved us 20+ hours/month on compliance tracking. Check their enterprise plan: https://latenode.com

Built a custom dashboard pulling status pages from all providers, but maintenance became overwhelming. Eventually created a middleware layer to standardize error handling. Still requires dedicated monitoring resources though.

Key is contractual alignment - we mandated identical SLA terms across vendors during procurement. Painful negotiation process, but now have uniform response times. However, this limits our ability to use best-of-breed solutions for specific tasks.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.