Kanonik: a product repository modernised in 2 months
Kanonik, an insurance software publisher, needed to move away from an ageing tool. In 2 months, TCM built a modular back office, synchronised with Elasticsearch and secured by SSO.
A central repository for the entire ecosystem
Kanonik, an insurance software publisher
In 2025, TCM (The Coding Machine), a custom software development agency based in Paris, modernised the product repository of Kanonik, an insurance software publisher, in 2 months, with a React and Symfony back office.
Kanonik is an insurance software publisher. Its ageing tool carried significant technical debt.
The need was critical: create a centralised, high-performance and scalable repository. It had to structure business entities and make interconnection with the existing ecosystem easier.
Complex data, always available
Complex dynamic structures
The repository had to model complex, dynamic data structures.
High-availability synchronisation
Data had to be synchronised asynchronously, with a high level of availability.
Robust code from day one
Delivering in 2 months without sacrificing quality: the architecture follows a DDD approach and development is covered by tests (TDD).
A modular and secure back office
Product repository, synchronisation and security
TCM built a modular back office in React and Symfony that manages the entire product repository.
An asynchronous synchronisation engine feeds Elasticsearch. Access is secured at the perimeter by an external identity provider.
Front-end administration application
An ergonomic interface for business administration.
SSO authentication module
Secure login via OpenID Connect and an external identity provider.
Technical architecture document (TAD)
The reference documentation for the architecture.
Two months is short to rebuild a repository. We bet on a clean, tested architecture from day one, so that Kanonik can evolve it with confidence.
The project's technologies
Redesign and modernisation
An ageing tool replaced in 2 months by a central, high-performance and scalable repository.
Business application
An ergonomic back office to manage the product repository day to day.
Custom development
A React and Symfony architecture, synchronised with Elasticsearch and secured by SSO.
Your questions about redesigning a business back office
What you need to know before launching a similar project, with the concrete example of what we built.
It all depends on the scope, but a well-defined repository can be modernised in a few months. For Kanonik, an insurance software publisher, TCM delivered a React and Symfony back office in 2 months, synchronised with Elasticsearch and secured by SSO.
By starting again from a well-modelled central repository, synchronising data to the other tools and covering the code with tests. This is the approach followed for Kanonik: DDD architecture, TDD development and asynchronous synchronisation to Elasticsearch.
TCM (The Coding Machine), a custom software development agency based in Paris, modernised the product repository of Kanonik, an insurance software publisher, in 2025: a modular back office, SSO authentication with OpenID Connect and a technical architecture document.
