There are many tools on the market for developing CRM and SaaS systems: Laravel, Symfony, Directus, Salesforce, and dozens of other solutions.
Nor Abon does not aim to replace general-purpose frameworks. Its goal is to reduce the development time of typical CRM, ERP, and SaaS projects through architectural standardisation and automation of routine tasks.
In most frameworks, developers define the application structure through program code.
In Nor Abon, the majority of the system is described using declarative schemas:
DB Schema → Object Schema → Action Schema → Page Schema
Based on these schemas, the framework automatically generates:
database structure API administrative interface data validation access control checks forms lists relationships between objects
This allows developers to focus on project business logic rather than implementing standard CRUD operations.
All Nor Abon projects follow the same structure.
Regardless of the business domain, developers always know:
This simplifies project maintenance and reduces the onboarding time for new developers.
In typical projects, a significant amount of development time is spent building administrative interfaces.
Nor Abon automatically generates:
edit forms record lists filters reference directories object view pages
When necessary, any automatically generated interface can be extended or overridden.
Standard operations (`add`, `get`, `update`, `remove`, `search`) are implemented at the core level and become available immediately after creating the corresponding schemas.
For non-standard scenarios, developers can implement their own actions, modules, and handlers.
This approach combines rapid development with the ability to deeply customise application behaviour.
In most web applications, the Backend is responsible only for data, while the interface structure is implemented entirely on the Frontend.
In Nor Abon, the Backend defines not only the data but also the interface structure through Page Schemas.
This makes it possible to:
The framework core is isolated from the application code.
The standard project structure is divided into two parts:
framework/ app/
When updating the framework, only the contents of the `framework` directory are modified, while the project's business logic remains unchanged.
This simplifies project maintenance and reduces the risk of conflicts during upgrades.
Nor Abon is designed for projects where the primary workload consists of:
The more a project relies on objects, forms, lists, business processes, and administrative interfaces, the greater the benefits of using a declarative architecture.