A deployment quote you can understand.

Private AI pricing depends on the environment and the work. Sotaire scopes the implementation, infrastructure, software, and support separately so the cost drivers stay visible.

What a Sotaire quote separates.

No artificial “Custom” price cards. The quote shows the work, infrastructure assumptions, recurring platform cost, and optional scope as distinct lines.

One-time implementation and deployment work
Hardware or customer-provided infrastructure assumptions
Annual platform software and support
Optional integrations, resilience, or expansion scope
Milestones, acceptance criteria, and customer responsibilities
01
Commercial structure

Three stages, each with a concrete outcome.

The engagement progresses from definition to implementation to ongoing operation. Scope can expand without hiding what changed.

01Scoped quote

Scope + architecture

Before the deployment quote

Map the workflow, source data, users, security requirements, success criteria, and the customer environment.

  • Workflow and data-boundary brief
  • Capacity and integration assumptions
  • Security and responsibility matrix
  • Phased rollout recommendation
02Scoped quote

Deploy + validate

One-time implementation scope

Configure the platform, provision the agreed environment, connect the first sources, implement the workflow, and test acceptance criteria.

  • Dedicated deployment configuration
  • Source ingestion and retrieval setup
  • Workflow, agent, and review controls
  • Validation evidence and handover
03Scoped quote

Operate + expand

Annual software and support

Run the platform with agreed maintenance, support, tuning, and a clear path for new teams or workflows.

  • Platform updates and support
  • Operational review cadence
  • Retrieval and workflow tuning
  • Expansion scoped as needed
02
Cost drivers

What changes the quote.

These inputs matter more than a generic seat count. Early scoping makes the assumptions visible before implementation begins.

Teams + users

Number of departments, workspaces, roles, reviewers, and rollout locations.

Data footprint

Source volume, formats, OCR needs, metadata quality, retention, and ingestion frequency.

Model + capacity

Model mix, concurrency, latency target, GPU capacity, resilience, and storage requirements.

Integrations

Identity provider, document repositories, line-of-business tools, and approved external paths.

Control depth

Network segmentation, audit evidence, review gates, backup, recovery, and framework mapping.

Support model

Response targets, maintenance windows, training, tuning cadence, and named operational support.

03
Common starting scopes

Start at the size the workflow needs.

These are scoping profiles, not rigid plans. The final quote follows the actual environment and acceptance criteria.

Focused launch

One team, one high-value workflow

A department proving value on real operational data.

One primary document collection
Focused user and reviewer group
One validated workflow
Guided handover
Multi-team deployment

Shared platform, several controlled workflows

An organization expanding access while keeping role and data boundaries clear.

Multiple source collections
Directory-aligned roles
Several workflows or agents
Ongoing tuning cadence
Complex environment

Advanced capacity, integration, or operating needs

A large or regulated organization with multi-site, resilience, or bespoke control requirements.

Capacity and resilience design
Custom integrations
Detailed security review
Named support model
Pricing FAQ

Questions about scope and cost.

The practical details teams usually need before requesting a deployment quote.

Sotaire includes private hardware, deployment work, model choices, tailored agents, and support. We scope the environment first, then quote the tier that fits your organization.

Get a quote scoped to the real environment.

Bring the workflow, user groups, source data, integration needs, security requirements, and operating expectations. We’ll turn them into a visible scope.

Start with a 30-minute scope

Bring the workflow, the sensitive sources, and the review rules. We'll map the deployment boundary and next step.