Platform
One architecture from data to decision.
A connected platform that transforms fragmented operational information into governed, auditable, decision-grade intelligence.
Architecture
A shared foundation, not a collection of point solutions.
Every Yaqīn product works from the same meaning layer and operating model. This preserves identity, context, lineage, and policy as intelligence moves across systems, teams, and decisions.
Workloads
Sirāj · Mīzān · Nūr · Falak
Purpose-built experiences for intelligence, enterprise decisions, governed AI, and space-and-signals workflows.
Semantic foundation
Naẓm · نظم
A bilingual ontology connecting policy, evidence, people, assets, transactions, events, and decisions.
Operational backbone
Bunyān · بنيان
A unified control plane to deploy, observe, govern, patch, and operate every platform workload.
Infrastructure
Sovereign by design
Deployment across in-Kingdom data centres, sovereign cloud, edge, dedicated, and isolated environments.
Naẓm ontology
Meaning, lineage, and accountability built in.
Naẓm creates a shared, bilingual model of the organization. It makes institutional concepts machine-readable while preserving the definitions, sources, relationships, and permissions that give them authority.
Decision lifecycle
A governed path from source to action.
The architecture preserves context and control from the moment a source connects through to approved action and its record.
Ingest
Connect structured and unstructured sources while preserving ownership and classification.
Model
Map information to Naẓm so systems share an operational language.
Reason
Apply analytics, models, rules, and agents within explicit policy boundaries.
Review
Present evidence and uncertainty to the accountable human decision-maker.
Act
Return approved actions to workflows and retain the complete decision trail.
Governance
Governance that travels with the intelligence.
Identity, permissions, provenance, model configuration, evaluations, approvals, and operational telemetry remain part of the workflow—not a separate compliance exercise. This makes every important output explainable in its operating context.