Turning challenges into solutions

Integration, cloud and continuous delivery for companies whose critical systems cannot stop. No unnecessary replacements and no vendor lock-in.

Tell us about your challenge See a reference architecture

10+

Years of experience across our engineering team

47

Technologies in our stack

9

Middleware and API management platforms: TIBCO, IBM API Connect, ACE, MQ and DataPower, Apigee, Azure API Management, WSO2 and Kafka

Stack

The technologies we work with every day

47 technologies · 8 specialities

  • Cloud
  • AWS
  • Azure
  • GCP
  • IBM Cloud
  • DevOps & IaC
  • Terraform
  • Kubernetes
  • OpenShift
  • Jenkins
  • GitLab
  • GitHub Actions
  • Azure DevOps
  • Middleware
  • TIBCO BWCE
  • TIBCO BE
  • TIBCO EMS
  • TIBCO ActiveSpaces
  • IBM API Connect
  • IBM ACE
  • IBM MQ
  • DataPower
  • IBM z/OS Connect
  • WSO2
  • Apigee
  • Azure API Management
  • Kafka
  • Development
  • Java
  • Spring Boot
  • Python
  • .NET Core
  • Node.js
  • Liferay
  • Data
  • Oracle
  • SQL Server
  • PostgreSQL
  • MongoDB
  • MariaDB
  • Sybase
  • Databricks
  • Observability
  • Dynatrace
  • Grafana
  • ELK Stack
  • Prometheus
  • Calidad · QA
  • Postman
  • SoapUI
  • ReadyAPI
  • JMeter
  • Management
  • Jira
  • Power BI

The real problem

What holds a company back is almost never the technology

It is coupling. An ERP nobody dares to touch, point-to-point integrations that keep multiplying, deployments that need an overnight window and knowledge that lives in three people's heads.

Point-to-point integrations

Every new system multiplies the connections. With 6 systems there are up to 15 links to maintain.

Deployments with an overnight window

If deploying is scary, you deploy rarely. And the less you deploy, the bigger and riskier each change becomes.

Undocumented knowledge

An architecture that only exists in someone's head is an architecture that cannot be audited or evolved.

What we do

Four services, with the detail that matters

See all services
01

Systems Integration

APIs, events and middleware over your existing systems: your current technology gains agility without throwing away the investment you have made.

  • TIBCO BWCE
  • TIBCO EMS
  • TIBCO ActiveSpaces
  • IBM API Connect
  • IBM ACE
  • IBM MQ
  • DataPower
  • Apigee
  • Azure API Management
  • Kafka
How we do it
02

Cloud and Artificial Intelligence

Public, hybrid or multi-cloud with costs under control (FinOps), and structured data for AI agents to consume.

  • AWS
  • Azure
  • GCP
  • IBM Cloud
  • Terraform
  • FinOps
How we do it
03

DevOps

CI/CD, Kubernetes and Terraform with security built into the pipeline: faster releases and no manual errors.

  • GitHub Actions
  • Jenkins
  • GitLab
  • Azure DevOps
  • Kubernetes
  • OpenShift
  • Terraform
How we do it
04

Custom Software Development

Service-based, cloud-native software that another team can maintain and that gains value over time.

  • Java
  • Spring Boot
  • .NET Core
  • Python
  • Node.js
How we do it

Engineering pods

A multidisciplinary team for your technology projects, by the hour or as a dedicated team.

  • By the hour
  • Dedicated team
  • Spain and Latin America
Discover our pods
Technical guidesStep-by-step tutorials, admin cheat sheets and best practices based on industry standards: APIs, integration, cloud, DevOps, development, monitoring and AI. See the guides

Reference architecture · Examples by sector

Decoupled, event-driven architecture

No system calls another directly: it publishes events or exposes APIs with a contract. Choose a sector to see how we would apply it.

This is how we would apply it in a bank, where cores, satellite applications and memory grids coexist.

  • Existing systems, unchanged
  • What we build
  • New consumers

Channels

  • Online banking and app

  • Branches and contact centre

  • ATMs and POS

  • PSD2 third parties

    fintechs and aggregators

  • AI agents

    internal and customer-facing

HTTPS · OAuth 2.0 / OIDC · mTLS eIDAS

Exposure and security

  • API Gateway

    Versioned OpenAPI contracts, OAuth 2.0 and per-consumer quotas. A single entry point for every channel.

    Apigee · Azure API Management · IBM API Connect

  • Security gateway

    mTLS with eIDAS certificates (QWAC) for PSD2 and protection against XML and JSON threats.

    IBM DataPower

REST · gRPC · events

Events and integration

  • Event bus and CDC

    Every change is published as an event, and whoever needs it subscribes.

    Kafka

  • Microservices

    Small services, each with its own contract and data.

    Spring Boot · Kubernetes · OpenShift

  • Containerised integration

    Transformation and orchestration deployed like any other service.

    TIBCO BWCE · IBM ACE

CDC · change events

In-memory data

Memory grid · Kubernetes

Balances, positions and customer profiles, served from memory.

TIBCO ActiveSpaces · Red Hat Data Grid · Hazelcast

APIs · CDC · events

Cores and systems of record

  • Core banking

    accounts · loans · customers

  • Data lakehouse

    Databricks · data for AI

  • Cards

    real-time authorisation

  • Payments

    SEPA Instant · ISO 20022

  • CRM and onboarding

    SaaS · APIs

  • Risk and compliance

    fraud · AML · ML models

How it applies to each system

APIs · CDC

Core banking

Its operations, exposed as APIs; its changes, published to Kafka.

