Use case
AI Office
Your documents, email and meetings, understood on hardware reserved for you.
A knowledge assistant for the whole company that reads what your teams write on a single-tenant node, with one data-processing agreement and no shared tenancy.
AI Office · Feature 01
Retrieval over internal documents
Index wikis, drives, tickets, contracts and email, then ask questions in plain language. Every answer cites the passages it used and only draws on documents the asker is already allowed to open.
- Connectors for drives, wikis and ticketing
- Citations link back to the source
- Respects existing document permissions
AI Office · Feature 02
Meeting transcription
Live transcripts, summaries and action items for every meeting, processed on your dedicated node. Nothing is sent to a transcription vendor and recordings can be deleted by policy.
- Live transcript with speaker labels
- Summary and action items in minutes
- Retention policy per team
AI Office · Feature 03
Permission-aware access
Plug into your identity provider and the assistant inherits it. What a person can ask matches what they can read, group by group, without a second permissions system to maintain.
- SSO with SAML and OIDC
- Groups and roles mirrored from your directory
- Every query logged with the identity that made it
Use cases
Where AI Office goes to work.
Deployments customers run today. Each one starts on a single node and grows with the fleet.
Contract review
Legal hears that a supplier is being acquired. Counsel asks which agreements contain a change-of-control clause. The agent lists three, quotes each clause with the page it came from and flags that one requires consent within 30 days. The contracts were never uploaded anywhere; the agent read them on the company's own node.
HR policy assistant
Ben is on a plane at 06:00 wondering whether he can expense the hotel breakfast. He asks the assistant. It answers from the travel policy, quotes the paragraph and links the form. The next question about a colleague's salary is refused, because the assistant only sees what Ben is allowed to see.
Runbook search
The payment service is down at 02:00. The on-call engineer asks what was done last time. The agent returns the runbook, the ticket from March and the post-mortem, and highlights the step that fixed it. Nine minutes later the service is back and the agent drafts the incident timeline from the chat.
Reply drafting
A customer writes in angry about a duplicate charge. The agent reads the ticket history, finds the same issue from last month and drafts a reply with the refund steps and an apology in the company's tone. The support agent tightens one sentence and sends it. Nothing about the customer went to a third-party model.
Also included
Everything in the box
Retrieval over internal documents
Index wikis, drives, tickets and contracts. Answers cite the source and respect existing permissions.
Meeting transcription
Live transcripts, summaries and action items for meetings, all processed on the node.
SSO and role-based access
Plug into your identity provider. What a person can ask matches what they are allowed to read.
OpenAI-compatible API
Internal tools talk to the same assistant through the standard API on port 443.
Runs on
Supported nodes
AI Office runs as agents on these nodes. Models are served from a Node Cluster or an API you choose. Pick a node and deploy it with AI Office included.
Dedicated
Node One
Up to 50 Agents at once
one-time purchase25000000
Dedicated · 2U
Node Pro
Up to 250 Agents at once
one-time purchase45000000
Dedicated · 8U
Node Cluster
Hosts models up to 405B
one-time purchase750000000