← river42
PROD 01
Guide
Released

Guide.

An AI workspace for teams — grounded in your own knowledge.

Chat with frontier and open-weight models, with your team's documents, code, and policies as context. Hosted in the EU, isolated per customer, and built on Open WebUI. The model answers from your knowledge base — not the open internet — and that knowledge base never leaves your tenant.

guide.river42.eu · EU-hosted · OIDC SSO · per-customer isolation

02 In practice

Three ways teams use Guide.

Real deployment shapes from customers running today — each is one Guide tenant with its own isolated knowledge base.

UC 01

Software company · engineering

An assistant that has read your whole codebase and its history.

The team's handbook and source repositories sync into Guide every few minutes. Engineers and new hires ask questions in plain language and get answers grounded in the actual code — including why it looks the way it does, pulled straight from git history.

01Sync. Read-only access mirrors the team's handbook and service repos into the tenant on a short, configurable interval.
02Index. Full-text search plus a code graph for relational queries; git log, blame and pickaxe are first-class retrieval signals.
03Ask. Onboarding, code archaeology, and "is this still used?" questions answered without spelunking.

"When did MAX_RETRIES change in the billing service, who changed it, and what was the reasoning in the commit?"

UC 02

Professional services · operations

Plain-language answers over a contract and policy library.

A consultancy's document library — contracts, SOWs, internal policies, scanned reports — becomes searchable in natural language. Layout-heavy and scanned PDFs are OCR'd so the assistant can read tables and signed documents, not just born-digital text.

01Mirror. The document tree is pushed one-way into the tenant; removals propagate, so the KB stays current.
02Read scans. Ranked BM25 search over the indexed library; local OCR for clean scans, opt-in cloud OCR for tables and multi-column layouts.
03Cite. Answers point back to the source document and clause, so staff can verify before acting.

"Which of our active MSAs cap liability below 12 months of fees, and what's the exact clause in each?"

UC 03

Regulated enterprise · IT & compliance

The knowledge base never leaves the customer's network.

For organisations that cannot let documents leave their own infrastructure, the knowledge-base runtime stays on-prem. Guide reaches it over a private tunnel; the chat front-end is EU-hosted, the data is not. Access is gated by the customer's own SSO.

01On-prem runtime. The knowledge-base runtime runs on the customer's own hardware — reached over a private network tunnel or a TLS endpoint they publish.
02Isolation. One tenant group, scoped access grants; users outside the customer's group never see the model or its data.
03SSO. Sign-in via the customer's OIDC provider; sign-up is closed, membership is explicit.

"Summarise the change-control exceptions filed last quarter from the on-prem audit repository — without anything leaving our network."

03 Data

Where your data sits.

The reason Guide lives on .eu: data sovereignty is the product, not a footnote.

01

EU-hosted

The workspace runs on infrastructure in the EU. TLS terminates on our reverse proxy; nothing routes through a US control plane.

02

Per-customer isolation

Each customer is one tenant group with its own knowledge-base backend and scoped access grants. No shared index, no cross-tenant retrieval.

03

Your KB, your choice

Host the knowledge base with us, or keep it entirely on-prem and let Guide reach it over a private tunnel. The model reads it; it doesn't keep it.

04

Open models on request

Frontier models for capability, open-weight models when a workload must stay on infrastructure you can point at. Chosen per tenant.

05

SSO, closed sign-up

Authentication via your OIDC provider. Self-service sign-up is disabled; membership is explicit and auditable.

06

Open WebUI core

Built on Open WebUI — a familiar chat surface, not a bespoke black box, with the knowledge-base and isolation layers added by sysinit.

Bring your own knowledge.

Tell us the shape of your knowledge base — repos, a document tree, or an on-prem source — and we'll stand up a tenant.