The architecture behind the platform.
A single gateway schema for nine verticals, an agentic runtime that fixes supplier drift before it becomes a failed booking, and regional infrastructure that keeps data where the law says it lives.
Five layers, each replaceable, none of them magic.
A request enters at the edge, is normalised by the gateway, supervised by the agentic runtime, executed by independently scaled product services, and persisted in stores chosen for the job.
Edge
Regional ingress · WAF · DDoS mitigation · TLS 1.3
Synapse gateway
REST · OpenAPI 3 · authentication · rate limits · idempotency keys
Agentic runtime
Schema-drift detection · mapping patches · replay tests · supervised promotion
Product services
Booking · pricing · supplier · finance · CRM · analytics · loyalty, as independent services
Data
PostgreSQL for the transactional core · MongoDB for documents · Redis at the edge
What “AI-enabled” means here, step by step.
Not a chatbot. A supervised set of agents with narrow jobs, hard limits and an audit log, keeping supplier integrations working without waiting for a developer.
- 1
Watch
Every supplier response is diffed against its contract. Renamed fields, new enums and dropped elements are flagged in seconds.
- 2
Propose
An agent drafts a mapping patch with a confidence score and a blast radius: which fields, which products, which clients.
- 3
Prove
The patch is replayed against cached real traffic. Anything short of a full pass stops here and pages an engineer.
- 4
Promote
Passing patches ship behind a versioned mapping with one-click rollback. People are told what changed and why.
- 5
Route
Separately, search traffic is ranked per route by live latency and success rate, so slow suppliers stop costing look-to-book.
Built by engineers, for the engineers who will maintain it.
- A published OpenAPI 3 schema with Postman collections and typed client libraries.
- A sandbox with parity: the same mappings and agents as production, with simulated supplier responses.
- Granular webhooks for PNR changes, ticketing, policy issuance and payment events.
- Idempotency and retries designed in, so a network blip never double-books.
- A direct engineering channel for integration partners, not a ticket queue.
// Illustrative request shape. Field names follow the public OpenAPI schema.
import { Synapse } from '@elkanio/synapse';
const client = new Synapse({ apiKey: process.env.ELKANIO_KEY, region: 'in' });
const { offers } = await client.offers.search({
trip: { from: 'COK', to: 'DXB', depart: '2026-11-04' },
pax: { adt: 2 },
include: ['flights', 'hotels', 'insurance'],
});
const order = await client.orders.create({ offerId: offers[0].id, travellers, payment: { method: 'wallet' } });Commitments we put in writing.
Data residency
Hosted in your choice of region, India, Singapore, EU, Dubai, and kept there.
GDPR-ready
Consent management, anonymisation and right-to-erasure workflows are built into the platform, not bolted on.
99.99% SLA
Contractual uptime for the API gateway and portals, with scheduled maintenance notified 72 hours ahead.
Payments
Card data is handled by PCI-DSS compliant third-party gateways and tokenised; Elkanio never stores card numbers.
Ready for an architecture deep dive?
Bring your CTO. We will walk through the gateway, the agentic runtime, your residency requirements and the migration path from what you run today.