Deployment & pricing

Choose a pilot, a business rollout or a private deployment. Pricing is scoped to your data, users, infrastructure and support requirements.

Three engagement paths

Pricing is provided after scoping. No fixed subscription prices are published.

01 / Guided pilot

Pilot

Prove one business use case with a bounded knowledge domain.

  • One priority knowledge domain
  • Hosted deployment
  • Retrieval evaluation and tuning
  • Executive readout

A clear basis for a production decision.

Discuss a pilot
03 / Sovereign enterprise

Private

Align the platform with strict infrastructure and data boundaries.

  • Private, on-premise, or air-gapped
  • Local model integration
  • Security and audit alignment
  • Custom operating requirements

A deployment matched to your environment.

Plan your infrastructure
What shapes the scope

A proposal built around
your operating reality.

Agree the requirements that influence cost, implementation, and ongoing ownership.

Knowledge domains
Topics, document volume, update frequency, and retrieval complexity.
Infrastructure
Hosted or private deployment, data residency, offline operation, and local models.
Users & channels
Workspaces, public web chat, messaging integrations, APIs, and administrator roles.
Governance & support
Audit exports, retention, DLP, SIEM alignment, security review, and rollout support.
Before you decide

Questions from procurement,
IT, and risk teams.

Can we run iKB on our own infrastructure?
Yes. Deployment patterns include hosted, private cloud, on-premise, and air-gapped environments. The final architecture depends on your security and operational requirements.
Can we use our preferred models?
The model gateway supports hosted model providers and local OpenAI-compatible endpoints, with per-topic policies and usage controls.
How is answer quality evaluated?
Use your source corpus and representative questions, including adversarial cases. Inspect citations, evaluate retrieval, and tune the system before production rollout.
What does the pilot produce?
A deployment recommendation covering scope, governance settings, channel rollout, and operational ownership, supported by the evaluation findings.
What changes in an air-gapped environment?
Core ingestion, retrieval, and answering can run locally with local models. Features requiring live external sources or hosted services are not available inside the closed boundary.

Scope the right deployment.

Share your knowledge domain, audience, and infrastructure requirements. We will recommend an appropriate starting point.

Talk to our team