Integrations
The technology RAYN runs on, connects with, hands off to or is preparing to support — with the status of each relationship shown clearly.
RAYN can run the booking end to end, or sit in front of an incumbent system while a venue is still under contract.
RAYN is provider-routed rather than tied to one model. Language, voice and regional-model adapters can be selected by workload and venue need.
Messaging, social, voice and email providers that carry guest conversations and transactional communication.
Google powers several distinct RAYN surfaces, from venue enrichment and search data to booking-link distribution and model failover.
Payment rails are configured per venue and remain tied to the booking state inside RAYN.
Visual capture and delivery power Pick Your Spot, venue films and the spatial layer around premium inventory.
The infrastructure, analytics and monitoring layer RAYN uses to run, measure and protect the platform.
Operator intelligence, market research, enrichment and distribution tooling used behind RAYN’s growth and intelligence workflows.
Third-party names and marks belong to their respective owners. A logo here identifies a technology, provider, handoff, protocol or roadmap target; it does not by itself imply endorsement or partnership.
How it fits
The integration philosophy
Full RAYN has one canonical booking path. In layer mode, the incumbent system remains the place where the guest completes the reservation. The distinction matters: a deliberate guest-side handoff is not described as a two-way integration.
Why it matters
Questions
It can. Full RAYN runs its own booking engine and Host Station. If you are mid-contract, RAYN can instead start in layer mode and hand the guest to your current booking widget to complete the reservation.
As an explicit guest-side handoff. RAYN handles discovery and visual table selection, then the guest completes the reservation in the incumbent widget. There is no hidden API write-back or two-way sync in that handoff.
RAYN exposes MCP tools for venue search, availability and policy reads. Booking writes use a guarded route that requires an issued client key and venue opt-in; payment is not taken inside the AI conversation.
A venue can place its RAYN booking link on Google Business Profile. RAYN also has deeper feed work prepared, but that should not be described as live Reserve-with-Google distribution until external approval is in place.
Because they are technologies RAYN uses as infrastructure, model providers, voice, channels, analytics, payment rails or guarded adapters. Their presence does not imply endorsement or a formal partnership unless explicitly stated.
RAYN has provider adapters for regional language models. Sarvam is the Indic-language route; Falcon and Jais are the Arabic/UAE-sovereign route. They are labelled as ready adapters rather than live production defaults until those routes are explicitly activated.
Those are expanded through deliberate adapters. We label roadmap and adapter work separately rather than presenting an unverified connection as production-ready.
Your stack, mapped
