Multi-tenant by design
Business identity, roles, branding and configuration are tenant-scoped rather than hard-coded around one operator.
HalNora Platform · shared foundation
One platform.
Clear authority underneath every product.
HalNora Platform centralizes what should be shared—identity, security, events, audit, integration infrastructure and selected capabilities—while keeping each product authoritative for its own workflow and data.
Product domainsDispatch · Marketplace · POS · Booking · Communications · CRM · Accounting · Inventory · Payroll · Payments · HR · Pharmacy↕Versioned contractsAPIs · Events · Tenant context · Audit · Idempotency · Reconciliation↕Shared platformIdentity · Security · Inventory · Fleet · Data · Payments · Notifications
Architecture principles
Designed to scale without becoming tangled.
The platform exists to reduce duplicated infrastructure—not to erase product boundaries.
Clear domain ownership
The product that creates a business record owns its lifecycle and decisions. Other products receive only the contract they need.
Versioned APIs & events
Cross-product changes use explicit authenticated interfaces and events rather than direct table access.
Identity, roles & sessions
Shared identity can support multi-role and multi-product businesses while products keep domain-specific permissions and short-lived protected access.
Audit & evidence
Operational history, exports, attachments and evidence are designed to remain attributable and reviewable.
Idempotency & retries
Important handoffs are retry-safe so network or integration failures do not duplicate business actions.
Offline-aware execution
Field products distinguish pending device actions from server-confirmed state and reconcile against the authoritative source.
Provider-neutral integrations
Maps, payments, pharmacy, video/VMS and other integrations avoid assuming one provider forever.
Clean releases & rollback
Immutable releases, cache/build identity, verification and rollback are part of the deployment model.
Backup & recoverability
Independent backup/restore and disaster-recovery readiness are treated as product release gates where authoritative business data is involved.
HalNora One workspace
Shared business context is moving from architecture into implementation.
The workspace foundation now supports catalogue visibility, shared business/staff context, business switching and permission-aware access to connected surfaces.
Connected where verified.
Dispatch, Driver and Merchant links can be exposed by permission today in the development workspace. CRM, Payroll, Pharmacy and other standalone products stay separate until their identity and onboarding contracts pass end-to-end validation. This prevents a marketing promise of “one login” from outrunning the engineering.
Shared capabilities
Reuse capability without turning everything into one product.
The platform provides reusable services and integration contracts without taking over product authority. Inventory and Payments are maintained as standalone products where stock and payment orchestration require their own control boundaries.
Identity & RBAC
Tenancy
Communications
Notifications
Files & evidence
Audit
Locations
Scheduling
Resource capabilities
Fleet & inspections
Integrations
Payment integration contracts
Business events
Data & migration
Inventory integration contracts
Tracking & ETA
Offline sync
Scanning & load management
Ownership example
The same business action can cross products without losing authority.
A Marketplace order can trigger POS/KDS preparation, Inventory movement and Dispatch fulfillment while Marketplace remains the commercial-order owner. Accounting can later receive an approved business event without becoming the source of the original sale.
MarketplaceCommercial order
→POS / InventoryPreparation & movement
→DispatchExecution