NeuroChat is the chat workspace your whole company can use, running on the NeuroRoute gateway. Everything they already expect — documents, projects, artifacts, agents, web search, memory — with 59 models behind one picker, a per-person bill you can actually attribute, and conversations kept under a retention policy you set.
Everything your teams already expect from a chat assistant — documents, files, projects, agents — with the model choice, the bill and the data under your own control.
59 models across Anthropic, Vertex, Bedrock and DeepInfra sit behind a single entry in the picker. The router chooses per prompt, so nobody has to learn which model is good at what.
Every message is metered per person and per request, tagged for chargeback, and reported against a fixed baseline. A flat seat subscription cannot tell you which team spent what.
Conversations are kept only as long as you say — down to storing nothing at all — and content at rest can be encrypted under a key that lives in your own cloud project, which you can revoke.
Shipped white-label: your branding, your own domain. Not a co-branded tab inside somebody else's product.
Two screens carry most of the product: the composer, and the agent marketplace your own teams fill.
Graded as deployed today. “Others” is the shape of a typical single-vendor seat subscription, and it is strong on most of these rows — the gap NeuroChat is built to close is the last group.
| Area | Others | NeuroChat |
|---|---|---|
| Models and cost | ||
| Models | One vendor's own lineup, and only that | 59 models across Anthropic, Vertex, Bedrock and DeepInfra, behind one picker |
| Model selection | The person picks a model by hand, every time | Routed per prompt by task and strategy — a 48× cost spread measured across identical prompts |
| Cost visibility | None. A flat per-seat subscription with no per-use breakdown | Per-person, per-request metering, chargeback tags, org billing and savings against a fixed baseline |
| Working with content | ||
| Chat with documents | Standard | Live — retrieval over your own uploads, proven end to end |
| File generation | Usually via a code sandbox | Purpose-built: PDF, DOCX, PPTX and XLSX returned as attachments |
| Artifacts and canvas | Standard | Side-by-side artifacts for documents, code and diagrams |
| Projects and folders | Standard | Yes |
| Reading images | Standard | Upload a screenshot, diagram or scan and ask about it |
| Image generation | Standard | In build |
| Agents and automation | ||
| Agents | A large public marketplace | Agent builder plus an in-org marketplace, organised by department |
| Web search | Standard | Live — answers grounded in current sources, with the routing unchanged |
| Memory across chats | Standard | Live — context carries between conversations, under your own retention policy |
| Connectors and apps | Vendor-specific app SDK | Live over MCP with OAuth 2.1, so any MCP tool connects — not only ones on a vendor's list |
| Voice | Standard | In build |
| Scheduled tasks | Standard | In build |
| Identity, data and deployment | ||
| Identity and access | Vendor accounts, on the vendor's SSO terms | Your OIDC. NeuroRoute is the identity provider, with access gated per organisation |
| Data location and retention | The vendor's cloud, under the vendor's retention policy | Your retention policy, enforced per request — including store-nothing — with at-rest encryption under a key you can hold and revoke |
| White-label | Not possible | Shipped — your branding, on your own domain |
| Install on desktop and mobile | Standard | Installs as an app on desktop and mobile |
NeuroChat as deployed, September 2026. "Others" is the shape of a typical single-vendor chat subscription rather than any one product, and it is genuinely strong on the content and automation rows — the difference NeuroChat is built for is model choice, a bill you can attribute, and data that stays under your own policy. Where a row says Coming soon, the capability is in build and is not shipped today. Corrections welcome.
NeuroChat holds no separate user directory, no separate ledger and no separate policy engine. It is a client of the gateway, so it inherits all three.
NeuroChat signs people in through NeuroRoute over OIDC. There is no second user directory to keep in step, and no separate set of credentials to audit.
NeuroChat is a licensed add-on, enabled per organisation with an optional seat limit. Turn it off and the sign-in is refused at the identity layer, not hidden in the interface.
Chat traffic is not a separate ledger. It lands in the same usage events, budgets and request logs as everything else, so one invoice and one audit trail cover both.
PII policy, input and output guardrails, and per-key spend caps apply to a chat message exactly as they do to an API call — because it is the same pipeline underneath.
Three capabilities in build. None of them is needed to get value from NeuroChat today, and we would rather list them than let you find out later.
