Questions, answered.

Rouva is built for small teams and solo developers who use AI APIs in their product or workflow and want the bill to stop being a mystery — typically anyone whose monthly AI spend adds up to more than the subscription costs, across providers such as Anthropic, OpenAI, and any others you use. If you need self-hosting or on-prem deployment, we're not that (yet) — Rouva is fully managed, which is the point.

Rouva doesn't log your conversations. Each request stores metadata only — token counts, cost, task type, and a quality score — to power your dashboard. If semantic caching applies, a short prompt preview and the cached response are kept so repeat questions can be answered instantly — and prompts that look personal or account-specific are automatically excluded from caching.

Yours. You connect your existing provider keys, and usage is billed by each provider directly to you at their standard rates — Rouva never marks up tokens. Keys are encrypted at rest with AES-256-GCM and only decrypted at request time.

Auto-routed requests fail over automatically: if a provider returns an error or is overloaded, Rouva retries with the next capable model from another provider you've connected, so your request still completes. And because you bring your own API keys, you can always call providers directly — there's no lock-in.

One lightweight classification step before your request is forwarded — classification results are cached, so repeat patterns skip it entirely. Responses stream straight through from the provider, and quality scoring runs after your response completes, never in the request path.

Nothing is lost. AI models don't hold your conversation between requests — every request is self-contained and carries the full transcript with it. Rouva forwards that complete history to whichever model it selects, translating provider-specific formats (like system prompts) so the new model sees exactly what the previous one did. Switching mid-conversation is seamless.

Conservatively. Savings are counted only when you explicitly requested a model and Rouva routed to a cheaper one that could handle the task: what the requested model would have cost, minus what you actually paid. Auto-routed requests record zero savings — we don't inflate the number against a hypothetical baseline.

Always. Pass a provider and model explicitly and Rouva forwards exactly that — routing never overrides an explicit choice. Auto-routing also respects a price ceiling: it will never pick a model more expensive than the one you asked for.

Barely. Install the @rouvanpm/rouva SDK, or point your existing HTTP calls at the Rouva gateway endpoint with your rva_ key. One integration covers every connected provider — the docs quickstart takes about two minutes.