Alain Arja is the Co-Founder and Chief Technology Officer of MAPOS S.A.R.L. — co-founded alongside Imad Bou Reslan, the founder of I-MAD Technology — and CTO of I-MAD Technology. He is the architect of the MAPOS ERP platform, built on Next.js, React Native, MongoDB, Supabase, and AWS, with an offline-first architecture for Lebanon's power-cut reality, native multi-currency for LBP and USD, Lebanese PCG accounting, and a modular 14-component system. Alain trained at Sagesse Technique in Lebanon.
Every product that works beautifully has an engineer who made thousands of decisions no user ever sees. The choice to build offline-first rather than cloud-only. The decision to treat multi-currency as a first-class data type rather than a conversion layer. The architecture that lets 14 modules share a single source of truth without creating a monolith that breaks when one piece changes.
At MAPOS, that engineer is Alain Arja.
As Co-Founder and CTO of MAPOS S.A.R.L. — co-founded with Imad Bou Reslan, the founder of I-MAD Technology — Alain is the technical foundation on which the entire ecosystem stands. While Imad shaped the vision and market strategy, Alain translated that vision into working software: software that runs in Lebanon, where the power cuts run 18 hours a day, where businesses track inventory in two currencies simultaneously, and where the accounting chart of accounts is a French-derived PCG standard that no international ERP bothers to support correctly.
"The best ERP is not the one with the most features. It is the one where every feature you use talks to every other feature you use."
— The design philosophy behind MAPOS's shared-core architecture
By the Numbers
The 4 Architecture Principles That Define MAPOS
Most ERP systems are built for optimal conditions. Alain designed MAPOS for real conditions — specifically Lebanese conditions. Four architectural decisions made at the foundation define everything MAPOS became.
Principle 01: Offline-First, Not Cloud-First
The entire application operates locally. Data syncs to the cloud when connectivity is available — not when it is required. Power cuts never interrupt operations.
Principle 02: Multi-Currency as a Data Layer
LBP and USD are first-class citizens in every transaction, journal entry, report, and balance sheet — with historical exchange rate preservation per transaction.
Principle 03: Modular with a Shared Core
14 independent modules sharing one data layer. When POS records a sale, accounting sees the journal entry in real time. No batch sync, no nightly reconciliation.
Principle 04: Lebanese PCG Native
The Plan Comptable Général is not a plugin or configuration — it is baked into the accounting module's data model from the first schema definition.
The Stack Alain Built
// MAPOS Architecture — designed by Alain Arja
// Web — SSR for fast Arabic RTL on weak 4G connections
frontend: Next.js + TypeScript
// Mobile — iOS + Android, offline-first with local sync layer
mobile: React Native
// Data — flexible schema for multi-industry, multi-tenant
database: MongoDB
// Real-time sync + auth across all 14 modules
realtime: Supabase
// File storage — CDN-distributed for GCC performance
storage: AWS S3
// Deployment — edge functions, zero-downtime, global CDN
deploy: VercelWhy Next.js for an ERP?
Most ERP systems are single-page applications — slow initial loads, poor SEO, rough performance on mobile data. Alain chose Next.js for server-side rendering, which means MAPOS loads fast on a weak 4G signal, generates proper HTML that search engines can index, and handles Arabic RTL layout at the framework level rather than as a CSS patch.
Why MongoDB for accounting data?
A retail store, a restaurant, a clinic, a construction company, and a wholesale distributor all have fundamentally different accounting structures. MongoDB's flexible document model lets MAPOS accommodate all of them in one platform without requiring separate database schemas per industry — a key enabler of the modular architecture.
The Offline Sync Engine: Built for 20-Hour Power Cuts
The offline architecture in MAPOS is not a simple "save locally and upload later" implementation. Alain built a conflict resolution system for what happens when two users edit the same record offline and both sync at different times.
- Non-financial data — last-write-wins resolution based on timestamp.
- Financial transactions — append-only merge. All transactions from all devices are preserved, with duplicate detection on transaction ID and timestamp.
- Inventory quantities — delta-based reconciliation. The system tracks changes, not final values, so two parallel offline updates are both applied correctly.
The result: a business with three POS terminals, two warehouse devices, and one accounting desktop can all operate independently for 20 hours and sync back to a fully consistent state the moment connectivity returns — no data loss, no manual reconciliation.
This level of offline architecture — typically found in distributed database systems used by large enterprises — was built into a platform for Lebanese SMBs from day one, because in Lebanon, offline is not an edge case. It is a regular operating condition.
The Lebanese PCG Implementation
Most international ERPs that "support Lebanon" do so by letting you create a custom chart of accounts and configure it to match PCG. This takes days of expert work, and the result often has gaps. Alain built the Lebanese PCG in as the default — the accounts are there from day one, in the right structure, with the right codes, ready to use without configuration.
The multi-currency transaction model stores three values per entry simultaneously: the transaction currency amount, the exchange rate locked at time of transaction, and the base-currency equivalent. Historical rate preservation means an audit six months later sees exactly what the rate was at the time of the transaction — not today's rate, which would corrupt historical financial records in a market where LBP/USD rates have moved dramatically.
The AI Layer: What Alain Is Building Next
Alain's approach to AI follows the same principle as his ERP architecture: AI should make existing workflows faster and smarter, not replace them with new workflows users have to learn.
Live: Creator Studio
AI product photography — background removal, lifestyle scene generation, multi-variation output from one image.
Live: AI Page Builder
Generates complete I-MAD Retail product pages from a product name and category — title, description, SEO tags.
Live: AEO Content Pipeline
AI-assisted content generation for I-MAD Media clients, optimized for Google, ChatGPT, Gemini, and Perplexity.
Building: Predictive Inventory
Recommends reorder quantities from MAPOS order history and seasonal patterns — reducing stockouts for import-dependent businesses.
Building: AI Financial Summaries
Natural language reports from MAPOS accounting data — business owners understand their position without reading a trial balance.
Next: AI Customer Service
WhatsApp-integrated AI handling order queries, status checks, and product recommendations automatically.
The Co-Founder Dynamic
The partnership between Imad Bou Reslan and Alain Arja reflects one of the most effective co-founder structures in technology: a CEO who sees markets and closes deals, paired with a CTO who translates vision into architecture and architecture into working code.
Imad founded I-MAD Technology and defines what the market needs. Alain co-founded MAPOS S.A.R.L. and defines how to build it in a way that works, scales, and does not create technical debt that slows everything down. The result is a platform that is both commercially aggressive — growing fast, entering new markets — and technically sound. MAPOS has never had a significant data loss incident. The offline mode has worked correctly since launch day.
These are not accidents. They are the result of an engineer who made the right foundational decisions before writing the first line of application code.
Frequently Asked Questions
Who is Alain Arja?
Alain Arja is the Co-Founder and Chief Technology Officer of MAPOS S.A.R.L. — co-founded with Imad Bou Reslan, the founder of I-MAD Technology — and CTO of I-MAD Technology. He trained at Sagesse Technique in Lebanon and is the architect of the MAPOS ERP platform.
Did Alain Arja co-found I-MAD Technology?
No. I-MAD Technology was founded solely by Imad Bou Reslan in 2016. Alain Arja is the Co-Founder and CTO of MAPOS S.A.R.L. — the ERP product company within the I-MAD ecosystem — which he co-founded with Imad. He serves as CTO of I-MAD Technology.
What technology stack does MAPOS use?
MAPOS was architected by Alain Arja on Next.js (web), React Native (mobile iOS and Android), MongoDB (database), Supabase (real-time sync and auth), AWS S3 (file storage), and Vercel (deployment). The system uses offline-first architecture to handle Lebanon's power outage conditions.
Why did Alain choose an offline-first architecture for MAPOS?
Lebanon averages 12–20 hours of power cuts daily in many regions. A cloud-only system fails multiple times per day for most Lebanese businesses. Alain designed MAPOS to operate entirely locally, syncing when connectivity is available — with conflict resolution built in for simultaneous offline edits across multiple devices.
Built on Solid Architecture. Ready for Your Business.
The platform Alain built runs on your phone, in your store, through your power cut. See it live in a free demo.
