Supported platforms & integration targets

Built to work with the stack you already run.

Signage players and operating systems, in-store sensors, and commerce / POS platforms — connected through documented APIs, OAuth, webhooks, middleware, and scoped custom work. No rip-and-replace.

Signage players & operating systems

Signal monitors and Relay operates mixed estates across dedicated players and system-on-chip displays.

In-store sensing

Sensor events become triggers for Relay, health signals for Signal, and audience intelligence for Glass.

Commerce & POS platforms

Glass correlates campaign and screen activity with store-level outcomes — without creating a data silo.

Core integration targets

Restaurant & hospitality

  • Toast

    Restaurant order, menu-item, and daypart performance signals for menu-board and promotion analysis.

    Available through provisioned or partner-scoped API access depending on the use case.

  • Lightspeed Retail

    Store-level sales, SKU performance, and inventory availability through supported OAuth APIs.

Enterprise & QSR

  • Oracle Simphony

    Enterprise QSR transaction and menu-item context, scoped to the specific API product and its permitted use.

    Requires provisioned or custom access; analytics use must respect the permitted use of the specific Simphony API product rather than assuming bulk analytics access.

How integrations are delivered

Every connection is validated against the vendor's documented surfaces before we commit to scope.

Documented APIs

Built on publicly documented vendor APIs, read within the permissions and rate limits each platform grants.

OAuth & merchant authorization

Commerce integrations connect through per-merchant or per-location authorization with scoped permissions.

Webhooks & event streams

Order, inventory, and playback events delivered as they happen for near-real-time automation and correlation.

Middleware & exports

Where direct APIs are restricted, supported middleware, scheduled exports, or scoped custom work bridge the gap.

Product names and logos belong to their respective owners. These are supported platforms and integration targets built on publicly documented APIs — listing does not imply a formal partnership or endorsement. Specific fields, events, rate limits, approvals, and features depend on each vendor's APIs, your plan, granted permissions, and implementation scope. We validate scope during discovery.