Web applications
Pages, portals and dashboards built on shared components and logic.
Proprietary framework / HermesLXP
One core. Many possibilities.
A proprietary framework for building custom software platforms. Designed to turn reusable parts into tailored products.
Our method in practice
Our most ambitious
engineering project.
Hermes isn’t just a product: it’s the concrete proof of how we design and build complex software systems.
Why we built Hermes
The same complexity.
A better foundation to face it.
Every platform has unique needs. But identity, data, permissions and interfaces shouldn’t start from scratch every time.
We designed HermesLXP to gather these foundations into a proprietary framework: to speed up building custom applications and keep control over the architecture.
The problem isn’t only writing faster. It’s making the parts a product has to connect coherent.
Inside the architecture
Separate responsibilities.
Connected capabilities.
Select a module to explore its role.
A conceptual view of Hermes.
Module / core
Core Engine
The coordination point: it connects modules, configuration and the application lifecycle.
A shared foundation lets features evolve without replicating the structure of every product.
Hermes Core Core EngineModule / data
Data Engine
A custom data system to organise entities, relations and operations.
Modelling data together with application flows makes ownership, validation and access explicit.
Hermes Core Data EngineModule / application
Application Engine
Pages, dashboards and processes composed from reusable modules.
Applications combine components and specific rules while keeping a common structure.
Hermes Core Application EngineModule / ai
AI Engine
An integration layer connecting AI, context and application processes.
Hermes AI is the integration point for AI capabilities in the product. Local models, APIs, vector search and agents are options to evaluate per use case, not universal guarantees.
Hermes Core AI EngineModule / auth
Authentication
Identity and access to the system, before any protected interaction.
User identity is kept separate from the rules that decide which operations are allowed.
Hermes Core AuthenticationModule / permissions
Permissions
Access rules for users, content and features.
Permissions travel with actions on the system and must be enforced on the server, even when the UI hides a command.
Hermes Core PermissionsModule / automation
Automation
Processes and node connections to organise operational flows.
Making conditions, actions and errors visible helps to understand and maintain automations.
Hermes Core AutomationModule / plugins
Plugin System
Extensions that add capabilities to the platform.
An extension point must have explicit responsibilities and dependencies, to preserve the coherence of the core.
Hermes Core Plugin SystemModule / api
API Layer
Contracts to integrate services and different interfaces.
Integrations require validated inputs, understandable errors and intentional version management.
Hermes Core API LayerModule / builder
UI Builder
Visual composition of pages and sections with drag & drop.
No-code to compose; low-code to customise. The builder brings the application model closer to the interface.
Hermes Core UI BuilderApplication builder
Visual by design.
Custom by nature.
Pages, sections and dashboards take shape with a visual drag & drop editor.
No-code composition makes the system accessible. Low-code customisation leaves room for the product’s specific needs. Users, rules and flows stay part of the same architecture.
Page header
Content
module
module
Data
view
view
Action → Workflow
Interfaces & delivery
One system. Many surfaces.
Mobile integration
Mobile experiences connected to the platform’s data and capabilities.
Desktop applications
Dedicated interfaces to bring flows and tools into the work context.
The project, in context
Decisions behind the framework.
Proprietary framework
HermesLXP
One common foundation. Infinite product possibilities. A modular framework for building custom software platforms.
Product & Software Architecture
Read the case studyFuture direction
A platform is a journey.
The direction is to widen the possibilities of composition, integration and reuse while keeping the system understandable.
The next steps will be shared once defined. No release date announced.
Have a complex challenge?
An ambitious idea deserves an architecture to match.
Let’s talk