Platform

The distribution operating system for hotels.

Hotels stay in control. Authorized partners sell. Every booking is revalidated, reconciled, and audit-logged.

Not a PMS · Not a Channel Manager · Not an OTA · Not a Bed Bank

The Escapra model

One governed spine, end to end.

Five pillars composed as a system. Each pillar is a section below.

Escapra sits alongside your PMS as a governed layer between supply and authorized B2B demand. The spine below is the contract — every booking traces this path.

Hotel

Owns the policy

PMS

System of record

Escapra

Govern · Authorize · Validate · Settle · Audit

Authorized Partner

Scoped, revocable

Booking

Quote → Hold

Revalidation

Live against PMS

Confirmation

Or 409 PRICE_CHANGED

Settlement

Atomic · Lineage

Audit

Append-only

Govern
Authorize
Validate
Settle
Audit

Five pillars · one governed layer · lineage end-to-end

PILLAR 01Governance

Distribution as policy, not configuration.

  • 1

    Distribution rules are policy, captured per booking — not a vendor configuration.

  • 2

    Rules are scoped, revocable, and enforced before any booking decision.

  • 3

    Every booking carries the governance decision that authorized it; lineage is queryable per booking.

  • 4

    Governance, inventory, and cancellation decisions are captured to an append-only audit.

PILLAR 02Authorization

Nothing sells until the hotel approves.

  • 1

    Hotels — not Escapra — decide which partners may sell, at what rate plans, on what terms.

  • 2

    Partner authorization is scoped per rate plan, segment, geography, and date range.

  • 3

    Tokens are bound to scope; they cannot exceed what the hotel authorized.

  • 4

    Revocation is immediate and audit-logged; in-flight bookings honor their existing terms.

PILLAR 03Booking Trust

Every booking, revalidated at the source of truth.

  • 1

    Every booking is revalidated against the hotel's source of truth before confirmation.

  • 2

    If the rate has changed, the partner receives 409 PRICE_CHANGED and must explicitly re-accept.

  • 3

    Stale inventory is blocked, not booked. Out-of-order ingest is rejected.

  • 4

    When capability degrades, the platform fails closed rather than book unsafely.

PILLAR 04Settlement

From booking to payout — one traceable lineage.

  • 1

    Each booking carries its commission rule and distribution chain — lineage end-to-end.

  • 2

    Settlement is atomic and idempotent; statements, settlements, and payments reconcile as a read.

  • 3

    Wallet movement is transactional, pessimistically-locked, and idempotency-keyed.

  • 4

    Settlement audit is append-only — history is never updated.

PILLAR 05Audit

Append-only. Nothing edited silently.

  • 1

    Append-only capture of governance, inventory, cancellation, and settlement decisions.

  • 2

    Operational incidents are deduped (by source, category, entity, correlation), classified, and queryable.

  • 3

    Alerting is config-driven and never throws into business flow.

  • 4

    Read-only ops APIs expose governance, inventory decisions, and cancellation per booking.

Connectivity

Alongside your PMS — never instead of it.

Escapra reads what the PMS authoritatively exposes and writes bookings and cancellations back. The PMS remains the system of record for property, inventory, and reservations. Generic categories: cloud-native, enterprise & chain, independent & lifestyle, on-premise & regional. Public partner names appear only with written consent.

See the platform in action.

A walk-through using your property, your scopes, or your integration profile. Free to connect. 2% on confirmed bookings.