Models layer

AI stack · Models

The model is a choice, not a religion.

We pick the model per job, then settle where it runs, what it may see, and who signs the answer. A second model is cheaper than a wrong one.

Founded 2022 · Founder in the Salesforce MVP Hall of Fame · Dubai HQ · Kochi studio

  1. 01Models · Claude, Gemini, OpenAI, Bedrock
  2. 02Agentic systems · Agentforce, CrewAI, ADK, A2A
  3. 03Agentic memory · Neo4j, Cognee, IndyKite
  4. 04Automation and voice · n8n, Retell
  5. 05Deployment and governance · identity, evals, policy, audit

Choosing

One model for everything, or a model per job.

One model for everything

A model per job

Picked from a demo
Picked from your own examples
Every request at the top price
Easy work routed to a cheaper model
Hosting decided later
Region and data terms named before the pilot

Who picks the model

Three desks, three different models.

Typical choices, each made from the work rather than the demo.

  • Example

    Head of data, Riyadh consumer lender

    Today: Every team called its favourite model. Security cannot say which region holds customer data.

    After: Two or three candidates run your own cases, and the provider data terms are named in writing first.

    Banking and finance
  • Example

    Service lead, Dubai property manager

    Today: Every tenant message goes to the most expensive model, including the ones that only need a queue.

    After: Easy routing goes to a cheaper model or to Jev. The frontier model writes the replies that need writing.

    Property management
  • Example

    Operations lead, Kochi NBFC

    Today: Borrowers answer in Malayalam, and an English-first model hears noise.

    After: Sarvam hears the call in the borrower’s language, and the outcome lands on the loan record.

    Sarvam AI
Examples of the work, not case studies. Roles and cities are typical of the desks we see.

How we pick

From your examples to a model.

  1. Step 1

    Your examples

    Real cases from your desk, with the right answers marked.

  2. Step 2

    Two or three candidates

    Each runs the same set.

  3. Step 3

    Pass, cost, region

    The model that passes at a cost you accept, where your data may sit.

  4. Every change

    The set runs again

    A model update has to pass before it goes live.

Model selection as an evaluation, not a preference.

Questions

What buyers ask us.

Which model should we use?
The one that passes your evaluation set at a cost you accept. We test two or three candidates on your own examples before anyone commits, and we often route easy work to a cheaper model.
Can the data stay in our cloud or region?
Usually. Claude and other models run through AWS Bedrock or Azure in the regions they support, and Gemini runs on Vertex. We name the hosting region and the provider data terms in writing before a pilot starts.
Where does Jev fit?
Jev answers typed questions with a probability and never writes text. We pair it with the model that writes, so routing and scoring decisions are cheap, fast and logged.
Where does Sarvam fit?
When your customers speak Indian languages. Sarvam hears 22 of them, speaks 10 and reads documents in all 22. We connect it to Salesforce and keep Jev on the closed decisions. It has no Arabic, and its managed service runs in India.

The brief

Send the situation.

Name the process. We tell you which layer is missing. The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days.