Building Synapse: one schema for travel

From research lab to ecosystem

In 2017, I founded ElkanIO Research Labs with a deep‑tech focus—AI, analytics, and the discipline of turning messy, high‑variance data into reliable systems. That work pulled me into travel, where the problem is not a lack of ambition but a lack of architectural coherence. We evolved from experiments to infrastructure: a platform that lets travel companies scale without adding headcount to chase exceptions.

I build from Kochi. Not because it’s easy, but because it sharpened my bias for architecture over location. World‑class systems aren’t a postcode; they’re a set of design choices that make change safe and progress durable.

One schema, not one vendor

Synapse is our core: a unified model and API across verticals—flights, hotels, activities, insurance, visas, cabs, ferries, cruises. One schema does not mean a single product does everything; it means the truth is represented once, and every product in the platform—Nucleus (B2B), Nova (B2C), Orbit (corporate), Cluster (groups), and more—speaks the same language.

When the model is consistent:

• Reconciliation isn’t an afterthought; finance can see operational states without translation.
• Integrations don’t fork the truth; they adapt to a stable contract.
• New verticals plug in without re‑inventing identity, pricing, and settlement semantics.

Agentic self‑healing: the loop

Interfaces in travel break for ordinary reasons—schema drift, supplier outages, new edge cases. We designed an agentic loop so the core learns in production:

watch → propose → prove → promote → route

• watch: instrument the flows and detect anomalies
• propose: generate a candidate mapping or behavior change
• prove: test against recorded and synthetic data to verify correctness
• promote: roll out safely with guardrails and the ability to roll back
• route: choose the best supplier path given latency, price, reliability, and policy

This loop means the platform is not brittle. It gets better the more it runs.

Built in Kochi, built for the world

Being founder‑led since 2017 matters to me because it keeps the architecture honest. We don’t chase integrations as trophies. We design for the boring problems that consume teams: consistency, observability, and the ability to evolve without ceremony.

Kochi is where we write and ship, but the benchmark is global. Four hosting regions, enterprise controls, data residency, and a 99.99% SLA are features because architecture made them possible, not because a slide demanded them.

If you’re tired of the patchwork—tabs, scripts, rekeying—there’s another way. One schema. One core. A platform that watches, learns, and routes with intent. That’s Synapse.