Skip to content
All work
// Case studySaaSlive

MONTRA ERP

Multi-tenant maintenance-operations ERP — fault calls, preventive visits, live technician dispatch, parts and contracts.

2026 Egypt · Saudi Arabia Maintenance operations SaaS · Elevator industry
ERP & internal systemsMulti-tenant SaaS
MONTRA ERP — Multi-tenant maintenance-operations ERP — fault calls, preventive visits, live technician dispatch, parts and contracts.

// By the numbers

Tables under row-level securityevery tenant table ships with its isolation policy in the same migration
0 / 50
API p95 latencyload test with 200 concurrent technicians, 0% errors — target was 500 ms
0 ms
Built-in reportsjob costing, SLA, parts and technician performance, with scheduled e-mail
0
Sector templateselevators first, ready-made setups for six more maintenance trades
0
// The problem

What the business was up against

Elevator maintenance companies carry hundreds of contracts, each promising periodic visits and a response time on breakdowns. In practice the work ran on phone calls and WhatsApp groups: nobody knew which technician was nearest, preventive visits were missed until a lift stopped, spare parts left the warehouse without a trace, and month-end costing was a guess. Missed visits and slow responses are exactly what clients cancel contracts over.

// Overview

MONTRA ERP runs the field operations of a maintenance company. A breakdown call or a scheduled preventive visit becomes a job; the dispatch board ranks which technician should take it; the technician is tracked live until they arrive, then photographs, reports and requests parts from a mobile app. Spare parts, vans, contracts, cash custody, costing and reporting sit in the same system. It is sold as multi-tenant SaaS in Egypt and Saudi Arabia, and the same codebase installs self-hosted for companies that need it on their own servers.

// Inside the product

See it working

Real screens from the shipped product, recorded on demo data.

Where dispatchers and supervisors at a maintenance company log faults, see every technician on the map, assign the closest one and sign off finished jobs.

erp.montralift.com
// Architecture

How it's put together

  1. L1Surfaces

    • Operations Panel
    • Technician App
    • Customer Tracking
    • Platform Admin
  2. L2Application layer

    • Multi-tenant API
    • Job Workers
  3. L3Data & integrations

    • PostgreSQL + PostGIS
    • Live Maps
    • Payments
    • Object Storage

One multi-tenant API behind every surface; each tenant walled off by row-level security.

// Engineering decisions

The calls that shaped it

  1. ADR-01

    Tenant isolation enforced twice

    Every query filters by company, and PostgreSQL row-level security pins the tenant inside each transaction as a second wall. The API connects as a role that does not own the tables, so a missed filter fails closed instead of leaking another company's data.

  2. ADR-02

    Append-only audit at the database level

    The database role the application uses has no UPDATE or DELETE on the audit log. A history that the app itself cannot rewrite is the only kind worth showing an auditor or a client in a dispute.

  3. ADR-03

    Scoped, non-escalating permissions

    Permissions are resource.action strings with a data scope — whole company, one branch, or only my own tasks. No one can grant a role more power than their own, so delegation to branch managers is safe by construction.

  4. ADR-04

    Background jobs that run exactly once

    Scheduled work — preventive-visit generation, SLA escalation, report e-mails — runs on BullMQ with PostgreSQL advisory locks, so it fires once per tick across replicas, and deliveries retry with exponential backoff.

  5. ADR-05

    One codebase, SaaS or self-hosted

    Plans, limits and billing sit in a platform-admin layer above the tenants, and a license mode turns the same build into an on-premise install — one product serving both buyers who rent and buyers who must own.

// Highlights

Signature capabilities

Live dispatch

A board that ranks the best technician for each job by distance and load, tracks them on a map to site, and escalates before an SLA is breached.

Preventive plans that run themselves

Contracts define visits by calendar or meter reading; the system creates the jobs on time, so a missed visit is an exception, not the default.

Parts with a chain of custody

Every part is traced from warehouse to van to job, with approvals for outside purchases and cash custody per technician.

Defensible multi-tenancy

Row-level security, a non-owner database role and an append-only audit log keep each company's data isolated and its history tamper-evident.

// Features

Business feature set

18Features

  • Field operations5
    • Customers, sites and asset registry
    • Full fault lifecycle from call to closure
    • Shifts and live technician tracking map
    • Dispatch board with ranked technician suggestions
    • SLA warnings and automatic escalation
  • Preventive maintenance3
    • Maintenance contracts and meters
    • Versioned checklists
    • Time- or meter-based plans that create visits automatically
  • Parts & money4
    • Spare parts, warehouses and vans
    • Part requests and outside purchases
    • Cash custody and approvals queue
    • Job costing and 13 reports with Excel import / export
  • Platform6
    • Multi-branch, multi-tenant with role-based permissions
    • Offline-capable technician app
    • Customer tracking page and WhatsApp updates
    • Plans, limits and online payments
    • Self-hosted license mode
    • Arabic / English with full RTL
// Outcome

What changed operationally

  • Fault calls and preventive visits handled in one job lifecycle
  • Live technician tracking and a ranked dispatch board with SLA warnings and escalation
  • Spare parts traced from warehouse to van to job, with approvals and cash custody
  • Preventive plans by time or meter reading that create visits automatically
  • Customer tracking page and WhatsApp status updates
  • Templates for seven maintenance sectors beyond elevators
// Constraints

What we had to work within

  • Each tenant's data must be provably isolated — maintenance contracts and client sites are confidential
  • Technicians work in basements and shafts with poor signal, so the field app has to work offline
  • Arabic-first interface with full English parity across admin and field apps
  • Runs on a modest VPS alongside other services, under tight memory caps
  • Local payment gateways for Egypt and Saudi Arabia
// My role

What I owned

  • Product scope and competitor analysis
  • Multi-tenant architecture and security model
  • Database design with row-level security migrations
  • API: auth, RBAC, jobs, SLA engine, inventory, contracts, costing
  • Operations panel in Arabic and English
  • Flutter technician app
  • Billing, platform admin and self-hosted packaging
  • Docker deployment, CI/CD and load testing
// Stack

Built with

Backend

NsNestJS
TsTypeScript
DzDrizzle
PgPostgreSQL
PoPostGIS

Jobs & cache

RdRedis
BuBullMQ

Frontend

NxNext.js
TwTailwind CSS
Nenext-intl
TaTanStack Query

Mobile

FlFlutter

Infrastructure

DkDocker
GxNginx
CiCI/CD
SeSentry
// Makhloof Studio

Want something like MONTRA ERP?

Boutique software studio — agency-quality systems, built by a senior engineering team.