Find us at Booth A2, Pavilion Hall
Come and talk through what you are building with the engineers who run the platform.
Built for Indian banks, NBFCs, insurers and payment companies running AI on regulated data.
The build guides are free and ungated, and useful whether or not you visit the booth.
What happens at the booth
You describe what you are trying to put into production and what is stopping you, and one of our engineers draws the build with you. You leave with a component list and a cost model you can check against our published rates — whether or not you ever become a customer.
Typical conversations: real-time transaction risk scoring and fraud detection in the payment path, credit underwriting and document intelligence over bank statements for lending and NBFC portfolios, claims triage in insurance, and KYC or collections workflows built on tool-calling agents.
Bring 01
The thing you are trying to ship. Transaction scoring, document intelligence, a collections agent, or something we have not thought of.
Bring 02
Decisions or documents per month, and the latency you have to hold. Rough is fine — it changes the architecture more than anything else you could tell us.
Bring 03
Whatever is currently keeping the project in a pilot. Bring it and we will work through the architecture with you.
Build guides
Written for the engineer who has been told to ship AI this year and has no MLOps team. Each one covers the decisions that matter, and what breaks in month four.
Written for AI and data teams at banks, NBFCs, insurers, payment companies and fintech startups in India.
Guide 1 · Payments
Transaction risk scoring, routing models and dispute triage — and what changes when a model sits in the authorisation path.
Guide 2 · Lending
Underwriting decisioning, document intelligence over bank statements and filings, and vernacular collections. Your own lending history is data no vendor can supply.
Guide 3 · Agents
Tool-calling agents for dispute triage, collections and internal research — and where the line sits between doing and proposing.
All three are free and ungated on purpose. If they are useful to you and you never speak to us, that is a fine outcome.
Book time at the booth
A few questions, so the engineer you meet has already thought about your problem before you sit down. We will come back with a time.
You do not need a finished spec. The volume and the constraint are the two answers that change the architecture, and a rough number for either is more useful than a precise one you had to go and find.
Booking, what to expect at the booth, and how to get the guides.
It is a whiteboard conversation, not a scripted pitch. You describe what you are trying to put into production and what is currently holding it in a pilot, and one of our engineers sketches the build with you.
Either works. Booking through the form on this page means the engineer you meet has already read your notes, so the fifteen minutes start with your problem rather than with introductions. If you would rather just come by, come by.
Engineers and solutions architects from the team. If a question turns out to be commercial rather than technical, we will introduce you to a colleague who can answer it properly instead of improvising.
No, and there is no expectation that the conversation leads anywhere. If you leave with a sketch on paper and we never speak again, that is a perfectly good outcome.
Nothing written. It helps if you can describe what you are trying to ship and roughly how much of it per month, but a rough number you already know is more useful than a precise one you had to go and find.
Yes, and it is worth doing. Fifteen minutes goes a lot further with the engineer and the person who has to sign the work off in the same conversation. Mention it in the form and we will make sure there is room.
That happens, and it usually means the conversation is worth having properly. We will arrange a longer call rather than overrun at the booth and keep the next person waiting.
Three short engineering write-ups — one on payments, one on lending, one on tool-calling agents. They cover the design decisions that matter early and the things that tend to break a few months in. They are written by the same engineers who staff the booth.
No. There is no form and no gate on the guides. They are useful whether or not you visit the booth, and whether or not we ever hear from you.