Technical Roadmap

This is the technical roadmap for The NovaFacies Open Source Framework.

More information can be found in Documentation and in Resources.

Our approach

At NovaFacies, we believe that financial technology should be modular, standardized, and built to evolve. To achieve this, we have established a structured API-first development approach that ensures every component can be implemented in multiple ways while maintaining interoperability.

An API-First Development Approach

Our development methodology follows three clear steps:

1. Defining the Modules
   • Every module in NovaFacies is carefully designed before development begins.
   • This includes defining what the module does, what functions it should have, and how it interacts with other parts of the system.
   • Our structure for defining modules follows the General Framework Documentation, ensuring consistency across implementations.
2. Designing the API Before Writing Any Code
   • Each module starts with a well-defined API.
   • This API structure ensures that modules can be built using any technology while maintaining full interoperability.
3. Allowing Open Implementation
   • Once the API is defined, any organization can develop the module however they see fit.
   • Whether using traditional coding, low-code platforms, or Backend-as-a-Service, every approach remains compatible as long as it adheres to the API standard.

While NovaFacies is an open framework, the Foundation itself will lead by example by developing two versions of the core modules:

1. A traditional coded version
   • Built using a conventional software development approach.
   • Designed for maximum flexibility and control.
   • Excluding the Workflows module.
2. A rapid implementation using prebuilt tools
   • Developed as quickly as possible, leveraging existing FinTech solutions, low-code platforms, and Backend-as-a-Service (BaaS).
   • Ideal for organizations that need a fast, low-maintenance deployment.

Additionally, NovaFacies will support any organization that wants to develop its own version—whether they prefer a fully custom-coded solution or a hybrid approach using modern automation tools.

Workflows Module: The Key to rapid development

One of the most powerful aspects of NovaFacies is the Workflows Module. This module acts as a bridge that enables:

Inter-module automation – Allowing modules to interact dynamically through API-based workflows.
Internal module extensions – Adding functionality inside a module before it is natively developed.

For example, let’s take the User Module:

• Imagine that we want a rule stating “every user in Belgium should automatically be assigned the role ‘Belgium.’”
• If this feature is only planned for User Module v5 (imagine some funtion that automatically assigns uers to roles), the Workflows Module can be used in the meantime to achieve the same result dynamically.
• Some organizations may even choose to keep Workflows as their permanent automation layer rather than waiting for new module versions.

Evolving Modules Over Time

Instead of forcing rigid early-stage functionality, NovaFacies follows a progressive module development approach:

• Mandatory functions will expand over time.
• The Workflows Module allows users to extend functionality dynamically while waiting for new versions.
• This ensures that partners can start building immediately, even before every feature is officially implemented.

Modules

Modules can be found in in our Resources.