01
Applications
Public Experience, R GLOW, Storefront, Customer Portal, Owner Portal, and Platform Admin.
RINADS Cloud
The shared foundation behind the operating platform.
RINADS Cloud connects identity, tenancy, domain services, runtime, data, APIs, integrations, and infrastructure so multiple business experiences can operate on one platform core.
02
Identity + tenant context
Authentication, organization membership, active-org resolution, and tenant-aware access.
03
Domain services
Commerce, operations, salon, platform, billing, domains, CMS, and intelligence packages.
04
Runtime
Business events, workflows, jobs, approvals, retries, workers, and notification outbox.
05
Data + storage
PostgreSQL/Supabase-backed schema, RLS foundations, files, and structured business data.
06
Infrastructure
Deployment, integrations, APIs, cron/worker execution, and provider adapters.
Request path
Business operations move through identity and tenant context before domain work.
The exact path varies by product, but the platform architecture separates user/session context from domain services and runtime side effects.
- User / product
- Identity
- Tenant context
- Domain service
- Event / workflow
- Data
Runtime
Events and workflows connect domain state to reliable execution.
Business events
Carry correlated platform state changes into runtime processing.
Workflow executions
Track one workflow run and the status of its ordered steps.
Approval gates
Pause eligible workflow steps until the required approval path continues them.
Outbox
Queue customer and operational notifications with deduplication and delivery status.
Platform controls
Trust is implemented as boundaries, not marketing badges.
Tenant isolation
Commerce and operations have tenant-scoped RLS/security tests and organization-aware service patterns.
Runtime orchestration
Workflow executions and step runs model queued, running, waiting, completed, failed, cancelled, and dead-letter states.
Approval-aware steps
Workflow steps at or above the configured approval risk threshold can pause in a waiting-for-approval state.
Reliable notification queue
The notification outbox tracks pending, processing, sent, and failed delivery attempts with idempotency and correlation fields.
Model-provider boundary
Keep model providers replaceable behind the RINADS intelligence boundary.
The current platform already separates business tools and runtime controls from model choice. As LLM depth expands, model providers should remain replaceable implementation choices; permissions, tenant context, tools, approvals, and audit belong to RINADS rather than to an external model.
Explore RINADS IntelligenceRINPO / product request
User intent and current product context
RINADS Intelligence
Policy, tool selection, context, recommendations
Model / inference adapter
Replaceable compute provider
Registered tool / runtime
Governed business-side execution path
Current boundaries
Clear boundaries between what is available, configured, and still in progress.
Some external provider connections still need live credentials before production use.
Public RINPO demo chat is distinct from authenticated product-side intelligence and tool execution.
Some workflow definitions are still evolving toward fully configurable, organisation-managed runbooks.
Availability statements on this site reflect implemented product posture — not roadmap aspirations alone.
One shared platform foundation.
RINADS Cloud supports the operating systems, RINADS Intelligence, and product experiences through shared identity, domain, runtime, data, and infrastructure layers.