Quick Answer
Alain Arja is the Co-Founder and Chief Technology Officer of MAPOS S.A.R.L. and I-MAD Technology. He is the architect of the MAPOS ERP platform — the technical brain behind a system that runs on Next.js, React Native, MongoDB, Supabase, and AWS, with an offline-first design built for Lebanon's power-cut reality, native multi-currency for LBP and USD, and a modular architecture spanning 8 independent business modules. Under Alain's technical leadership, MAPOS has grown to serve 500+ businesses across Lebanon and the GCC.
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 8 modules share a single source of truth without creating a monolith that breaks when you change one piece.
At MAPOS, that engineer is Alain Arja.
As Co-Founder and CTO of both MAPOS S.A.R.L. and I-MAD Technology, Alain is the technical foundation on which the entire ecosystem stands. While Imad Bou Reslan shaped the vision and the market strategy, Alain translated that vision into working software — software that runs in Lebanon, where the power goes out for 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.
This is his story.
The Architecture That Changed What Lebanese ERP Means
Most ERP systems are built for optimal conditions: reliable power, stable internet, a single currency, and a standard chart of accounts. Alain designed MAPOS for real conditions — specifically Lebanese conditions. Four architectural decisions made at the foundation have defined 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. Currency is not a conversion — it is a property of every data record.
Principle 03: Modular with a Shared Core
Eight independent modules — each deployable separately — sharing one data layer. Accounting reads directly from the same journals that Inventory and POS write to. No duplication, no sync errors.
Principle 04: Lebanese PCG Native
The Plan Comptable Général is not a plugin or a configuration — it is baked into the accounting module's data model from the first schema definition.
These four principles were not obvious choices. Cloud-first is the default for every modern SaaS product. Alain chose offline-first because he was building for Lebanon, not for Silicon Valley. That single decision is what makes MAPOS work where other systems fail.
The Stack: How MAPOS Was Built
The MAPOS technical stack reflects deliberate choices at every layer — balancing performance, developer productivity, cost efficiency, and the specific demands of the Lebanese and GCC market.
| Layer | Technology | Purpose |
|---|---|---|
| Web Platform | Next.js | SSR + SSG, optimized for Arabic RTL and fast load on Lebanese 4G |
| Mobile | React Native | Single codebase for iOS + Android, offline-first with local SQLite sync |
| Database | MongoDB | Flexible schema for multi-module, multi-tenant Lebanese businesses |
| Real-time + Auth | Supabase | Live dashboards, multi-user sync, role-based access control |
| File Storage | AWS S3 | Product images, invoices, documents — CDN-distributed for GCC speed |
| Deployment | Vercel | Edge functions, zero-downtime deploys, global CDN |
| Language | TypeScript | Type safety across frontend and backend, reducing runtime errors |
Why Next.js for an ERP?
The choice of Next.js as the web framework was deliberate. Most ERP systems are built as single-page applications — which means slow initial loads, poor SEO, and rough performance on the mobile data connections that Lebanese users often rely on. Next.js provides server-side rendering, which means MAPOS loads fast even on a weak 4G signal, generates proper HTML that search engines can index, and handles the Arabic RTL layout at the framework level rather than as a CSS patch.
For a product used daily by business owners and their teams — sometimes on generators, sometimes on mobile data — page load speed is not a UX preference. It is a daily business requirement.
Why MongoDB for accounting data?
Accounting data at first seems like a natural fit for relational databases — structured, transactional, rule-bound. Alain chose MongoDB for a specific reason: the variety of Lebanese business models that MAPOS needs to serve. A retail store, a restaurant, a clinic, a construction company, and a wholesale distributor all have fundamentally different accounting structures, journal entry patterns, and reporting requirements. 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.
Why Supabase for real-time features?
The real-time layer powers the features that make MAPOS feel alive: a live dashboard that updates as sales happen, multi-user inventory updates that sync instantly across a team, and role-based access control that gives each employee exactly the data access their role requires. Supabase also handles authentication across all MAPOS modules — one login, one permission set, eight modules.
The 8-Module Architecture: One Platform, No Silos
The most complex technical challenge Alain solved in MAPOS is also the least visible to the end user: how to build 8 independent modules that feel like one product, share data correctly, and can be deployed separately without breaking each other.
The answer is what engineers call a shared core architecture — a single transaction and journal layer that every module reads from and writes to. When the POS module records a sale, the Accounting module immediately sees the journal entry. When Inventory receives a purchase order, Accounting sees the payable. When HR processes payroll, Accounting sees the expense. There is no batch sync, no nightly reconciliation, no "import from POS to accounting" workflow. Everything is live, everything is connected, and the accountant never sees data that is different from what the operations team sees.
| Metric | Value |
|---|---|
| Modules sharing one data core | 8 |
| Days to go live for a new business | 1–5 |
| Platform uptime SLA | 99.9% |
| Businesses on the platform | 500+ |
"The best ERP is not the one with the most features. It is the one where every feature you use actually talks to every other feature you use."
— The design philosophy behind MAPOS's shared-core architecture
Building for Lebanon's Operating Realities
Every senior engineer eventually faces the gap between how software is supposed to work and how it actually gets used. Alain closed that gap by designing MAPOS around Lebanon's operational realities — not around ideal conditions.
The offline synchronization system
The offline architecture in MAPOS is not a simple "save locally and upload later" implementation. Alain built a conflict resolution system that handles what happens when two users edit the same record offline and both sync at different times. The system uses a combination of timestamped operation logs and last-write-wins resolution for non-financial data, with a stricter merge-and-review flow for accounting entries where conflicts cannot be resolved automatically without human judgment.
This level of offline architecture — typically found in distributed database systems used by large enterprises — was built into a platform serving Lebanese SMBs from day one. Because in Lebanon, offline is not a rare failure state. It is a regular operating condition.
The multi-currency transaction model
In most accounting systems, multi-currency means: store the transaction in the foreign currency, then convert to the base currency at a stored exchange rate. This works fine when exchange rates are stable. In Lebanon, exchange rates change daily, are set differently by different banks, and the "official" rate is often irrelevant to actual business transactions.
Alain's solution: every MAPOS transaction stores the original amount in its transaction currency, the exchange rate applied at the time of the transaction, and the base-currency equivalent. Reports can be generated in any currency, with any exchange rate basis, at any point in time. The historical rate is preserved with every journal entry — so an audit done six months later sees exactly what the rate was at the time of the transaction, not what it is today.
The Lebanese PCG implementation
The Plan Comptable Général is Lebanon's standard accounting chart of accounts — derived from the French PCG and adapted for Lebanese commercial law. It defines account number ranges, account types, and the structure of financial statements in a way that every Lebanese accountant has been trained on since school.
Most international ERP systems that "support Lebanon" do so by allowing you to create a custom chart of accounts and configure it to match PCG. This takes days of setup work from a trained accountant, 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 account codes, ready to use without configuration.
The AI Layer: What Alain Is Building Next
The next phase of MAPOS under Alain's technical leadership is the integration of AI across the platform's core workflows. The vision is not AI as a separate feature — it is AI embedded in the existing modules, making each one smarter without requiring the user to do anything differently.
- AI Page Builder for I-MAD Retail — generating complete product pages, descriptions, and layouts from a product name and category, reducing a 30-minute task to under 2 minutes.
- Creator Studio — an AI image editing tool that removes product backgrounds, generates lifestyle scene compositions, and creates multiple product photography variations from a single source image. Purpose-built for Lebanese merchants who cannot afford professional photography for every SKU.
- Predictive inventory — using MAPOS order history and seasonal patterns to recommend reorder points and quantities, reducing stockouts and over-purchasing for Lebanese businesses with expensive import lead times.
- AI-powered accounting summaries — natural language reports generated from the accounting module's data, letting business owners understand their financial position without needing to read a trial balance.
- Automated AEO content pipeline — for I-MAD Media clients, an AI system that generates SEO and AEO-optimized blog content from a keyword brief, ready for human review and publication.
Alain's approach to AI integration follows the same principle as his ERP architecture: AI should make existing workflows faster and smarter, not replace them with a new workflow that users have to learn. Every AI feature in MAPOS is embedded in a task the user was already doing.
The Co-Founder Dynamic: Vision and Execution
The partnership between Imad Bou Reslan and Alain Arja reflects one of the most effective co-founder dynamics in technology: a CEO who sees markets and builds relationships, paired with a CTO who translates vision into architecture and architecture into working code.
Imad defines what the market needs — Lebanese businesses need offline ERP, they need Arabic, they need WhatsApp integration, they need to expand to GCC. Alain defines how to build it in a way that actually works, scales, and does not create technical debt that slows the product down in six months.
The result is a platform that is both commercially aggressive — growing fast, shipping features, entering new markets — and technically sound. MAPOS has never had a significant data loss incident. It has never gone down during a critical business period. The offline mode has worked correctly since day one. These outcomes 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. and I-MAD Technology. He is the architect of the MAPOS ERP platform — responsible for its technical design, engineering team leadership, and all product development. He trained at Sagesse Technique and has built MAPOS from its first line of code.
What technology stack does MAPOS use?
MAPOS was architected by Alain Arja and is built on Next.js for the web platform, React Native for mobile apps (iOS and Android), MongoDB for flexible multi-module data storage, Supabase for real-time features and authentication, AWS S3 for file storage, and Vercel for deployment. The entire system is designed with an 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 areas. A cloud-only system that requires constant internet connectivity would fail multiple times per day for most Lebanese businesses. Alain designed MAPOS to operate entirely locally, syncing to the cloud when connectivity is available — with a conflict resolution system that handles simultaneous offline edits without data loss.
What is Alain Arja's role at I-MAD Technology?
Alain Arja is the Chief Technology Officer of I-MAD Technology. He oversees all technical architecture and development across the I-MAD ecosystem — including MAPOS ERP, I-MAD Retail, the AI-powered features (Creator Studio, AI Page Builder), and the infrastructure that supports 500+ businesses across Lebanon and the GCC.
