Workspace-native intelligence

One chat. Every datasource. Documents, SQL, MCP tools, and dashboards — isolated per workspace.

Talk2data unifies retrieval-augmented generation, warehouse queries, Model Context Protocol servers, and saved analytics boards behind a single assistant. Each workspace is a hard boundary: vectors, rows, tools, and shares never cross tenants.

Create workspace Sign in

Self-host friendly: Postgres + pgvector, private S3, Auth.js, optional Resend for email. Enterprise SSO and fair plan tiers when you need to govern who sees which capability.

Intelligent chat hub

The same thread, every signal

Users should not juggle a “doc bot”, a “SQL bot”, and a “tools bot”. In Talk2data, one conversation can pull from uploaded files (RAG), approved warehouse tables, live MCP tools, and charts you pinned to dashboards — with the model choosing the right retrieval and tool calls from context.

Grounded answers

Citations from chunks and structured query results reduce hallucinations on numbers, dates, and policies.

Tool-aware

MCP exposes HTTP tools with schemas the model can call safely inside the workspace boundary.

Dashboard handoff

Promote tabular and chart outputs from chat into persistent dashboards your team can revisit and share.

How the platform fits together

Each capability is first-class and wired into chat — not a bolt-on integration. Together they form a single reasoning surface for operators, analysts, and knowledge workers.

Documents & RAG

Presigned uploads to your bucket, text extraction, chunking, and embeddings into pgvector. Search and generation are always filtered by workspace id so retrieved context cannot leak across tenants.

Folder organization, processing pipelines, and mentionable datasources in chat keep large corpora manageable. Insight scans help teams monitor the corpus for risk language and anomalies on a schedule.

Data sources & warehouse

Connect Postgres, cloud warehouses, and other drivers with encrypted configs. Table-level entitlements decide what chat and insights may reference — administrators stay in control.

Introspection feeds the assistant schema awareness; refreshable charts can re-run SQL when dashboards update so numbers stay aligned with the database.

MCP servers

Attach streamable HTTP MCP endpoints per workspace. Tools discovered from the MCP tools/list handshake become callable in chat with arguments validated against JSON Schema — ideal for internal APIs, ticketing, and custom actions.

Operators enable or disable servers, rotate headers, and inspect last sync errors without leaving workspace settings.

Dashboards

Build boards from chat outputs: charts and tables land in a responsive grid. Share links support workspace-only or external audiences with optional expiry and revocation.

Dashboards close the loop: exploratory chat becomes durable assets the team can open without replaying the whole thread.

Enterprise SSO

Configure Microsoft Entra ID or Google Workspace OAuth per workspace. Domain rules route the right users through your IdP; first-time sign-in can provision membership automatically. SSO sits alongside standard email and social login so you can roll out gradually.

Secrets at rest. API keys and connection configs use workspace-scoped encryption; LLM keys never appear in client bundles.
IAM & invites. Owners, admins, members, and viewers — plus audit logs for sensitive actions when you enable them.

Security & workspace isolation

Isolation is structural, not cosmetic. The data model keys documents, chunks, usage events, dashboards, connections, and MCP rows to a single workspace. Application code resolves entitlements before showing navigation or running tools — so plans can hide or disable entire surfaces consistently.

Hard tenant boundary

Queries and tool calls carry workspace scope end-to-end; there is no shared “global” corpus across customers.

Least privilege

Data source entitlements, share audiences, and role checks gate who can read, invite, or rotate secrets.

Operational transparency

Metrics and admin views show footprint (dashboards, MCP, SSO, warehouse links) per workspace for support and governance.

Fair pricing

Plans are expressed as capability templates: chat, documents, dashboards, warehouse, MCP, SSO, API keys, sharing, invites, and more. A workspace either inherits the platform default or an assigned tier; operators can layer a custom deal for one tenant without forking the product. You bring your own model keys, so inference spend stays transparent.

Start free Talk to us about enterprise

Ship a governed copilot for every team

Connect data, documents, and tools once — then let chat orchestrate retrieval, SQL, MCP, and dashboards under workspace isolation and SSO.

Create workspace Sign in