This page is only about backend integration. Either your backend connects directly to OpenQloud, or you expose APIs and webhooks so OpenQloud integrates against your platform.
Two backend variants
There are only two cases here: your backend integrates directly with OpenQloud, or OpenQloud integrates against the backend surface you expose.
Each product page lets you choose between active backend integration and passive backend integration.
Active backend
Your platform keeps its own backend and integrates with OpenQloud directly through APIs, webhooks, events, and operational data flows.
This is the active backend variant.
Passive backend
Your platform exposes APIs and webhooks, and OpenQloud builds and maintains the integration layer against that contract.
This is the passive backend variant.
Role directory
Each backend type supports one or both integration variants. Open the product page to choose active backend integration or passive backend integration.
POS manufacturers and back-office platforms seeking real-time sync for orders, catalogues, and payments.
Food marketplaces preparing to publish modules on the standard.
Brand-owned websites that need to plug into POS, PSPs, and delivery services via the standard.
Table-ordering apps that orchestrate dine-in flows, menus, and payments with QR codes.
Self-service kiosks seeking a neutral backend for catalogues, orders, and payments.
At-table devices coordinating menus, POS, and service providers without bespoke integrations.
Kitchen orchestration displays syncing tickets, prep timing, and expo workflows across providers.
Handheld ordering terminals for staff that need neutral access to menus, payments, and POS data.
Reservation and guest-management platforms syncing bookings, seating plans, and diner profiles.
Consumer booking marketplaces distributing demand to restaurants through the OpenQloud standard.
SaaS, white-label commerce, and owned channels operating multiple providers without one-off integrations.
Last-mile fleets and logistics operators exposing dispatch, tracking, and settlement via OpenQloud.
Delivery management platforms exposing dispatch, driver, and logistics APIs to OpenQloud.
Payments infrastructure that wants to become plug-and-play across platforms, marketplaces, and POS.
AI copilots or automation suites consuming normalized hospitality data and events.
Finance and back-office suites syncing invoices, payouts, and settlements from OpenQloud.
FAQ
No. Start with your backend type. Inside that page you can choose whether you are integrating your backend actively or exposing a passive backend surface.
Yes. Real time is not a separate category. Backend active integrations and backend passive integrations can both exchange state in real time through the same APIs and event layer.
That is a separate concern from backend integration. OpenQloud provides the shared system underneath, while Service Providers operate the business-facing platforms used by merchants.
