Pricing — hosted public beta

Start with a useful question, not a long implementation.

Pantasso is a hosted public beta. Start with Files or Obsidian. Slack, Drive, Telegram, and GitHub need a connection. Every engagement begins with the sources you approve, the answers your team needs, and a clear definition of success.

Pilot

$1,500/mo

For a focused evaluation built around one useful company workflow.

  • Files or Obsidian first
  • A defined evaluation question
  • Cited answers with receipts
  • Source health monitoring
  • Direct onboarding support
Plan a pilot

Enterprise

$15,000+/mo

For organizations with dedicated security, compliance, and support requirements.

  • Custom connectors scoped in evaluation
  • SLA scoped in evaluation
  • SSO and audit logs scoped in evaluation
  • Dedicated support scoped in evaluation
  • Custom data retention scoped in evaluation
Contact Sales
Want to see the experience first? Explore cited answers with receipts using sample company data. View the live demo →
Read the buyer argument first: company context with receipts. Company context with receipts →
For ops, legal, and assistants that need the same governed record. Company context for ops, legal, and assistants →

FAQ

Plan the right first step.

How does an evaluation begin?

We start with a working session to choose one approved source, one important company question, and the evidence that will make the evaluation useful. In the hosted public beta that first source is Files or Obsidian; Slack, Drive, Telegram, and GitHub need a connection. We agree on scope, timing, and success criteria before setup begins.

How does billing work?

Pilot and Team engagements are billed monthly per workspace. Enterprise agreements are typically billed annually with terms shaped around the rollout. We confirm the commercial structure before any work begins.

What counts as a connected source?

A connected source is one approved endpoint Pantasso may read: a file set or Obsidian folder today, or a Slack workspace, Google Drive folder, Telegram chat, or GitHub repository after that connection is set up. Each counts as one source. Team does not include a full live connector suite.

What should we bring to the first conversation?

Bring one question your team regularly struggles to answer, the source most likely to contain the answer, and the people responsible for approving access. That is enough to shape a practical first step.

Bring Files or Obsidian and one real question.

We will help you turn them into a focused evaluation with clear success criteria.