Why C10R?
In every CRM, ERP or SaaS application, developers repeat the same code again and again: list pages, entity views, forms, status updates. The same duplication happens on the backend: queries, handlers, and permission checks. This slows down delivery and increases costs.
When business needs a new field, tab, or workflow, developers must touch multiple layers: database, API, UI, and tests. Scaling this is painful.
The Config Driven Development approach
C10R replaces code duplication with declarative configuration. Applications are built from reusable building blocks:
- Frontend: UI components like
text,list,button,table - Backend: data selects and handlers
The framework reads the config, assembles the UI, and wires the server logic automatically. The same declaration drives both frontend and backend behavior.
Simple Examples
{
"type": "text",
"value": "Hello, world!"
}Render:
Hello, world!
{
"type": "button",
"text": "Mark as Done",
"serverHandler": "task.handler.update_status",
"data": { "taskId": "123", "statusName": "Done" }
}Render:
(on click → calls task.handler.update_status on the server)
Where to use C10R
- CRM systems: contacts, deals, tasks
- ERP & internal portals: warehouses, orders, invoices
- SaaS platforms with repeating UI patterns
- Fast prototyping of business processes
Compact by design
Configurations do not bloat the project. All components and handlers exist once, and the config just tells the engine how to combine them. Adding a new entity or page means only adding a JSON description, not hundreds of lines of code.