Company context with receipts

Ask a company question. Get a cited answer.

Pantasso is your SQL-first company knowledge base. Approved sources become operating context people and assistants can query. Answers come with citations, never a guess dressed as company fact.

Try the live demo See plans

What did we decide about the Q3 launch?

context_ready3 citations

The launch moved from August 12 to September 2 to clear the billing migration.¹ Scope was cut to the two flagship connectors; the analytics add-on shifts to Q4.² Priya owns the launch checklist, tracked in LNCH-42.md.³

Sources

decisions.mdFilesMaya R. · Jun 24

“Final call: launch moves to Sep 2 so billing migration lands first. No further slips.”

Q3-launch-plan.mdObsidianSection “Scope” · updated Jun 26

“In: flagship connectors A + B. Out: analytics add-on (defer to Q4).”

LNCH-42.mdFilesAssigned to Priya · open

“Own the launch checklist through Sep 2. Blockers escalate in decisions.md.”

Rendered from a sample workspace with synthetic data — this is the shape of every real answer.

Integrations

Files first. Other sources need a connection or are listed.

The hosted app starts with Files and Obsidian. Slack, Drive, Telegram, and GitHub can be connected. The directory lists more families; a listing is not a live connector.

Files and ObsidianSlackGoogle Drive and DocsTelegramGitHub

Browse all integrations

Your company already has the answer. In the hosted public beta, start with Files and Obsidian. Slack, Drive, Telegram, and GitHub need a connection. Pantasso finds the approved evidence and cites it.

Ask what the approved files cover. Your team and its assistants work from the same files-first context.

What Pantasso does

Turn approved files into trusted operating context.

The hosted public beta starts with Files and Obsidian. Slack, Drive, Telegram, and GitHub need a connection before daily messages or Drive records become company context.

Keep operating context current

In the hosted public beta, organize approved Files and Obsidian into current, source-backed context. Slack, Drive, Telegram, and GitHub need a connection before their activity appears.

Ask detailed questions

In the hosted public beta, ask about approved Files and Obsidian first. Slack, Drive, Telegram, and GitHub need a connection before those records appear in answers or views.

Control what each assistant can use

In the hosted public beta, give each assistant a scoped profile over approved Files and Obsidian first. Slack, Drive, Telegram, and GitHub need a connection before those sources can appear in a profile.

Cited answers with receipts

In the hosted public beta, every grounded answer from approved Files and Obsidian links to its records. Slack, Drive, Telegram, and GitHub need a connection. You can see the source, author, and time.

Start with files, then connect more

The hosted public beta starts with Files and Obsidian. Slack, Drive, Telegram, and GitHub need a connection. Other families are listed for later setup.

Scoped assistant context

In the hosted public beta, each assistant gets a scoped profile over approved Files and Obsidian first. Slack, Drive, Telegram, and GitHub need a connection. Assistants inherit the same citation rules; they do not unlock a finished action suite.

How it works

From scattered sources to trusted answers in four steps.

Start with one approved source.

In the hosted public beta, start with Files or Obsidian. Slack, Drive, Telegram, and GitHub need a connection. Pantasso reads only the source you approve. Other families stay listed until they are proven live.

Pantasso maintains company context.

In the hosted public beta, Files and Obsidian are the live first source. Approved files become governed company context that retains its source, author, authority, and time. Slack, Drive, Telegram, and GitHub need a connection before messages or Drive records appear.

Ask questions, get cited answers.

In the hosted public beta, ask about approved Files and Obsidian first. Cited answers trace back to those files. Slack, Drive, Telegram, and GitHub need a connection before their records appear in answers.

Give AI assistants safe context and approved workflows.

In the hosted public beta, create scoped agent profiles over approved Files and Obsidian first. Assistants cite those files. Slack, Drive, Telegram, and GitHub need a connection before their records become assistant context.

For developers

Ask the company knowledge base. Get cited JSON.

In the hosted public beta, Files and Obsidian are the live first source. Slack, Drive, Telegram, and GitHub need a connection before those sources appear in cited JSON.

