People, users, verification, sessions, roles and scoped access.
Enterprise platform foundation
The CoreBuild the business application. Reuse the foundation.
Identity, security, organization, data protection, workflow, operations and shared application services form one trusted platform layer—so new products can focus on the business domain instead of rebuilding infrastructure.
Reusable by designSecure by defaultMulti-language & RTLModular & extensible
Policies, profiles, scoped authorization and information protection.
Entities, branches, units, locations, brands and memberships.
Trusted history for events, changes, errors and sensitive operations.
Health, backup, maintenance, retention and monitoring foundations.
APIs, shared modules and independently evolving domain applications.
Built for what matters
One foundation, many business applications.
The Core separates stable enterprise capabilities from domain-specific business logic. Each new application inherits the same identity, access, organization, audit and operational foundations.
Core foundation
Runtime, configuration, localization, logs, monitoring, backup and trust primitives.
Identity & security
People, users, authentication, MFA, permissions, scopes and information protection.
Shared modules
Organizations, notifications, files, workflow, contracts, payments and repeated services.
Business applications
Booking, finance, gaming, clinics, CRM, inventory or any new domain with its own rules.
Product vision
See what the platform can become.
These are illustrative future-state interfaces—not claims that every module is already complete. They show how a consistent experience can span light, dark and Arabic/RTL views.
Featured enterprise command views
High-fidelity views of the platform at enterprise scale.
These are the primary visual direction for the public showcase, using illustrative data to demonstrate disciplined tables, metrics, approvals and operational context.
Additional module concepts
Broader module and experience coverage.
These supporting concepts preserve coverage for booking, gaming, inventory, CRM, analytics and Arabic/RTL until each receives the same high-fidelity treatment.
Arabic-first capability
RTL is a product experience, not a translation afterthought.
The same model can present Arabic workflows, tables, metrics and navigation with correct direction, hierarchy and terminology.
The Core · الهوية+ إضافة شخص
الأشخاص1,284
الحسابات النشطة846
بحاجة إلى مراجعة12
| الشخص | الموقع | الوصول |
|---|---|---|
| أحمد المنصوري | أبوظبي | نشط |
| سارة الهاشمي | دبي | مستخدم |
| عمر حسن | عمّان | بدون دخول |
The Core · المنظمةعرض الهيكل
الفروع18
الوحدات63
المواقع27
| الوحدة | المدينة | الحالة |
|---|---|---|
| المكتب الرئيسي | أبوظبي | نشط |
| فرع العمليات | العين | نشط |
| مركز الأبحاث | دبي | متخصص |
The Core · الماليةتقرير جديد
الإيرادات4.82M
المصروفات3.11M
معلّق18
Model design & reasoning
What belongs in the Core—and what belongs in the application.
The boundary is deliberate. Shared trust and platform services live in The Core; the rules that make a booking system, game, clinic or finance product unique stay inside that domain application.
Identity & Access
Stable natural-person identity with separate user accounts and fully auditable access.
The Core owns: People, users, authentication, MFA, sessions, permissions and protected identity.
Application owns: Customer, patient, player or employee profiles that are specific to a domain.
Why: One person can participate in many applications without duplicating core identity.
Organization & Locations
Reusable enterprise structure from legal organizations through branches, units, locations and brands.
The Core owns: Organizations, units, branches, locations, memberships and scope structure.
Application owns: Operating rules that are unique to the activity performed at each branch or location.
Why: Security, reporting and settings can all rely on the same organizational truth.
Security & Information Protection
One trust layer for roles, exceptions, scoped access and information classification.
The Core owns: Security profiles, permissions, explicit deny, classification, clearance and audit.
Application owns: Business decisions such as who approves a request or manages a particular event.
Why: Protection rules should not be reinvented independently by every product.
Requests & Workflow
Shared patterns for request state, transition, approval, escalation, ownership and decision history.
The Core owns: State/audit primitives, notifications, ownership patterns and common workflow infrastructure.
Application owns: Request types, steps and domain-specific approval rules.
Why: The experience stays consistent without forcing every product into one business process.
Notifications & Communications
Central delivery for alerts, messages, priority, channels, preferences and delivery history.
The Core owns: Channels, templates, preferences, delivery records and secure deep links.
Application owns: When and why a domain sends a message and the business meaning of that event.
Why: Delivery infrastructure is separated from domain intent.
Finance & Reporting
A common financial foundation that can support products needing ledgers, payments and reporting.
The Core owns: Shared accounting/payment primitives, audit, controls and reporting foundations.
Application owns: Pricing, commissions, fees, products and economics unique to a domain.
Why: Applications gain consistent financial control while preserving domain-specific economics.
Booking & Scheduling
A specialist domain that reuses people, locations, notifications, payments and permissions.
The Core owns: Identity, locations, access, notifications, payments and audit.
Application owns: Resources, availability, reservations, conflicts and scheduling policy.
Why: Booking is a business domain—not part of the platform identity model.
Inventory & Assets
Track stock, assets and movement across locations with full organizational context.
The Core owns: Identity, locations, access, audit and document linkage.
Application owns: Stock types, reorder rules, domain movements and valuation rules.
Why: Trust and locations are reusable even when inventory logic differs dramatically by industry.
CRM & Relationships
Customer relationships, interactions and opportunities built on top of clean identity.
The Core owns: Person, entity, organization, contact, access and audit foundations.
Application owns: Pipelines, opportunity stages, campaigns and follow-up policy.
Why: CRM should not become a second contradictory source of identity truth.
Gaming & Engagement
A highly specialized example that reuses the foundation without pushing game logic into it.
The Core owns: Accounts, access, notifications, payments, audit and common analytics.
Application owns: Players, teams, tournaments, matches, rewards and in-game economy.
Why: The Core stays generic while a game can evolve quickly and independently.
Operations & Monitoring
Consistent operations for every application: health, backup, errors, schedules and retention.
The Core owns: Health, errors, backup, maintenance, retention and monitoring foundations.
Application owns: Operational signals meaningful only inside the domain.
Why: Every product inherits a dependable operational baseline.
Analytics & Intelligence
A shared context for trusted events and common dimensions, with domain-specific metrics layered above.
The Core owns: Trusted events, common dimensions, policy and reporting access.
Application owns: Metrics, models, forecasts and success definitions unique to the domain.
Why: Analytics needs shared context without limiting each domain’s definition of insight.
Build the application. Reuse the foundation.
Enter the current Core demo, or explore the UAE-specific platform vision.