Identity and tenancy
Users, organisations, workspaces, authentication, roles and isolation.
Rihuum Master Enterprises
One governed enterprise core for every authorised Rihuum product.
RME prevents each product from rebuilding identity, tenancy, policy, workflow, commercial controls, integrations, audit and support. Sector products reuse the foundation while preserving their own domain logic.
Current release status
RME is a controlled foundation in development. Public availability, service levels and client migration commitments require a documented release and readiness review.
Shared services
Build once. Govern centrally. Extend deliberately.
Every module has a versioned contract, documented owner and compatibility path so the product family can evolve without a full rebuild.
Policy and approvals
Authorisation, duties, approval paths, limits and controlled exceptions.
Enterprise records
Shared customers, people, assets, catalogues and governed master data.
Workflow and automation
Tasks, states, rules, schedules, notifications and human-controlled actions.
Commercial controls
Plans, entitlements, subscriptions, licensing, billing events and usage policy.
Integration and audit
Versioned APIs, adapters, events, evidence, support and lifecycle traceability.
Control rule
RIA and every product must pass through RME.
AI models, agents and tools may never bypass tenant boundaries, identity, entitlements, approval, data policy, commercial controls or audit. Architecture exceptions require documented approval and a lifecycle plan.
See the Rihuum OS experience ↗ExperienceRihuum OS · sector products · portals
IntelligenceRIA knowledge · models · agents · tools
Enterprise coreRME identity · tenancy · policy · workflow · audit
InfrastructurePortable runtime · data · storage · observability · recovery