Active backend
Integrate your backend.
Your platform keeps its own backend and integrates with OpenQloud directly through APIs, webhooks, events, and operational data flows.
Kitchen orchestration displays syncing tickets, prep timing, and expo workflows across providers.
Backend integration
Integration is decided per product: connect your backend directly or expose an API so OpenQloud can maintain the adapter.
Active backend
Your platform keeps its own backend and integrates with OpenQloud directly through APIs, webhooks, events, and operational data flows.
Passive backend
Your platform exposes APIs and webhooks, and OpenQloud builds and maintains the integration layer against that contract.