One engine, a registry of integrations.
A connector is the engine plus its configuration — a named, mutable instance per integration. One property can run many.
Statuses published honestly.
What the layer enables, level by level.
The adoption ladder in one line: hotels adopt in six levels, L0–L5 — Watch (L0–L2) observes, Translate (L3–L4) speaks the shared model, Act (L5) applies custom rules. The full ladder lives on the adopt page.
Message analysis, live views, and apps built on the ordered event feed: every message across every seam, on record and searchable, with cross-system and cross-property views on live data.
Connect anything to anything through the shared model. Credentials live in one managed vault — vendors never see them.
Amend, enrich, and route data in flight, by rule — only where the hotel says so.
A sales system fires the parts of a group booking near-simultaneously and the PMS needs them in order — a routing rule holds the set until it is complete, then forwards it in sequence.
A guest taps a keycard at a restaurant terminal — a rule resolves the tap to a room number via the keycard system’s event and injects it into the POS transaction, enabling a room charge the POS could not build alone.
Capability belongs to the layer; products on top of it — the portal, mini apps — belong to the implementers.
Who builds a connector decides how open it starts.
Rule of thumb: an open vendor API means the translation is open-sourced; an API closed under NDA can't be. Today every running connector is built by Niji Labs — to be released under Apache-2.0 at the published gate.
The translation joins the commons for every deployment to use.
Permitted — commercial work on top of the core is the business model.
Always open.