Architecture

Sooner or later someone in your IT department will ask the question that no feature list answers: what is this thing, exactly, and what will it do to our servers? Perhaps a security review board wants to see the design before it approves the purchase. Perhaps a systems administrator has been handed a budget line for a new machine and needs to know what to buy. Perhaps you are simply being asked, in a tender document, to attach "the application and infrastructure architecture".

These pages are that attachment. They describe how Nama ERP is put together, how it is deployed and operated, and how it is secured — written for the people who run servers rather than the people who post invoices.

🏗️Application ArchitectureHow the system is built: layers, modules, clients, the data model, and how a saved document becomes an accounting entry.🖥️Infrastructure ArchitectureHow it is deployed and run: servers, ports, storage, backups, upgrades, and the supported topologies.🔒Security ArchitectureHow access is controlled and data protected: authentication, permissions, transport security, and the audit trail.

Looking for something more specific?

Hardware sizing lives in System Minimum Requirements, the step-by-step install in the Installation Guide, and the programmatic interface in Nama ERP REST API.