There is a question buyers rarely ask out loud and always want answered: is anyone still working on this? It is a fair question. The ERP market is full of products that were finished in 2018 and have been maintained ever since in the sense that a building is maintained.
Here is the answer in one number. 124 consecutive monthly releases, from April 2016 through July 2026. Not 124 releases — 124 months, each with its own release, each written up and published. There is no gap in that run.
Why the cadence matters more than any single feature
A monthly rhythm changes what a vendor can respond to. A tax authority publishes a new requirement; a regulator changes a form; a customer finds an edge case in end-of-service calculation. On an annual cycle those are next year’s problems. On a monthly one they are a release note.
It also changes what you can verify. The notes are public, they go back a decade, and they are specific. You can read what changed in the module you care about, in the year you care about, before you sign anything — which is a different kind of due diligence from a roadmap slide.
Why ERP updates and upgrades are not a project here
The usual reason upgrades hurt is that the last one was customised. Somebody changed the source for one customer, and every subsequent release has to be re-merged onto that fork, forever. That is the tax most ERP buyers eventually pay without having been told about it.
Nama’s architecture removes the cause. Screen layouts, validation rules, numbering schemes, approval cycles, document behaviour, calculated fields and automated actions are all stored as data and edited by administrators from inside the system. A typical implementation involves a great deal of configuration and no change to the shipped application at all.
The consequence, in the documentation’s own words: because customisation lives in configuration rather than in modified source code, upgrades do not have to be re-merged customer by customer. Every installation runs the same build.
Two customers running that identical build can still behave very differently. That is the point.
What to do with this
Ask every vendor on your shortlist for their release history — not their roadmap. A roadmap describes intentions; a decade of dated release notes describes a habit. Ours are published, in Arabic, on the documentation site, and you are welcome to read them before you talk to us.
Good question — already answered
How often is the system updated?
Monthly. There are 124 consecutive monthly releases from April 2016 through July 2026, each named for its year and month, each with published release notes. No month is missing from that run.
Will an upgrade break the changes we made?
Customisation in Nama lives in configuration — screen layouts, validation rules, numbering, approval cycles, document behaviour, calculated fields, automated actions — all stored as data and edited from inside the system. Because it is not modified source code, upgrades do not have to be re-merged customer by customer. Every installation runs the same build.
Where can we read the release notes?
They are published on docs.namasoft.com, in Arabic, going back to the first one in April 2016.
How old is the company?
Namasoft was founded in 2011. The monthly release run begins in 2016, which is when the notes started being published, not when the product started.
Do we have to take every release?
No — but they are cumulative improvements and fixes, and customers under warranty or a service agreement receive them as they are published.
