Why Nama
Buying business software is a long relationship, not a transaction. These are the commitments that come with it — the ones worth asking any vendor about before you sign.
-
Our branches look after you
The relationship does not end when the system goes live. We keep teams in several Arab countries for after-sales service, and your staff are entitled to enough training to actually use what you bought. Our implementers configure the system around how you work — the chart of accounts a trading company needs is not the one a manufacturer or a services firm needs.
-
Check before you buy
Before choosing Nama ERP, verify for yourself every capability you have been shown — whether published on this site, described by a salesperson, or reported by another customer. Ask directly about anything your business specifically requires. Do not buy the system until you are genuinely satisfied it does what you need.
-
A ready-made system you can still tailor
Most ready-made applications become the obstacle: they suit some businesses and block the rest. Nama ERP is built on an open design, so it can be tailored — hiding or showing fields, changing screen layouts, altering translations and field titles, and as far as adding a complete new module built for one customer that still integrates with the rest of the system. Requirements can also be raised before you buy, to be delivered within an agreed period.
-
After-sales service
Once you are live, the nearest branch is who you call — for a problem, for extra training, or for technical support. Your data's integrity is protected, and its confidentiality with it: balances, debts and the rest stay yours even while our team works on the database. You can also request enhancements, which are weighed on their merit and on how many customers need them. New releases carrying fixes and improvements are published regularly, and customers under warranty or a service agreement receive them.
-
Moving from another system
If you are running something else and want to move, we migrate your existing database into Nama ERP — keeping your data, your opening balances and your history rather than starting you from an empty system.
- Your ERP as an MCP Server
Nama ERP ships a built-in MCP server, so an AI client like Claude Desktop or Claude Code can connect to the system and work inside your permission model. It is deployed and running at customer sites today.
- Governed AI in Your ERP
The assistant has no capability of its own. Everything it does goes through a tool an administrator defined, executing as a real user with the full security model applied — and Expert Mode shows you exactly which tool ran.
- Arabic First, Not Arabic Later
Amounts written in words with the four Arabic grammatical forms a cheque needs, Hijri dates beside the fields that need them, and every label in the system editable in place. Arabic ERP software written that way from the start reads differently.
- Every Company in One Database
Five dimensions — legal entity, sector, branch, department, analysis set — sit on almost every record, driving who sees it, how it groups in reports and how it maps to the account code. One database, one item catalogue, consolidated figures.
- It Keeps Working When the Network Doesn't
The till has its own local database and sells through an outage. The mobile app downloads what it needs at login and syncs when the line returns. An offline ERP is not a slogan here — it is where the data physically sits.
- Ten Years of Monthly Releases
124 consecutive monthly releases, April 2016 through July 2026, every one of them written up and published. And because customisation lives in configuration rather than in modified source, every installation runs the same build.
- An Open REST API, Included
CRUD on every entity, an OpenAPI 3.0 specification and a Swagger UI generated from your own configuration — available to every customer at no additional cost. Integration stops being a line item and becomes a Tuesday.
- Six Doors Between a User and Your Data
Authentication, menus, type permissions, record visibility, field and page control, then actions and capabilities — six layers, resolved in a fixed order, where an unmatched permission is denied rather than allowed.
Get started with Nama today
Tell us how your business runs and we will show you how Nama ERP fits it — in your language, on your infrastructure.