Plans for procurement-grade knowledge infrastructure

No catalogue prices on this page by design. Commercial terms mirror how you ingest, query, deploy and govern — so CFO, CTO, CISO and operations leads each find a legible tier without brittle unit economics that confuse committees.

Deployment tiers

Start where programmes begin today — we qualify sovereign isolation, residency posture and tenancy early when procurement makes it non‑negotiable.

Starter

Single initiative, bounded corpus

  • Governed ingestion and traversal for one squad or regulated line of defence.
  • Hands‑on onboarding to lock scope before data spreads.
  • Clear runway to widen sources after repeatable value.

Growth

Multiple departments sharing one substrate

  • Unified ontology lineage and departmental scopes on the same rails.
  • Identity patterns ready for wider roll‑out.
  • Coordinated releases with escalation paths baked in.
Recommended

Enterprise

Programme governance and resilience

  • VPC, private interconnect or sovereign adjacency aligned to policy packs.
  • Reviewer‑friendly documentation bundles for audits and questionnaires.
  • Named success rhythm for launches that cannot miss.

Sovereign and dedicated

Architected isolation for mission‑critical workloads

  • Joint design clinics with architecture and security owners.
  • Tailored tenancy stories for hardened or air‑gapped postures.
  • Procurement‑grade SLAs drafted with your sourcing team.

Every tier is quoted from ingestion breadth, concurrency, deployment topology and success coverage — seat counts rarely tell that story.

Capability comparison

Grouped for security, procurement and operations reviewers — shareable attachments for internal decks without retracing every marketing page.

Coverage and ingestion
CapabilityStarterGrowthEnterpriseSovereign and dedicated
Approved knowledge sourcesCurated connectors for bounded evidenceBroader corpus with change control checkpointsProgramme catalogue with departmental boundariesCustomer‑approved frontier with tenancy isolation hooks
Ingest pipelinesOpinionated normalisation tuned to pilot scopeParallel lanes for regulated vs general knowledgeReleases orchestrated alongside enterprise change windowsLanes that honour disconnected or segmented networks
Content lifecycleFocus on freshest pilot artefacts firstVersioning across BU boundaries without driftGlobal retention tiers with legal hold interplayPolicy packs matched to hardened environments
Retrieval, traversal and grounding
CapabilityStarterGrowthEnterpriseSovereign and dedicated
Semantic discoverabilityMeaning‑aware retrieval for anchored questionsConsistent boosts across departmental corporaProgramme‑wide synonym and policy overlaysCustom lexical packs for sensitive ontologies
Graph and multi‑hop traversalLight joins for investigative packsShared graph substrate for cross‑squad dossiersDeep joins with departmental compartment modelsPhysically partitioned graph paths available
Generative groundingOpt‑in guarded responses on pilot corpusModel routing with departmental policy hintsFull guardrail stack tied to ontology releasesArchitectures for models that cannot leave tenancy
Security and identity
CapabilityStarterGrowthEnterpriseSovereign and dedicated
Identity and SSOWorkforce auth aligned to pilot usersSAML‑ready federation across squadsSCIM choreography for large directoriesPatterns for segregated IAM estates
Encryption and transportIn‑transit and at‑rest defaults for SaaS perimeterKey rotation stories with shared servicesCustomer‑managed keys or HYOK‑style integrationsDedicated cryptography boundaries where required
AuditabilityTraceable ingestion and query logs inside the pilotExportable artefacts for departmental reviewsEvidence packs with lineage for supervisory dialogueAir‑gap friendly export routines
Compliance narratives
CapabilityStarterGrowthEnterpriseSovereign and dedicated
Data residency stanceEU‑aligned processing for introductory deploymentsResidency pledges surfaced for regional committeesResidency overlays matched to BU policyDedicated footprints negotiated with sourcing
Responsible AI artefactsDPIA and model card starters for pilotsCommittee‑ready dossiers reused across BUBoard‑visible governance packets per release waveEvidence aligned to national security overlays
Subprocessors and questionnairesCurated disclosures for introductory reviewsTemplate answers for departmental security desksFull transparency register with update cadenceCustom attestation rhythms for hardened buyers
Delivery and continuity
CapabilityStarterGrowthEnterpriseSovereign and dedicated
Success coverageGuided onboarding with weekly steeringNamed specialists through expansion wavesExec‑touch success planning for programme gatesJoint steering with architecture and sourcing
Operational resilienceStandard SaaS uptime with fair creditsHeightened patching collaboration windowsNamed maintenance slots and DR rehearsal hooksBespoke HA stories with failover drills
Support response targetsBusiness hours coverage for pilotsExtended coverage aligned to BU geographyPriority routing during critical filingsCustom severities with wartime escalation

