Case study / Proprietary framework
HermesLXP
One common foundation. Infinite product possibilities. A modular framework for building custom software platforms.
- Our role
- Product & Software Architecture
- Focus
- Proprietary framework
- Technology
- PHP / JavaScript / MySQL / Modular architecture
Problem
Building custom platforms often repeats the same problems: identity, permissions, data, interfaces and integrations. Solving them from scratch every time scatters the design work.
Context
HermesLXP was born as a proprietary framework to speed up building software products with specific needs.
Constraints
Reconciling customisation and reuse. A visual environment must leave room for the technical needs of different applications.
Architecture
A common core coordinates data, applications and modules. The builder composes interfaces and sections; authentication and permissions govern access. The diagram shows a conceptual view of the system.
- Data Engine
- Application Engine
- AI Engine
- Authentication
- Permissions
- Automation
- Plugin System
- API Layer
- UI Builder
- Web
- Mobile
- Desktop
Our role
Conception of the framework, architecture design and development of the HermesLXP ecosystem.
Technical decisions
Separating reusable modules from product-specific choices. Distinguishing identity from authorization. Exposing visual composition without removing technical customisation.
Implementation
Visual drag & drop editor, modular pages and dashboards, configurable user registration and processes represented through a node structure.
Challenges
Keeping the relations between data, users and processes understandable as the number of features grows. Clarity of boundaries is part of the product.
Results
A platform that gathers common capabilities into a reusable building environment. Quantitative results are not published yet.
Lessons learned
Reusability requires a coherent model: moving code into a module is not enough if responsibilities and dependencies stay implicit.
Have a complex challenge?
An ambitious idea deserves an architecture to match.
Let’s talk