SaaS administration
Tenant and property provisioning, subscriptions, entitlements, seat-limited membership records and period-based usage controls inside the protected workspace.
Hospitality intelligence platform
A governed hospitality operational core connecting SaaS administration, central reservations, physical rooms, stay and folio workflows, finance, procurement, stock and accountable provider readiness.
Internal SaaS, reservation, folio, finance and procurement workflows are implemented in the protected application. Booking.com, Expedia, Agoda, Airbnb, payment gateways and property hardware still require provider onboarding, released adapters, authenticated testing, reconciliation and production acceptance before activation.
Release evidence
RAHIS separates internal records, externally evidenced payments and provider connectivity so an operational workflow is never mistaken for a bank settlement, provider certification or live integration.
Tenant and property provisioning, subscriptions, entitlements, seat-limited membership records and period-based usage controls inside the protected workspace.
Server-priced reservations, guarded inventory, physical rooms, assignment, check-in, folios, independently confirmed payment evidence and zero-balance checkout.
Chart-of-account masters, append-only balanced journals, supplier and stock masters, controlled purchase orders, goods receipt, supplier bills and payments.
Encrypted immutable configuration revisions, credential rotation, mapping checks, test records, maker-checker approvals and a hard-disabled live-activation guard.
Memberships do not yet provision tenant logins; usage is not automatic billing; provider records are not live adapters; and wider hospitality modules remain separately released.
Product architecture
The module families below describe the long-term product architecture. The release evidence above—and the exclusions stated on this page—define what v8.1 currently implements.
Provider-readiness governance
Configurations, mappings and credentials are encrypted server-side. Test attestations and independent approval decisions are retained against the reviewed versions. These records are not represented as live connections, and none of this activates a network adapter.
Requires Booking.com connectivity-partner onboarding, property permission and provider certification.
Requires Expedia Group lodging connectivity onboarding, certification and production credentials.
Requires Agoda connectivity approval, property identifiers, test access and certification.
Available only through Airbnb-approved software-partner access and applicable host/property permissions.
The selected channel manager must be added to the server-side endpoint allowlist before testing.
Use server-side transaction initialisation and verification. RAHIS never stores card number, CVV, PIN or OTP.
Requires merchant onboarding, API-version selection and verified webhook signatures.
Requires an approved Squad merchant account, current integration specification and production credentials.
Requires merchant onboarding and the approved Interswitch product/API profile.
Private-LAN terminals require an outbound property bridge. A public cloud service cannot safely dial a hotel private IP.
Each supported device model and firmware requires an approved local adapter, outbound TLS and an operational fallback.
Requires Meta business verification, approved templates and customer messaging consent.
Use a dedicated transactional mail account with SPF, DKIM and DMARC alignment.
Restrict API keys by application, domain, API and quota before production use.
Requires a reviewed accounting mapping, fiscal controls and endpoint allowlisting.
Commercialisation path
RAHIS is designed for hotels, resorts, aparthotels, restaurants, event venues and hospitality groups. Each customer receives a governed tenant, property scopes, a plan, entitlements and an accountable release path. Tenant-facing membership login, automatic metering and subscription collection remain future controlled releases.
Request a RAHIS discovery