[tair]

We're not PaaS and not hosting anything, only orchestrating, so scaling is not our biggest concern right now. All the integrations are run in one-off Docker containers, which we're managing in our internal Docker cluster. Up until now we've been adding integrations ourselves, but the plan is to open-source our integration framework and let anyone add support for their tools. It's going to be quite easy, we will most probably require only Dockerfile and a metadata file for us to build the pipeline UI.

Answering your downtime question, sure we will provide plans with SLAs and multi-AZs, but basically it's a similar situation when repository hosting provider, DNS, container registry, or another infrastructure service is unavailable. That being said, we'll definitely think of a way to provide a fallback mechanism. Thank you!