Hosted
A managed starting point for a bounded pilot using representative knowledge and agreed review criteria.
Your operating boundary.
Your deployment choice.
Compare hosted, private cloud, on-premise and air-gapped iKB deployments. Review the model endpoints, connectors and external services each workflow needs.
How it supports the work
From the question to the next step.
- 01
Choose the environment
Begin with a hosted pilot or evaluate dedicated private-cloud and on-premise operation against your requirements.
- 02
Review external flows
Hosted models, business connectors and public research introduce external data flows. Check the actual endpoint and action configuration.
- 03
Plan for local operation
An air-gapped deployment uses local core services and models. Live web research and externally hosted services are unavailable inside that boundary.
Capabilities & controls
Explore deployment boundaries.
Private cloud
A dedicated environment for the organisation, with explicit model, connector and external-service configuration.
On-premise
Keep core services close to internal systems, with local model choices, capacity controls and operator-led installation and recovery.
Air-gapped
Operate the core knowledge experience using local infrastructure and models. Features requiring live external services are unavailable.
Architecture and controls depend on the deployment. Review source quality, permissions, privacy, model failure, retention and export behaviour against your own requirements.
Evaluate deployment boundaries with your team.
Bring representative sources, a useful business question and the controls your organisation needs.