Kubernetes

Microservices

Spring Boot on Kubernetes: each service scales and is deployed independently.

Real time

Cards

Every authorisation is an event read at the same time by fraud prevention, notifications and the app.

ISO 20022

Payments

SEPA Instant with status events: every payment is tracked from start to finish.

Open banking

PSD2 third parties

APIs with eIDAS mTLS and OAuth 2.0, without exposing the core to the internet.

New consumer

AI agents

Permissioned data from the grid and the APIs, every query traced. Never the core directly.

Two flows, from the inside

Patterns we have built on Kubernetes.

Query with a memory grid

An API that responds from memory

  1. REST request at the API Gatewayby account · by document · by card
  2. API on TIBCO BWCEshared grid access module
  3. Is the data in ActiveSpaces?
  4. Yes
    1. JSON response from memorywithout touching the core
    No
    1. Query to the corevia API
    2. JSON response

Event conversion and distribution

One event, several consumers

  1. Authorisation eventevery card payment
  2. Kafka topic
  3. Enriching microserviceSpring Boot · Kafka Streams
  4. Consumer groupseach consumer at its own pace
  5. Fraud prevention Notifications App

If a consumer goes down, it resumes from its offset: no event is lost.

The decision, and what it costs

What you gain

Reads come from memory and changes travel as events. A new channel, or an AI agent, consumes a contract: it does not touch the core.

What you pay

Eventual consistency: data in memory may lag behind for a few moments. Whatever cannot tolerate that, such as instant payments, stays synchronous.

This is how we would apply it in an airline, where reservations, airports and operations need to share the status of every flight in real time.

  • Existing systems, unchanged
  • What we build
  • New consumers

Channels

  • Airline website and app

  • Airports

    check-in desks · kiosks · boarding

  • Agencies and distribution

    indirect sales

  • Partners and alliances

    codeshare · interline

  • AI agents

    customer service and operations

HTTPS · OAuth 2.0 / OIDC

Exposure and security

  • API Gateway

    Versioned OpenAPI contracts, OAuth 2.0 and per-consumer quotas. A single entry point for the website, the app, the airports and partners.

    Azure API Management

  • Container platform

    APIs and integration run on managed Kubernetes and scale automatically with sales or operational peaks.

    Azure AKS

REST · events · messages

Events and integration

  • Event bus

    Every change to a flight is published once and received by whoever needs it.

    Kafka on AWS

  • Integration APIs

    Services with a contract over the reservations and operations systems.

    TIBCO BWCE

  • Reliable messaging

    Guaranteed delivery for the systems that still communicate through queues.

    TIBCO EMS · IBM MQ

change events

In-memory data

High-availability memory grid

Availability, fares and flight status, served from memory to absorb query peaks.

TIBCO ActiveSpaces · Red Hat Data Grid · Hazelcast

APIs · events

Systems of record

  • Reservations (PSS)

    reservations · tickets · inventory

  • Departures and boarding (DCS)

    check-in · boarding

  • Flight operations

    scheduling · fleet · crews

  • Loyalty

    members · miles

  • Baggage

    bag tracking

  • Analytics and logs

    Databricks · data for AI

How it applies to each system

APIs · events

Reservations

Its operations, exposed as APIs; every booking change, published as an event.

Real time

Flight status

A delay or a gate change is an event received at the same time by the app, the airport and operations.

Memory

Availability and fares

Mass queries are served from the memory grid, without loading the reservations system.

Guaranteed delivery

Message-based systems

EMS and MQ connect whatever does not yet speak APIs, without losing a single message.

New consumer

Partners and alliances

APIs with their own contracts and quotas, without opening up internal systems.

New consumer

AI agents

They query flights and bookings through the same APIs, with permissions and every query traced.

Two flows, from the inside

Patterns we have built on Kubernetes.

Query with a memory grid

Availability that responds from memory

  1. REST request at Azure API Managementby flight · by date · by route
  2. API on TIBCO BWCEon Azure AKS
  3. Is the data in ActiveSpaces?
  4. Yes
    1. Response from memorywithout touching the reservations system
    No
    1. Query to the reservations systemvia API
    2. Response and grid update

Event conversion and distribution

One flight change, everyone notified

  1. Flight status changedelay · gate · cancellation
  2. Kafka topicAWS
  3. Enriching serviceflight and passenger data
  4. Consumer groupseach consumer at its own pace
  5. App Airport Operations

If a consumer goes down, it resumes from its offset: no event is lost. The logs end up in Databricks.

The decision, and what it costs

What you gain

A flight's status is published once and reaches everyone at the same time. Mass queries are served from memory, and a partner or an AI agent consumes a contract: it does not touch reservations or operations.

What you pay

Eventual consistency in queries: availability held in memory may lag behind for a few moments. Sales and ticket issuing are still confirmed against the reservations system.

Blog

What we learn on every project

Technical guides See the whole blog
  1. 30 Apr 2026 · Software Engineering Beyond the chat window: How self-employed agents are redesigning business operations
  2. 22 Apr 2026 · Innovation & AI AI-Ready Architecture: Don’t build for today. How to design infrastructure that protects your investment.
  3. 17 Mar 2026 · Innovation & AI Code that keeps promises: Why Spec-Driven Development is the end of uncertainty in large enterprises
  4. 9 Mar 2026 · Software Engineering The Cost of Inaction: How to Transform Legacy Systems Without Disrupting Your Operations

Contact

Do you have a system nobody dares to touch?

Tell us what you need and we will reply with a clear technical proposal, with no obligation.

Request information

Fields marked with are required.