Mission-critical systems that keep running while they evolve

Stories that show what our approach looks like once it reaches production.

Insurance · Galicia Seguros

New digital capabilities without replacing the platform

  • Legacy Modernization
  • APIs
  • Microservices
  • Core
  • CRM
  • Payment methods
  • Messaging
Legacy componentsCoreCRMPayment methodsChannelsAPIs and microservices
Legacy componentsCoreCRMPayment methodsChannelsAPIs and microservices
Conceptual diagram

APIs and microservices as a common layer: legacy components migrate progressively.

See context, scope and outcome
  1. The context

    Evolving digital channels and processes (claims, collections, policies, endorsements and self-service) within a complex ecosystem of systems and integrations, while legacy components remained in operation.

  2. What we did

    We developed and integrated APIs and services for business processes; integrated core systems, CRM, payment methods, messaging and digital channels; and progressively migrated legacy components toward API- and microservices-based architectures.

  3. What changed

    Functional evolution of channels and processes moved forward in parallel with technology modernization, adding new capabilities without requiring a full replacement of the existing platforms.

Have a system like this?

Let’s talk
Healthcare · Hospital Alemán

Two portals, one platform

  • Product & Platform Engineering
  • Legacy Modernization
  • Angular
  • Node
  • Microservices
  • OKD
  • Integrated monitoring
Member PortalPatient PortalWeb and mobile platformUnified Angular front endNode microservices on OKD
Member PortalPatient PortalWeb and mobile platformUnified Angular front endNode microservices on OKD
Conceptual diagram

One web and mobile platform: a unified Angular front end and Node microservices on OKD.

See context, scope and outcome
  1. The context

    Two portals, one for health-plan members and one for external patients, with different technologies, functionality and architectures, used by thousands of people.

  2. What we did

    We built a unified Angular front end, migrated the back end to Node microservices on OKD, added differentiated logic for members and external patients, and introduced integrated monitoring without interrupting the existing portals.

  3. What changed

    A single web and mobile platform in production that centralizes digital healthcare management for thousands of users with a consistent experience.

Have a system like this?

Let’s talk
Public sector · City of Buenos Aires · Finance

SIGAF evolves without ever stopping

  • Legacy Modernization
  • SIGAF
SIGAFBudgetAccountingTreasuryAssetsOperation
SIGAFBudgetAccountingTreasuryAssetsOperation
Conceptual diagram

The same modules evolve incrementally, without interrupting operations.

See context, scope and outcome
  1. The context

    SIGAF manages the City’s budget, accounting, treasury and asset processes. It is a mission-critical platform that must keep operating while incorporating new requirements from different government areas.

  2. What we did

    We provide corrective and evolutionary maintenance, incident resolution, improvements and new capabilities in coordination with the different areas of the City Government.

  3. What changed

    Operational continuity and incremental evolution, expanding SIGAF’s functional scope and strengthening its role in the City’s financial and asset management.

Have a system like this?

Let’s talk

More mission-critical systems we evolved without disruption

Mercel’s experience also includes call-center and branch platforms, member and plan management, integration buses for payments and transfers, patient portals and nationwide medication traceability.

  • Swiss Medical Group · SGINationwide call-center and branch platform.
  • Medifé · SUMEMember and plan management core integrated with CRM, electronic billing and ERP.
  • Western Union / Pago FácilService bus for payments, transfers and KYC.
  • Ministry of HealthNationwide 24x7 medication traceability.