01 / 14 · Start from what exists
The core system
It works. But it was designed for a world of counters and office hours, not for 24/7 digital.
Core banking, an operator’s BSS/OSS, ERP, a public administration’s business applications: the core keeps the business running. But users are mobile, payments are instant, and partners want to connect.
Key takeawayThe core system doesn’t go away. It simply can no longer stand alone.
Before opening up, you need to see what is happening in-house.
Consulting & transformation →02 / 14 · See
Monitoring & observability
When a counter goes down, an employee calls. When a digital service goes down, the user leaves without a word.
You need real-time visibility from the user’s point of view: response times, error rates, availability. Not just “is the server responding?”, but “is the service working?”.
Key takeawayObservability isn’t monitoring: you watch services, not just servers.
Centreon · Elastic · Uptime Kuma
Now you can see. And what you see is worrying: what happens if this critical server goes down?
Platforms & operations →03 / 14 · Hold
High availability & sovereign cloud
Digital services run 24/7: every interruption is a direct loss, of business and of trust.
Redundancy, replication, automatic failover — plus one more requirement in our context: sovereignty. Customer and citizen data stays on national soil, under control.
Key takeawayHigh availability isn’t backup: it means zero noticeable interruption.
HAProxy · MariaDB Galera · OpenStack · Proxmox · Kubernetes
But with ten servers to manage instead of two, how do you keep up?
Infrastructure & cloud →04 / 14 · Industrialise
Automation & management
Manual management doesn’t scale: going from 2 to 20 services without automation multiplies errors.
Automated deployments, provisioning, inventory, identical configurations between test and production: this is what lets you grow without multiplying teams.
Key takeawayThe difference between a craftsman and a factory: both produce, but only the factory scales.
Ansible · Foreman · GLPI · phpIPAM
The foundation is ready. Now it’s time to open up to the outside world.
Infrastructure & cloud →05 / 14 · Accelerate
Middleware · business processes
A file that takes three days and five paper signatures holds back the entire transformation.
Between the core system and the outside world, middleware acts like the front desk of a grand hotel: it welcomes, directs, translates and protects. Its first role: modelling and executing processes, and automating manual tasks where existing systems have no API.
Key takeawayRPA isn’t the destination, it’s the bridge. Once digitalised, a process goes from three days to a few minutes.
BPMN (Camunda, Bonita) · RPA
Processes are automated. Who orchestrates the technical exchanges?
Integration & orchestration →06 / 14 · Orchestrate
Middleware · orchestration
An instant transaction involves more than five systems in under ten seconds.
Verify identity, check, debit, confirm, notify… You need a conductor: an ESB or microservices for critical real-time flows, and lighter tools for internal flows and notifications.
Key takeawayDistinguish transactional orchestration (real time) from operational orchestration (batch, internal flows).
ESB · integration microservices · n8n
Flows are orchestrated. But who controls access?
Integration & orchestration →07 / 14 · Govern
Middleware · API management
Every API exposed without governance is an open door.
Who is allowed to call what, how often, and with what level of security? A single gateway to your IT systems: developer portal, quotas, and a sandbox where partners can test risk-free.
Key takeawayAPI management is a governance issue before it is a technical one.
WSO2 API Manager · Kong Gateway
The systems are talking. How do you handle asynchronous flows?
Integration & orchestration →08 / 14 · React
Middleware · events
In modern IT systems, systems don’t call each other constantly: they publish and they subscribe.
A completed transaction, a new account, a raised alert: every event is published, and the systems concerned react. It is the nervous system of your IT — real-time anti-fraud, continuously fed data, instant notifications.
Key takeawayLike a notice board: everyone posts what’s happening, and the others react if it concerns them.
Kafka · RabbitMQ · Redis Streams
The middleware is complete. All this openness requires well-managed development.
Integration & orchestration →09 / 14 · Build
Software factory
Connectors, interfaces, custom integrations: transformation depends on well-managed development.
Version control, continuous integration and deployment, code quality and security, containers. And when in-house skills are lacking, staff augmentation experts reinforce your teams on specialist topics.
Key takeawayYou can’t carry everything alone: getting support is a choice that keeps you in control.
GitLab CI/CD · SonarQube · Docker
None of this transformation makes sense without security.
Software engineering →10 / 14 · Protect
Cybersecurity & compliance
Everything you open up creates attack surface: every API, every channel, every partner is an entry point.
Cybersecurity isn’t a layer added at the end: it runs through everything. Real-time incident detection, privileged access control, centralised end-to-end identity.
Key takeawayRegulatory compliance is built in from the design stage, not after the audit.
Wazuh · Wallix PAM · Keycloak
The foundations are in place. Channels can now be opened with confidence.
Cybersecurity & trust →11 / 14 · Open
The channels
The end user is the judge. If the experience isn’t seamless, nothing else matters.
Web, mobile — tomorrow’s front door —, USSD to reach those without a smartphone, and above all partners, who build their services on top of yours.
Key takeawayOpening up without foundations is building on sand.
Web · mobile · USSD · partners
Every interaction generates data. What do you do with it?
Software engineering →12 / 14 · Steer
Data & performance management
Today, data lies dormant in logs, databases and files. Tomorrow, it drives decisions.
Data converges, becomes structured and usable: dashboards, automated regulatory reporting, in-depth user insight. Event-driven architecture feeds it continuously.
Key takeawayOnce automated, regulatory reporting becomes a by-product of your IT systems.
Data lake · pipelines · BI
Once the data is there, the next question is obvious…
Data & performance →13 / 14 · Augment
Artificial intelligence
AI isn’t a gimmick: it is the natural use of the data that modernised IT systems produce.
Models that learn to detect fraud or anticipate failures, agents that handle support and analyse documents, accelerated processes.
Key takeawayWithout the foundations, AI doesn’t deliver on its promise.
Machine learning · LLM · agents
Infrastructure, openness, data, intelligence: a strategic question arises…
AI & automation →14 / 14 · Tomorrow
IT systems become a platform
Yesterday, a closed system: users came to you. Today, channels and open APIs: you go to them.
Tomorrow, your services are embedded in your partners’ applications. Your IT systems become infrastructure that others build on, and your APIs create value.
Key takeawayInfrastructure is the soil, AI the seed, the platform the harvest.
Let’s talk about your roadmap →