The right model for the task
Auto reads the request and sends it to the model whose strengths fit that kind of work. It is a judgement, not a claim of perfection.
Rileva chooses the right model for every question—or brings leading models together with Council.
Powered by leading AI models
Whether you’re drafting complex prose, reasoning through code, or verifying facts with live citations, Rileva keeps your context, files, and thinking in one fluid flow.
Frame the release around one customer problem, support it with the strongest evidence, and keep the first commitment reversible.
Different models lead at different jobs. Rileva keeps track of their strengths and chooses an appropriate one for each question—without making you manage a stack of separate subscriptions.
Careful prose, tone, editing, and long-form thinking.
Structured reasoning, technical plans, and complex problem-solving.
Large documents, images, and mixed-format information.
Fresh web retrieval with sources you can inspect.
Direct analysis, alternative angles, and current topics.
Fast, fluent work across major European languages.
One subscription. One interface. The right model for the job.
Auto reads the request and sends it to the model whose strengths fit that kind of work. It is a judgement, not a claim of perfection.
Council asks three strong models the same question and writes one considered answer from where they agree and differ.
Projects hold chats, files and standing instructions together, so work that continues over days keeps its footing.
Rileva reads what you asked for and routes it to the model whose strengths fit that kind of work. It is a judgement, not a claim of perfection. You can lock a model or return to Auto at any time.
Just say what you need. No model picker, no prompt engineering, no settings.
It reads the request and judges which model's strengths fit it — careful reasoning, nuanced writing, live research, large files, or speed.
The best-suited model replies, and the answer always says who wrote it.
What is a multi-model AI router? Explain it in three short sentences.
A router reads each request and sends it to the model best suited to that kind of work. You get a sensible choice without switching providers yourself.
Now design the TypeScript architecture — streaming, fallbacks, idempotent retries.
Core invariant: every request is exactly-once deliverable — streamed once, or a deterministic fallback runs without duplication.
interface Router {
decide(req: ChatRequest): Promise<RouteDecision>;
stream(req: ChatRequest, id: RequestId): AsyncIterable<Token>;
}Council puts the same question to several leading models, then writes one clear synthesis: where they agree, where they differ, and Rileva’s conclusion. The full perspectives remain available to read.
The challenge verdict: don’t commit to the original recommendation as written. It overstates the shared evidence and treats several distinct risks as one decision.
Demand matters before scale. Test the premise with a small, reversible commitment.
A challenge round makes the hidden assumption visible. One perspective supports the direction; another shows where it could fail under pressure.
A technically sound idea can still fail when switching costs or adoption are underestimated.
The original recommendation is too compliance-centric. The stronger view ranks who pays, how fast, and whether the product is genuinely high-risk.
European delivery needs evidence that customers will convert before category timing runs out.
Rileva keeps the thread of your work — how you think, what you decided last time, the files and chats that belong together — so a question picked up weeks later starts where you left off.
Stuck on the pricing page again. Honestly a bit frustrated — it feels like we’re going in circles.
You’ve been here before. In March the onboarding rewrite stalled the same way, and what broke the loop wasn’t more options — it was choosing one audience and shipping the narrow version.
So let’s not reopen the tier debate. Pick the customer you already know pays, write the page for them alone, and leave the second plan out until that page converts. I’ll keep the rest of the thinking here for when you want it back.
Connections — in progress
Upload files and documents directly into any chat or project today. Direct connections for Google Drive, Gmail, and Google Calendar are currently in development.
These are the models Rileva can use right now. Auto chooses among them; you can also select one yourself.
Straight answers about how Rileva works, what it saves, and what it can reach.
Start in the browser. No setup, no model picker.