Financial & Insurance
WTEC Coming Home: Migrating core banking systems in-house for a regional financial services leader.
Removing external vendor dependency to shorten time to market and regain strategic control
Our Client’s Backstory
Our client is a technology provider within a major financial group based in Austria, supporting banking, insurance, and financing operations across Central Europe. They manage the software systems and infrastructure of the entire group. While most systems were already handled internally, their core digital banking applications were still owned and maintained by an external vendor, and bringing these in-house became a clear strategic priority.
The Challenges
The client’s core digital banking and field service applications were developed and hosted externally, leaving the client dependent on a third party for software their customers and field staff relied on every day.
Recurring costs with limited return: Paying an external provider to develop and maintain software was a recurring cost that grew with every scaling need, with limited return compared to managing it internally.
Slow response times for changes: With every change going through the external vendor, minor deployments took up to seven days from request to delivery.
Reduced visibility into security and data handling: With systems managed externally, the client had less visibility and control over security standards.
No flexibility to evolve the product independently: With core systems under vendor control, the client lacked the flexibility to build new capabilities or integrate new tools and services without going through the vendor first.
Klika Solution
We reviewed the existing vendor implementation to understand its architecture, dependencies, and integration points, then designed a migration solution to integrate it fully within the client’s own infrastructure and tooling.
Full application migration: We migrated 32 backend services, 1 middleware layer, and 15 microfrontends into the client’s own environment, with no interruptions for end users.
Third-party services integration: We rebuilt the messaging and notification infrastructure using Active MQ for internal messaging, and Firebase for push notifications, replacing vendor-owned components with the client’s own implementations.
CI/CD and infrastructure setup: We set up deployment pipelines and infrastructure on OpenShift, giving the client full control over how and when they release changes, with a configured API Gateway managing all service traffic in one place.
Security improvements: As part of the migration, we introduced automated security scanning using Sonatype IQ and SonarQube across frontend and backend services, identifying and resolving 99% of previously undetected vulnerabilities.
The Results
The migration was delivered successfully and without any disruption to end users, giving the client full ownership of their core banking software for the first time.
Full autonomy over growth and scaling: The client can now build new capabilities, integrate new tools, and scale their systems at their own pace.
Long-term stability and strategic control: With core banking applications fully in-house, the client removed a critical external dependency and now controls the direction, costs, and future development of their own systems.
Faster time to delivery: What previously took weeks or days now goes live within hours, giving the client the ability to respond and release changes independently.
Security ownership and visibility: The client now manages security internally, with full visibility into risks and the ability to detect and resolve issues on their own terms.
Technology Stack
Quarkus, WildFly, JSF, Angular, Liquibase, Firebase, ActiveMQ, MSSQL, OpenShift, Helm, 3scale API Gateway, Sonatype IQ, SonarQube







