Book a demo Sign up
Kroolo Search · Smart Routing

Smart routing: the right model and engine for every question.

Smart Routing decides which model thinks and where each query runs, inside the user’s permissions and your budget. Better answers, lower cost, and a record of every decision.

Show written premium by region for the last four quarters, and flag anything unusual.
Data route
1Validate and check policyRead-only SQL · user may see these tablesAllowed
2Cache lookupNo fresh result for this entitlementMiss
3One source involvedSnowflake native adapter, run as the userNative
4Cost checkDry-run estimate against the tenant budgetIn budget
Model route
1Plan and write SQLStrongest reasoning modelFrontier
2Explain the resultMid-tier model, works from a profile not raw rowsBalanced
3Embed and rerankSelf-hosted open model, no external callLocal
4Log the routeModel, version, tokens and data classesAudited
Illustrative route for one question
3 modes
cost-efficient, balanced, frontier
one gateway, swappable providers
Policy first
checked before any source is contacted
Every route
recorded for audit
Model routing

The right model for each step.

Kroolo Search reaches models through one gateway, so providers and routes can change without touching agent code. You choose the trade-off; routing handles the rest.

Pick a mode per workspace: cost-efficient, balanced or frontier
Claude, GPT and Gemini behind one gateway, with open-weight models for private deployments
Zero-retention, no-training routes preferred, recorded per tenant
Every model change is tested against your golden questions before it ships
Task to model class
TaskModel classWhy
SQL generation and planningStrongest reasoning modelBiggest effect on accuracy
Summaries and explanationsMid-tier modelWorks from profiles and aggregates
Enrichment draftsMid-tier modelA person approves the output
Embeddings and rerankingOpen models, self-hostedNo external call for retrieval
Evaluation judgeStrong, separate modelKept apart from the generator
In-VPC and air-gappedOpen-weight models on vLLMUnder approved licences
Modes

Set the dial. You decide the trade-off.

One setting moves the whole workspace between lowest cost and strongest quality. Teams that need more can be set differently.

Cost-efficient
Mid-tier models wherever quality holds, the strongest model only where it matters.
Best for: Everyday search, summaries, high-volume teams
Weekly velocityQ4
Balanced
The default. Routes each step by task and difficulty to trade price against quality.
Best for: Most workspaces and analysts
Summarise open risks this week
Kroolo AI
2 risks are high: vendor delay and budget.
Frontier
The strongest reasoning model for every step of planning and SQL generation.
Best for: Hard analysis, risk and regulatory questions
Draft PRD for feature XDone
Assign new bugs to triageDone
Weekly status digestRunning
Data routing

Route the query, not the data.

Customer data stays in the customer’s platform. The router sends each query where it runs best, and moves data only when a join genuinely needs it.

Agent requestSQL with the user’s identity
Validateread-only · allowlist · row limit
Policy checkwhat this user may see
Routerpicks the cheapest safe route
1Fastest
Serve from cache
When
A fresh result exists for this user’s entitlements
Route
Return the cached result straight away
2No extra hop
Native adapter
When
Every object lives in one source
Route
Run in the source’s own dialect, as the user
3Pushdown
Federated plan
When
Objects span sources and stay within the cost budget
Route
Push filters and aggregates down to each source (Trino)
4Cost-capped
Join locally
When
Objects span sources but run over budget or without pushdown
Route
Extract the smaller side and join it in DuckDB
Arrow resultprofiled · cached for next time · written to the audit trail
Routing rules
ConditionRouteWhy
A fresh cached result exists for this user’s entitlementsServe from cacheFastest, and free of source cost
Every object lives in one sourceNative adapter, run as the userSource optimiser and governance, no extra hop
Objects span sources, within cost budgetFederated plan with pushdownFilters and aggregates run at each source
Objects span sources, over budget or no pushdownMaterialize the smaller side, join locallyCheap extract, joined in DuckDB
The user may not see an objectReject with an explanationPolicy runs before any source is touched
Guardrails

Fast routes need strict rails.

Every query is validated and costed before it runs. A bad route fails early, with a reason the agent can act on.

