How our distributed orchestration engine is built for reliability, and where specific commitments are defined.
COWE runs on a distributed, pull-based worker model with a transactional outbox and dead-letter handling, and is designed for high availability. Specific availability targets and any associated service credits are defined in the written agreement for Enterprise plans; contact us to discuss an SLA for your deployment.
For multi-step workflows, COWE uses a transactional outbox to avoid dropped or duplicated side effects, and supports BPMN compensation events so a failed transaction can be rolled back through explicitly modelled compensation steps. Workflow state is persisted durably so interrupted runs resume rather than restart.
For strict data-residency or isolation requirements, COWE can be self-hosted in your own environment (on-premise or private cloud), giving you full control over where data lives. Encryption at rest uses AES-256-GCM with per-tenant key wrapping. We do not currently hold FIPS 140-3 or similar cryptographic certifications.
Support scales with your plan: Professional includes business-hours support and access to the full documentation and troubleshooting guides; Enterprise adds priority response and a named contact. Response-time commitments, escalation paths and any dedicated-support arrangements are set out in your written agreement. Operational tooling — visual run replay, dead-letter inspection and metrics — is included so most issues can be triaged from the dashboard.
COWE processes the data you route through your workflows on your behalf. Connectors run with your own provider keys (BYOK) — payments, messaging, accounting and identity calls go directly to those providers under your accounts, and COWE does not hold a master key across your integrations. A list of infrastructure sub-processors (hosting, email delivery) and a Data Processing Addendum are available for Enterprise customers on request.
COWE runs the workflows you build, including custom scripts. Custom code executes inside a hardened, network-restricted sandbox with CPU and memory limits, and the platform enforces protections against abuse — SSRF filtering on outbound calls, per-tenant rate limits, and execution guards against runaway loops. You remain responsible for using the platform lawfully and for the credentials and data you connect to it.