New projects
A paragraph about the problem is enough to start. We reply within two working days, usually with questions rather than a quote.
Retrieval over your own data, tool access through MCP, and an evaluation suite so you can prove the thing behaves before it ever reaches a customer.
Language models are the easy part. The work is everything around them: retrieval, permissions, measurement, and cost.
Agents that hold state across steps, hand work to each other, and retry without duplicating side effects. Once there is more than one agent you are writing distributed systems again, so we treat it as one.
RAG that respects the permissions of the source system, cites what it used, and returns nothing rather than something plausible when the index has no answer.
A trace per run, a regression suite built from your real historical inputs, and a cost ceiling that trips well before the invoice does. Nobody should ship an agent they cannot measure.
Model work inside the product you already have — your auth, your data boundaries, your release process. No separate AI island that nobody can operate.
We design the permission boundary before the prompt, because the prompt is not a security control.
If the agent cannot call the tool, no instruction hidden in any document can make it call the tool. Scope is the control that holds; filtering the text is not.
Instruction-shaped text arrives in tickets, PDFs, web pages and commit messages. We test against it before the agent has anything worth attacking.
Anything that moves money, changes access, or sends mail on your behalf stops for a person. That is a product decision, and we make it explicitly.
Every tool call logged with the input that triggered it, retained long enough to answer the question you will eventually be asked.
Each one sets out what is included, how it is delivered, and the questions people ask before starting.
A paragraph about the problem is enough to start. We reply within two working days, usually with questions rather than a quote.
Engineers, designers and researchers who like systems that are hard to get right. Send something you built and what you would change about it now.
Based in India and working remotely, with overlap hours agreed up front so your team always has a time to reach us.
Guides on AI agents, RAG, MCP, tokenization and chain abstraction, written by the engineers who build them.