Statement allowlist
Only SELECT and WITH on the read path. DDL, DML and multi-statement strings are rejected.
NameValue
Acme IndustriesAnn HoActive
Paragon LabsClive BakerReview
Pioneer DynamicsKate WilsonActive
Object allowlist
Every table and column is resolved against the catalog and the user’s entitlements first.
Connect your dataDone
Build the viewDone
Share with the teamNext
Row and result limits
LIMIT is injected when absent. Models see a profile, not bulk rows.
Collect vendor quotesDone
Approve contract termsWaiting
Send to legalTo do
Cost estimate
A dry run estimates bytes or rows against tenant and per-query budgets.
Revenue by regionThis year
EMEA
APAC
AMER
LATAM
Timeout and cancel
Per-query timeouts and concurrency caps, cancelled at the source.
Connected sources5 live
Synced 2 min ago
Query tagging
Tenant, user, agent run and tool call IDs ride along on every statement.
Access, enforced at retrieval
Finance teamRead
Sales leadsRead, edit
ContractorsNo access
Quality gate

Routes are tested, not guessed.

Routing rules, prompts and models change only after they pass your own golden questions. Quality is measured per environment, not assumed.

1
Change proposed
A new model, prompt, context change or router rule.
Show payments by supplier class
Kroolo AI
Median payment is 41 days; 3 suppliers are late.
2
Golden questions run
30 to 50 reviewed questions per environment, growing over time.
Summarise open risks this week
Kroolo AI
2 risks are high: vendor delay and budget.
3
Compared with baseline
Retrieval, execution accuracy and dashboard quality.
Pipeline created, by monthThis year
Aug
Sep
Oct
Nov
4
Release gate
No regression beyond the margin, and zero safety violations.
NameValue
Acme IndustriesAnn HoActive
Paragon LabsClive BakerReview
Pioneer DynamicsKate WilsonActive
5
Watched in production
Feedback, drift and cost per answer, with alerts.
What every route records
WhoTenant, user, groups, agent roleIdentity
WhatTool, redacted parameters, SQL hashQuery
DecisionPolicy version, tier, cost estimatePolicy
OutcomeRows, bytes, duration, cache hit, cost actualResult
ModelModel, version, prompt template, tokensModel
Visibility

See what every answer cost.

Each route is recorded, so finance, security and platform teams can answer who used which model, on which data, and why it was allowed.

Model and version, token counts and data classes sent
Source, rows, bytes, duration and cache hit
Policy decision and approval reference
Per-tenant cost caps and budgets on top of source limits
Why Smart Routing

Quality where it counts, cost where it does not.

Task-aware model choice
Planning and SQL get the strongest reasoning model. Summaries and enrichment use mid-tier models.
Which deals will slip this quarter?
Kroolo AI
4 deals ($84k) have no activity in 14 days.
Three modes
Choose cost-efficient, balanced or frontier per workspace, and change it as needs change.
Pipeline created, by monthThis year
Aug
Sep
Oct
Nov
Query in place
Single-source queries run natively in your platform, as the user, with no extra hop.
Connected sources5 live
Synced 2 min ago
Policy before contact
Access is checked before any source is touched, and unknown objects fail early.
GR1Auth context enforcedCritical
GR2Source citation requiredHigh
GR3PII masked in outputMedium
Cost gates
Dry-run estimates and budgets stop an expensive query before it runs.
Revenue by regionThis year
EMEA
APAC
AMER
LATAM
Tested changes
Routing rules ship only after they pass your golden question sets.
Summarise open risks this week
Kroolo AI
2 risks are high: vendor delay and budget.

FAQs on Smart Routing

How is this different from picking one model?
A single model is either too costly for easy tasks or too weak for hard ones. Smart Routing chooses per step, so planning and SQL get strong reasoning while summaries use cheaper models.
Which models can it route across?
Claude, GPT and Gemini through one gateway, plus open-weight models for in-VPC and air-gapped deployments. Providers can change without touching agents.
Does routing change who can see data?
No. Policy is checked before any source is contacted, and queries run as the end user wherever the platform supports it.
What happens when a query would be too expensive?
The router dry-runs the query, compares the estimate with tenant and per-query budgets, and blocks it or asks for approval.
How do you know a routing change is safe?
Every change to a model, prompt, context or router rule runs against your golden questions first, with release gates for accuracy, safety and cost.
Can I see why a model or engine was chosen?
Yes. Each route records the model and version, source, rows, bytes, cache hit, policy decision and cost.

Route smarter with Kroolo Search.

See Smart Routing on your own questions in a demo.

Book a demoExplore Kroolo Search