OQ
Shared model and OQIDs
Un modèle de données canonique et des OQIDs partagés pour les restaurants, les marques, les emplacements et les relations au sein de l'écosystème.
OpenQloud Operator
Transforme su plataforma en un Operador de OpenQloud.
Integrate OpenQloud into your SaaS so restaurants and chains can create, configure, and manage their presence in the ecosystem without leaving your product.
The restaurant keeps operating inside the operator's product. OpenQloud remains underneath as the shared system for data, identity, and operational coordination.
Operator capabilities
Create restaurants, brands, and locations in OpenQloud
Configure connections, activations, and integrations
Manage operational context and ecosystem relationships
Definition
What an OpenQloud Operator is
An OpenQloud Operator is a company or platform that integrates OpenQloud and acts as the management point for restaurants inside the ecosystem.
The operator uses OpenQloud APIs to create entities, activate connections, configure operational relationships, and keep the restaurant presence aligned in the shared system.
The restaurant keeps working inside its usual SaaS or platform, while OpenQloud stays underneath as the common GDS layer for identity, data, and coordination.
The operator is the company or platform integrating with OpenQloud APIs and operating the relationship from its own backend.
API surfaces
Operators use the OpenQloud Operator API.
This path is the management control plane for presence, entities, relationships, modules, access, and operational context in OpenQloud.
What OpenQloud provides underneath
OpenQloud stays below as the shared coordination layer.
The operator owns its backend and customer relationship. OpenQloud provides the shared system underneath so all connected actors work through the same identity, coordination, and operational model.
OQ
OpenQloud Operator API
The integration surface your platform uses to create entities, configure relationships, and operate presence in OpenQloud.
OQ
Synchronization and events
Eventing und Synchronisierungsmechanismen, die verbundene Systeme mit dem gemeinsamen Betriebszustand in Einklang halten.
OQ
Distributed runtime
Distributed runtime across cloud and local node for continuity, resilience, and low-latency execution.
Who this is for
Platforms that need backend control of OpenQloud presence.
This path is for platforms that manage restaurants, chains, or channels in their own backend and need OpenQloud to synchronize that operational context with the ecosystem.
POS and operational suites
Vertical SaaS products for restaurants
Owned channels, kiosks, and ordering products
Backoffice, orchestration, and integration platforms
Platforms that need backend control over restaurant presence and integrations
Next step
Your backend manages. OpenQloud coordinates.
If your platform needs to create and administer restaurant presence in OpenQloud, integrate the OpenQloud Operator API.