Nexus

Private AI workspace.

Ask, search and work with your organisation’s knowledge — on infrastructure you control.

Recent conversations

4 of 1,284

Infrastructure exposure, quarter over quarter

Sovereign mode · 3 sources cited

12 min ago

Supplier contract — termination clauses

Sovereign mode · 2 sources cited

2 hours ago

Draft incident summary for INC-2418

Sovereign mode · 5 sources cited

yesterday

Access review — dormant accounts

Cost mode · 1 source cited

3 days ago

Knowledge

Engineering

3,204 documents · Engineering group

indexed 12 min ago

Legal and compliance

1,880 documents · Legal group

indexed 1 hour ago

Operations

2,015 documents · Operations group

indexed 26 min ago

Public material

1,313 documents · All staff

indexed 4 hours ago

How a request is handled

The path is fixed. What changes per request is which model the router picks at step five, and why.

Every request passes policy, protection and routing before a model sees it›

01

Your request

A person or an application inside the customer environment.

02

Data protection

Personal data and secrets are detected and removed before anything leaves.

03

Sailient Intelligence Layer

Policy, classification and context assembly.

04

Model Router

Selects a model by mode, cost, latency or sovereignty.

05

Selected model

A self-hosted model, or a provider permitted by policy.

06

Response

Returned with its citations and the audit record.

This quarter

Synthetic

Conversations: 1,284
Documents indexed: 8,412
Median latency: 640 ms

Volume roughly tripled over twenty days, which is the shape of a workspace being adopted team by team rather than all at once.

Chat

Ask, with the sources attached.

Answers carry the documents they came from. A citation you are not entitled to open is never produced.

You

Summarise the change in our infrastructure exposure over the last quarter, and cite the source documents.

Nexus Sovereign mode EU region

Exposure narrowed on two of the four tracked classes. Three findings drove the change: edge coverage improved after the agent rollout, two dormant administrative accounts were closed, and the transit link at site C remained the one unresolved item.

Q3-infra-review.pdf · p.14asset-register.csvSG-SEC-001 §4

Ask a follow-up…

Sovereign modeProtection on

Why this answer routed the way it did

Data classification

Internal — confidential

external providers excluded

Residency requirement

EU only

two candidates remained

Mode

Sovereign

self-hosted preferred

Selected

Self-hosted, EU region

Policy satisfied

Knowledge

Your documents, under your permissions.

Retrieval is filtered by the asking user’s own entitlements before context is assembled — not after an answer is written.

Bases

Engineering

Design records, runbooks, architecture decisions

3,204

Legal and compliance

Contracts, policies, regulatory correspondence

1,880

Operations

Procedures, asset records, change history

2,015

Public material

Published documents and website content

1,313

Permissions

How document-level permission is enforced›

Entitlements are applied at retrieval, so a document outside a user’s access never enters the context window. The alternative — filtering citations after generation — leaks the content into the answer and only hides the reference. That distinction is the reason permissions live in the retrieval path rather than in the presentation layer.

Models

One place decides, and records why.

The router picks a model per request against the policy in force, and keeps the reasoning with the audit record.

Modes

Quality

Highest scoring candidate regardless of cost

Cost

Cheapest candidate that clears the quality floor

Speed

Lowest latency candidate

Sovereign

Self-hosted or in-region only

active

Manual

An operator pins a specific model

Candidates

Share of routed requests

Self-hosted — EU

Customer region · 710 ms median

41%

Provider A

EU region · 480 ms median

33%

Provider B

EU region · 520 ms median · degraded

19%

Provider C

Outside EU · blocked by policy

7%

Usage

What it costs, and who spends it.

Metering is per team and per mode, so the cost of a routing policy is visible rather than inferred.

Last 30 days

Tokens: 48.2 M
Cost: € 1,940
Cache hit rate: 31 %

By team

Share of cost

Engineering

11,402 requests · 22.1 M tokens

46 %

Operations

6,880 requests · 13.4 M tokens

28 %

Legal

3,120 requests · 7.9 M tokens

16 %

Commercial

2,503 requests · 4.8 M tokens

10 %

Data controls

What may leave, and what never does.

The gateway decides before routing, not after. Each control below applies to every outbound request in its scope.

Gateway policy

Personal data detection

All outbound requests

enforced

Redaction before routing

External providers only

enforced

Secret detection

All outbound requests

enforced

Residency pinning

All modes except Manual

EU

Prompt and response retention

Audit trail

30 days

Training on customer data

All providers

never

Scope of this pilot

What is real on this page and what is not›

Real: the interface, the information architecture, and the request path, which follows the documented Sailient architecture. Keyboard navigation, focus states and reduced-motion support are implemented.

Not real: every figure, conversation, document and model statistic. There is no gateway running behind this page and no request is sent anywhere.