How it works
Seven layers, one path for every request.
People and AI agents act through applications. Every request passes the same gateway and the same checks before a business service changes anything — and every change is recorded and published as an event.
01
Actors
People, AI agents and connected systems.
02
Applications
Public web, portals, Momin OS and the communication apps.
03
Edge and gateway
Routing, rate limits and authentication.
04
Checks
Identity, tenant, permission and validation before anything changes.
05
Business services
33 services in seven families.
06
Events
Every change published so other services can react.
07
Records
One ledger and one append-only audit trail.
One client journey, end to end
Controls that make AI safe to use
Deny-by-default authorisation
Every action is checked against a named permission such as sales.proposal.approve.
AI boundary
Data is filtered by the user's permissions before any AI model sees it; agents act as limited users.
Human approval
Business actions by AI need confirmation; sensitive and critical actions need human approval.
Audit
Every significant action is written to an append-only audit log.
Where it stands and where it goes
The whole platform is described in a full specification library. A first version exists as source code and is being made to run and tested. Nothing is deployed and there are no live users today — the accurate label is pre-alpha, source only.
- 01
Phase 0 — Foundation
Make the platform run: backend start, migrations, web app, deployment.
- 02
MVP
Private pilot: identity, content, booking, CRM, projects and payments.
- 03
V1 — Business OS
Full operating system across the seven service families.
- 04
V2 — Intelligent Ecosystem
AI assistant and agents, AI search, knowledge graph, analytics, public APIs and mobile.
- 05
Enterprise — Multi-tenant platform
Full SaaS multi-tenancy, SSO, enterprise security and finance, developer platform and marketplace.