Enterprise

Shared organization access for teams

Business covers 2–49 seats and Enterprise covers 50+ seats at $5/seat/month. The catalog is configured, but multi-seat checkout is not yet available; Ask Questions First remains optional, not an approval gate.

Quick actions
Review Reconnoiter AccessStart with the current $5 self-serve plan before evaluating organization-wide requirements.Open Open the crawlerReview the active Search + Web Crawler workbench and current product behavior.Open Discuss EnterpriseSend seat count, shared-resource, usage, security, and launch requirements to the support channel.Open Review docsCheck crawler, storage, RAG, export, and billing behavior before scoping a contract.Open
Enterprise foundation
Organization model

Business 2–49 seats · Enterprise 50+

Business and Enterprise are designed for governed organization workspaces rather than larger individual crawler allowances.

  • Owner, admin, and member roles
  • Central billing and seat management
  • Seat additions and removals
  • Organization-level access boundaries
  • Contract-defined usage and support
Discuss team access
Shared resources

One governed knowledge workspace

Authorized team members can work from shared organization resources while permissions, usage, and changes remain attributable.

  • Shared crawls and source collections
  • Shared documents and stored outputs
  • Shared pipelines and connector configurations
  • Shared vector indexes and RAG collections
  • Pooled credits and storage
Scope shared resources
Controls and evidence
Administration

Central permissions and credentials

Enterprise access must provide controlled sharing rather than exposing organization-wide resources or secrets to every member.

  • Scoped API keys and connectors
  • Role-based resource access
  • Centralized billing ownership
  • Usage visibility by workspace and user
  • Auditable administrative actions
Review security
Contract boundary

Explicit limits, never unlimited

Every Enterprise agreement requires defined usage, storage, provider pass-through, retention, support, and overage terms.

  • Licensed paid seat count
  • Contracted credits and storage
  • Explicit overage terms
  • Explicit provider pass-through costs
  • Optional dedicated infrastructure scope
Discuss contract scope
What to include

Team structure

Initial seat count, expected growth, administrator roles, member groups, and workspace boundaries.

Shared data

Sources, documents, crawls, pipelines, indexes, reports, and connector configurations the organization needs to share.

Usage and storage

Expected crawl volume, processing volume, RAG usage, API traffic, storage, retention, and model-provider requirements.

Security and launch

SSO or identity expectations, audit needs, compliance review, support requirements, pilot scope, and launch timing.

Status
Approved model is catalog configuredIndividual is 1 seat at $5/month. Business is 2–49 seats at $5/seat/month. Enterprise is 50+ seats at $5/seat/month. Multi-seat checkout is not activated in the application yet.
Enterprise capabilities require implementation gatesServer-side seat quantity enforcement, shared-resource authorization, pooled usage, role administration, webhook fulfillment, and audit reporting must be completed and verified before multi-seat activation.