Skip to content

Integrations

Every connection, and where it stands.

Dira connects delivery marketplaces, POS systems, infrastructure and finance through adapters around one canonical order model. Each entry below shows what it connects, the data that moves and its current status.

Book a demoHow adapters work
All categories12 entries

Showing 12 integrations in all categories.

  • Marketplace adapter for order intake, status synchronization and menu publishing.

    Data that moves
    • Orders
    • Cancellations
    • Order status
    • Menus
    • Store availability
    • Payout reports
    Direction
    • Orders in
    • status both ways
    • menu and availability out
    Used by
    Dira Connect
    Status
    Integrated. Built into the current Dira release and in use on the platform.

  • Marketplace adapter built on the same canonical order model. Targeted next.

    Data that moves
    • Orders
    • Cancellations
    • Order status
    • Menus
    • Store availability
    Direction
    • Orders in
    • status both ways
    • menu and availability out
    Used by
    Dira Connect
    Status
    In development. Adapter in active development and targeted next. Not yet live.

  • Marketplace adapter built on the same canonical order model. Targeted next.

    Data that moves
    • Orders
    • Cancellations
    • Order status
    • Menus
    • Store availability
    Direction
    • Orders in
    • status both ways
    • menu and availability out
    Used by
    Dira Connect
    Status
    In development. Adapter in active development and targeted next. Not yet live.

  • One gateway contract between canonical orders and every POS adapter, with retry and degraded-mode recovery.

    Data that moves
    • Order injection
    • Tender mapping
    • Cancel and void
    • Kitchen status events
    Direction
    • Orders out
    • status and tickets in
    Used by
    Dira Bridge
    Status
    Platform capability. A Dira platform feature available to every deployment.

  • Connectors to a brand's POS are isolated behind adapters and validated with that brand before go-live.

    Data that moves
    • Menu ID mapping
    • Checks
    • Store controller health
    Direction
    • Orders out
    • status and tickets in
    Used by
    Dira Bridge
    Status
    Scoped per deployment. Connected through Dira's adapter model and confirmed for each brand's systems during onboarding.

  • Progressive web app for in-store teams, including manual entry when a POS is unavailable.

    Data that moves
    • Order queue
    • Manual entry
    • 86 and pause actions
    Direction
    • Orders and alerts in
    • availability and pauses out
    Used by
    Dira Store
    Status
    Platform capability. A Dira platform feature available to every deployment.

  • Containerized Dira services run on a Google Cloud reference deployment.

    Data that moves
    • Cloud Run
    • Pub/Sub
    • Cloud SQL
    • Cloud Storage
    • Redis
    Direction
    • Hosting and managed services
    Used by
    Dira platform core
    Status
    Reference deployment. The environment Dira is built and tested on today.

  • Orders, catalog, stores and events live in PostgreSQL with an event/outbox model.

    Data that moves
    • Logical schemas
    • Event and outbox tables
    Direction
    • System of record
    Used by
    Dira platform core
    Status
    Platform capability. A Dira platform feature available to every deployment.

  • Documented, contract-tested interfaces for orders, catalog, stores and events.

    Data that moves
    • OpenAPI 3.1 contracts
    • Webhooks
    • Canonical events
    Direction
    • Both ways
    Used by
    Dira platform core
    Status
    Platform capability. A Dira platform feature available to every deployment.

  • Import payout reports and match each line to the canonical orders behind it.

    Data that moves
    • Payout lines
    • Commissions
    • Adjustments
    Direction
    • Payout reports in
    Used by
    Dira Reconcile
    Status
    Platform capability. A Dira platform feature available to every deployment.

  • Export reconciled entries into your existing finance and accounting process.

    Data that moves
    • Sales
    • Fees
    • Adjustments by channel and store
    Direction
    • Journal entries out
    Used by
    Dira Reconcile
    Status
    Platform capability. A Dira platform feature available to every deployment.

  • Channel profitability and operational KPIs from the same event history that runs orders.

    Data that moves
    • Channel performance
    • Store KPIs
    • Exception trends
    Direction
    • Read
    Used by
    Dira Command
    Status
    Platform capability. A Dira platform feature available to every deployment.

Statuses reflect the current Dira release and are confirmed with each brand during deployment scoping. Marketplace names describe compatibility only. No entry implies a certification or partnership with the named provider.

What each status means

Integrated
Built into the current Dira release and in use on the platform.
In development
Adapter in active development and targeted next. Not yet live.
Scoped per deployment
Connected through Dira's adapter model and confirmed for each brand's systems during onboarding.
Platform capability
A Dira platform feature available to every deployment.
Reference deployment
The environment Dira is built and tested on today.

Need a system that isn't listed?

Tell us what your restaurants run. We'll look at how it connects to Dira through an adapter and what it would take to support it in your deployment.

Every new connection is scoped with your team and validated against your systems before go-live.

Tell us what you runHow Dira Bridge connects POS

How adapters work

New channels connect at the edge. The core stays the same.

Every external system talks to Dira through an adapter. The adapter translates that system's payloads into canonical orders and events, so the rest of the platform never depends on which channel or POS an order came from.

Read the architecture
Channel adapters
  • Uber EatsIntegrated
  • DoorDashIn development
  • GrubhubIn development
  • The next channel
diraShared core
  • Canonical orders
  • Catalog
  • Store identity
  • Event history

One order model, versioned OpenAPI 3.1 contracts, PostgreSQL event and outbox tables.

Restaurant system adapters
  • POS gatewayBrand POS connectors
  • Store tablet appQueue, 86, pauses
  • FinancePayout reports, journal export
Simplified view of Dira's adapter boundaries.

  • Adapters translate.

    Each adapter validates incoming webhooks, maps the provider's order and menu formats to the canonical model, and applies that provider's status and cancellation rules.

  • The core does not change.

    Orders, catalog, store identity and event history keep one shape. Adding a marketplace means adding an adapter, not rebuilding the order pipeline.

  • Problems stay contained.

    Processing is idempotent and every event is recorded. When a provider or POS is unavailable, its adapter retries or holds work for replay without touching the rest of the network.

See how Dira fits the systems you run.

Bring your channel list and POS. We'll walk through how each one connects.

Book a demoArchitecture and APIs