Skip to main content
RihuumCompany
Rihuum websites
Discuss a requirement

Work and evidence

Release status before presentation.

Rihuum separates work that is publicly operating from controlled releases, internal platforms, documents and future directions. This register is designed to make that difference reviewable.

Evidence boundary

A public URL proves that a release can be reached; it does not by itself prove every provider, integration, payment method, client installation or operational claim. The evidence note states the verified boundary.

Public production

Releases available for direct inspection.

These entries are recorded as public production in the current portfolio register.

  1. 01

    Rihuum Digital Ecosystem

    Enterprise platform

    Public Sites deployment and rihuum.com product register reconciled on 24 August 2026; the register covers 36 evidence-labelled products and preserves release, access and commissioning boundaries

    Inspect public release
  2. 02

    RAHIS — Sandralia Hotel Edition

    Hospitality operations

    Public Sites deployment recorded at version 17 with its conventional favicon and checked production dependencies verified; public integration routes are configured for controlled staging, while custom-domain TLS, Namecheap installation, OTA, payment, hardware and operational acceptance remain blocked

    Inspect public release
  3. 03

    Sandralia Hotel by White Stones

    Hospitality and tourism

    Public Sites deployment remains recorded at version 19 with the exact Rihuum development credit, metadata assets and conventional favicon path verified. A newly packaged Namecheap installation bundle received on 17 August 2026 has a matching external SHA-256 record and valid ZIP structure; its clean source passes 12 verification controls and 17 independently rerun Node tests. The bundle is still the SH-WEB-1.0.0-RC1 pre-release—not a live replacement or production verification—and its own release status prohibits that classification. It requires cPanel Node.js 22.16 or later, still uses Node/SQLite with only a partial MySQL schema, omits the exact development-credit literal and does not retain the complete governed payment catalogue. Live migration, merchant, SMTP, PMS/CRM, content reconciliation, accessibility, security, legal, UAT, rollback and commissioning evidence remain absent

    Inspect public release

Controlled product evidence

What exists without overstating public access.

These records describe an internal release, governed workspace or managed service. They are not presented as unrestricted public products.

  1. 01

    Rihuum Master Enterprises

    • RME
    • Controlled internal release
    • Authorised owner workspace

    Controlled commercial, work and support records for Rihuum operations.

    Evidence reviewed 4 August 2026.

    Review product record
  2. 02

    Rihuum AI Hospitality Intelligence Suite

    • RAHIS
    • Controlled operational core
    • Authorised workspace

    Hospitality memberships, reservations, folios, finance and procurement controls.

    Evidence reviewed 4 August 2026.

    Review product record
  3. 03

    Rihuum Data Intelligence Studio

    • INSIGHT
    • Managed service
    • Scoped engagement

    Data quality, KPI design, dashboards and decision support delivered as a managed engagement.

    Evidence reviewed 4 August 2026.

    Review product record
  4. 04

    Rihuum OS

    • OS
    • Controlled owner release
    • Authorised workspace

    A protected operating experience for governed Rihuum workflows and configuration.

    Evidence reviewed 4 August 2026.

    Review product record

Publication standard

Four fields every work claim should answer.

The company register can expand, but these evidence requirements remain constant.

  1. 01

    State

    Whether the work is public production, a controlled release, a deliverable, an architecture or only a registered direction.

    Required for publication
  2. 02

    Access

    Who can inspect or use the work today, without implying broader availability.

    Required for publication
  3. 03

    Evidence

    What was actually verified, on what date where available, and which material limitations remain.

    Required for publication
  4. 04

    Boundary

    Credentials, providers, integrations, acceptance or operating work that has not been completed.

    Required for publication

Need evidence for a specific capability?

State the product, capability, intended use and assurance you require. Rihuum will confirm what can be provided and what remains controlled or unavailable.

Request evidence