Information here is indicative and evolves with our roadmap. It does not amend agreements or security commitments already under signature.

Trust without a rate card

We foreground what sceptical reviewers look for — not dollar anchors that mislead spreadsheets.

  • GDPR‑respectful processing narratives with accessible privacy artefacts.
  • Encryption in transit and at rest aligned to cloud baseline expectations.
  • Roadmap‑visible commitments toward ISO 27001, NIS 2 readiness and validated operating models — detailed alongside leadership materials.
  • European delivery ethos with facilitation on site when audits demand it.
  • Subprocessors and questionnaires published for repeat procurement cycles.

One page, multiple lenses

Modern buying committees argue before they agree. Each row below captures what tends to unblock their review.

We focus on regulated European institutions — composites and anonymised vignettes illustrate patterns, never guaranteed outcomes.

How commercial conversations start

When unit prices would mis‑scope the relationship, conversations centre on observable usage dimensions your teams already recognise.

  • Indexed corpus breadth, refresh latency and ingestion concurrency.
  • Query and agent concurrency with burst tolerances negotiated explicitly.
  • Deployment topology spanning shared SaaS, dedicated VPC and sovereign overlays.
  • Success coverage depth from guided pilots to jointly staffed programme offices.
  • Optional generative surfaces governed by ontology maturity and reviewer appetite.

You receive a scoped commercial summary after diligence — nothing on this page constitutes an offer.

Procurement objections we hear

Pricing and commercials FAQ

Why is there no public price?

Regulated procurements hinge on tenancy, lineage volume and reviewer obligations that vary order‑to‑order. Publishing anchors would distort internal business cases.

Can we anchor with a directional range later?

After diligence we share written commercial framing tied to mutually agreed workload assumptions — still without publishing static list prices externally.

Is there an unattended trial?

No — guided pilots protect your corpus and tighten security review. Trials are facilitator‑led from day zero.

What usage dimensions matter?

Indexed documents and media, ingestion throughput, traversal depth, concurrency for agents and reviewers, residency footprint and SLA tier dominate scoping worksheets.

How do pilots convert to broader programmes?

Pilots end with evidenced metrics, expanded ontology coverage and staged expansion waves so procurement can recognise each release gate.

Do you offer consumption and subscription blends?

Yes — hybrid envelopes are normal once baseline platform fees and optional burst envelopes stabilise budgeting conversations.

What about sovereign or air‑gapped footprints?

Sovereign and dedicated tiers start with architectural clinics. Commercials follow once isolation, data flow and staffing models are pinned.

How quickly can security teams get answers?

Security packets, subprocessors and control narratives are maintained for repeat diligence. Custom questionnaires slot into the same evidence base.

Who signs contracts?

Enterprise and sovereign tracks route through your vendor management function with legal and compliance counterparts on our side from the first workshop.

Can we start with a single department?

Starter exists for that exact pattern — it keeps governance tight while proving value before horizontal expansion.

Ready for a scoped commercial conversation?

Bring procurement, architecture and security leads — we co‑author the internal memo with you.

Subscribe to our Newsletter

Get 6 focused emails on digital intelligence, digitalisation, generative AI, and search in your inbox.