TypeScript and Python SDKs, plus a CLI — all speaking to your Pantasso workspace from scripts, services, and CI.
Two response shapes, no surprises: context_ready with citations, or insufficient_context with an explicit gap report.
Agent tools speak the same contract, so assistants answer only from returned citations.

Read the docs

import { Pantasso } from "@pantasso/sdk";
import { searchCompanyWorkspace } from "@pantasso/company-workspace";

// Connect to your Pantasso workspace
const sdk = await Pantasso.connect({
  workspace: "acme-ops",
  apiKey: process.env.PANTASSO_API_KEY,
});

// Ask. The response includes citations
const result = await searchCompanyWorkspace({
  query: "What did we decide about the Q3 launch?",
});

result.retrieval.status;         // "context_ready"
result.retrieval.citations[0];   // { source_id: "file:notes/q3-plan.md", … }

Trust and governance

Know where every answer came from.

In the hosted public beta, cited answers start from Files and Obsidian. Slack, Drive, Telegram, and GitHub need a connection before those records appear in answers or audit. You can see who asked, which approved file was used, and when the evidence is missing.

Source-aware answers

In the hosted public beta, every grounded answer from approved Files and Obsidian links to its records. Slack, Drive, Telegram, and GitHub need a connection. You can see who asked and which approved file was used.

Private by default

In the hosted public beta, workspaces are isolated. Files and Obsidian are the live first source. Slack, Drive, Telegram, and GitHub need a connection. Sources are opt-in. No data leaves your workspace unless you export it.

Operator control

In the hosted public beta, workspace owners start with Files and Obsidian. Slack, Drive, Telegram, and GitHub need a connection before those sources can be granted to agents or included in the support boundary.

How we build

Built in the open, held to its own standard.

Pantasso is operated by DB Hurley and built primarily by AI agents working under his direction. The public beta publishes what we can prove: a synthetic demo, a files-first hosted workspace, cited answers with receipts, and founder-led first source setup. You won’t find invented logos, GA claims, or a finished connector suite here — just the receipts.

Security and trust Product docs

FAQ

Common questions about Pantasso.

What is Pantasso?

Pantasso is a hosted public beta. It keeps approved company context current so people and AI assistants can answer and work from the same source-backed evidence. Files and Obsidian are the live first source. Slack, Drive, Telegram, and GitHub need a connection.

How do I know an answer is trustworthy?

In the hosted public beta, every grounded answer from approved Files and Obsidian links to its records. Slack, Drive, Telegram, and GitHub need a connection. You can see the source, author, and time.

How is Pantasso different from a vector database or agent knowledge layer?

A vector database helps applications find similar content. In the hosted public beta, Pantasso starts with Files and Obsidian and returns cited answers with receipts. Slack, Drive, Telegram, and GitHub need a connection. Trusted records, controlled agent access, analytics, and backup are later platform work, not the day-one public beta.

What sources does Pantasso support?

Files and Obsidian are the live first source on the hosted app. Slack, Google Drive and Docs, Telegram, and GitHub need a connection. The integrations directory lists more families for later setup; a listing is not a live or GA connector.

Can I use my existing AI assistants with Pantasso?

Yes, in the hosted public beta. Each assistant gets a scoped profile. Files and Obsidian are the live first source. Slack, Drive, Telegram, and GitHub need a connection. The profile does not grant new source access by itself.

How does pricing work?

In the hosted public beta, Pantasso offers Pilot, Team, and Enterprise plans with founder-led onboarding. Files and Obsidian are the live first source. Slack, Drive, Telegram, and GitHub need a connection. Team does not include a full live connector suite. See the pricing page, then contact us to plan the first source.

Is my data private?

In the hosted public beta, workspaces are isolated by default. Files and Obsidian are the live first source. Slack, Drive, Telegram, and GitHub need a connection. Sources are opt-in. Support diagnostics are redacted before transmission. No workspace data is shared across organizations.

See a cited answer with receipts.

Pantasso is a hosted public beta. Explore the live demo of Files and Obsidian answers, then talk with us about the first source. Slack, Drive, Telegram, and GitHub need a connection.

Try the live demo See plans