NexusIQ is a question-and-answer layer over your organization's own documents.
Find the answer without finding the file.
For the engineer chasing a decision made two years ago, the presales lead answering an RFP by Friday, and everyone who asks a colleague because search only hands back files.
Which authentication flow did we settle on for the partner API, and why?
The team settled on OAuth 2.0 authorization code with PKCE, because partner mobile apps cannot hold a client secret safely. Access tokens carry a fifteen-minute TTL and refresh tokens rotate on every use, so a replayed token is revoked server-side.
Generated from 2 retrieved passages. Nothing outside them was used.
Cited passages
- §3 · Decision
We adopt OAuth 2.0 authorization code with PKCE. Client credentials were rejected because partner mobile apps cannot hold a secret safely.
- p. 12 · Session handling
Access tokens are issued with a fifteen-minute TTL. Refresh tokens rotate on every use and are revoked server-side when a replay is detected.
- Runs on your servers
- The whole system installs inside your own network. A hosted option exists, but your own infrastructure is the default.
- AI on your own machines
- The models that read your documents and write the answers run on your hardware. Nothing is sent to an outside AI service.
- Every answer shows its source
- Each answer carries numbered references. Open one and the exact paragraph appears in the document it came from.
- Five languages, one product
- Every screen is available in English, Tiếng Việt, 日本語, 中文 and 한국어. Your team works in the language it already uses.
The answer exists. Reaching it costs an afternoon.
Three moments out of one ordinary week, in three different jobs. None of them looks like a search problem, and all of them end the same way: somebody asks a colleague, and the colleague answers from memory.
Engineering and PM
A new engineer asks which auth flow the team settled on.
The decision was made two years ago and written into an architecture record that sits in a repository nobody has opened since the handover. Three people answer from memory, one of them is wrong, and the flow gets re-argued in a meeting that did not need to happen.
Sales, presales and BA
An RFP lands on Tuesday and wants a comparable project by Friday.
The case study exists. It is a deck in somebody's shared folder, saved under a file name that never mentions the client's industry, next to a capability statement that answers the compliance question further down. Finding both takes longer than writing the response.
Everyone else
Somebody needs the current rule, not the forty-page policy.
The policy is on the intranet, it was updated in March, and the sentence they need is on page eight. They ask in the team channel instead and get an answer that was true last year. The same question comes back next month from somebody else.
And the obvious fix uploads all of it.
The usual answer to this is an AI service that reads your document store in somebody else's data centre. For a bank, a hospital or a defence supplier, that is where the evaluation ends. NexusIQ runs the index and both models inside your network, so the documents and the question never leave it.
Four jobs, four kinds of question
NexusIQ is used by whoever needs a fact out of the company's own material. Pick a role to see the question it gets asked and the answer it hands back.
They do not want the document. They want the one sentence inside it that settles the question, and proof that the sentence is the current one.
Can I expense a client dinner in Tokyo, and what is the limit per head?
Client entertainment is reimbursable when a line manager approves it in advance, and the cap in Japan is 15,000 JPY per head. A claim above the cap needs a written justification attached, or finance sends it back.
Generated from 2 retrieved passages. Nothing outside them was used.
Cited passages
- p. 8 · Client entertainment
Client entertainment is reimbursable when approved in advance by a line manager. The per-head cap is 15,000 JPY in Japan and 1,200,000 VND in Viet Nam.
- §2 · Above-cap claims
A claim above the per-head cap is accepted only with a written justification attached. Finance returns claims that arrive without one.
Four stages, all of them on hardware you control
A question does not go out to an external service. It runs through your own index and your own model, and comes back pointing at the passages it used.
- Step 1
Sources enter a notebook
Upload files, point at a URL to crawl, or connect a system you already run. A workspace also holds a shared library every notebook in it can draw on.
- Step 2
Chunking and embedding, in place
Each source is split into chunks and embedded by bge-m3 running on your hardware. Ingestion is asynchronous: a source is pending first, then indexed.
- Step 3
Semantic search, then reranking
A question runs semantic search across the notebook's private chunks and the workspace library, and the candidate passages are reranked before a word is generated.
- Step 4
Generation grounded in the retrieved passages
qwen3 writes the answer from those passages and streams it token by token. Each numbered citation opens the passage it came from in the document viewer.
That is the whole mechanism. A cloud-only product can match the first and last stage; it cannot run the middle two on your side of the firewall.
A chat reply is the floor, not the deliverable
The Studio turns a notebook's sources into something you can hand on: six output types, generated on demand from the same cited corpus.
- Editable in place
- An output is a draft you correct, not a black box you regenerate and hope. Fix the wording where it is wrong and keep the rest.
- Saved back as a source
- A finished output can be written back into the notebook as a new source, so the next question can retrieve and cite it.
Studio output types
Summary
Note
Data table
Mind map
Slide outline
Report
Point it at the systems your documents already live in
Sources arrive three ways. Google Drive connects today; the rest of the list below is coming soon. Whichever route they take, the chunking, the embedding and the index stay on your infrastructure.
Direct
- File upload
- URL crawl
Connectors
- Coming soon
- Coming soon
- Coming soon
- Coming soon
- Coming soon
- Coming soon
- Coming soon
Where it runs, who can see what, and what we will not claim
Enterprise buyers read landing pages defensively, so here is the part usually saved for a follow-up call.
Where it runs
Your network
Services, database, index and models all run inside your network. Document content never crosses the boundary, because nothing sits on the other side of it.
Hover, tap or focus any layer to read what it holds.
Who can see what
What we will not claim
Stated up frontThere are no benchmark numbers, customer logos, case studies or certification badges on this page, because none exist yet. Here is what else to know before a pilot.
- Bounded by a local model
- Cold starts are slow
- Studio outputs take time
- Indexing is not instant
Ask it a question from your own corpus
The honest evaluation is a notebook of your own documents, one real question, and a look at whether the cited passage actually says what the answer says.
- Your message reaches the NexusIQ sales team at Tinhvan Japan. No ticket queue, no auto-responder.
- A person who knows the product replies within one business day, in the language you wrote in.
- If it fits, we scope a pilot on your own documents before anything is installed.
Tell us what your team keeps looking for
A sales engineer reads every message. Describe what you are trying to find and where it lives today, and you get a specific answer back — not a brochure.