What is KontextOS?
KontextOS is a course-led organizational diagnostic and context-management system. It helps an organization identify whether the knowledge, perspectives, policies, decisions, responsibilities, and operating conditions needed for successful AI adoption are complete, consistent, representative, and trustworthy.
How is the KontextOS diagnostic different from a conventional AI-readiness assessment?
A conventional AI-readiness assessment commonly evaluates technology, governance, skills, use cases, and organizational maturity before recommending initiatives or producing a roadmap. KontextOS examines the organizational context on which those decisions depend. It is designed to reveal conflicting perspectives, undocumented knowledge, unclear ownership, policy-practice gaps, hidden dependencies, and unsupported assumptions, then connect candidate findings to their supporting evidence and limitations.
KontextOS can complement a partner's existing assessment. The partner may evaluate readiness and recommend a transformation plan, while KontextOS helps the customer establish more reliable organizational context for those decisions.
What KontextOS offering can an organization evaluate today?
The Organizational Simulation demonstrates the KontextOS method with fictional organizational information. It allows an organization to experience the course-led diagnostic workflow, participant perspectives, evidence-to-findings process, human-review concepts, and simulated Executive Dashboard without submitting real organizational evidence.
The Private Diagnostic Appliance application and deployment package are now in early testing. KontextOS is preparing to open a limited number of bounded, partner-supported pilots using real organizational evidence. Pilot participation will depend on a verified customer-controlled environment, a supported deployment configuration, defined responsibilities and success measures, and definitive commercial terms. The PDA is not generally available and has no direct online checkout. Persistent KontextOS remains planned and partner-dependent.
Where does KontextOS run?
The Organizational Simulation is hosted by KontextOS and is limited to fictional organizational data. The early-testing Private Diagnostic Appliance and the planned Persistent KontextOS product are intended to operate in a customer-controlled environment rather than a KontextOS-hosted real-data environment.
A verified customer-controlled deployment may be on premises or in a customer-controlled cloud. Terms such as limited-egress, disconnected, sovereign, or air-gapped describe specific technical and operational conditions and should be used only when the delivered environment satisfies them. The word "private" by itself does not establish any of those conditions.
What are the minimum requirements for running the Private Diagnostic Appliance?
The final supported configuration and numeric CPU, memory, and storage minimums have not yet been established. The current planned baseline is one dedicated, customer-provided virtual machine or server running a supported Linux configuration and the supported container runtime. It must have sufficient persistent encrypted storage for the application, database, evidence, reports, and audit records, together with a customer-managed backup and recovery path.
The customer will also need a qualified administrator; an approved hostname, DNS, HTTPS certificate, required ports, and reliable clock synchronization; participant and administrator browser access over the approved network; and one KontextOS-approved AI provider and model. An external AI provider requires customer-controlled credentials and permitted outbound access to the approved endpoint. A local model requires separately documented compute and model capacity, which may be substantially greater than the base appliance requirements.
The installation preflight will need to verify the operating system and architecture, resources, storage encryption, network and proxy rules, certificates, AI configuration, backup plan, and responsibility boundaries. Kubernetes, enterprise identity integration, source-system connectors, and a GPU are not universal requirements for the initial appliance. No organization should purchase or prepare infrastructure against an assumed specification until KontextOS provides the supported configuration for the proposed pilot or release.
What does customer-controlled mean?
For a real-data PDA pilot, the customer will control the deployment environment, participant access, evidence permissions, privacy conditions, reviews, exports, retention decisions, and the AI-provider relationship. The precise allocation of responsibilities will be documented for the supported pilot deployment and applicable agreements.
Who configures and facilitates a diagnostic?
The customer is intended to configure, facilitate, and administer its own diagnostic cohort through the KontextOS workflow. The customer defines the scope, selects participants, establishes evidence permissions and privacy conditions, monitors participation, and supervises review of the results.
A partner may provide separately contracted facilitation, training, interpretation, or implementation assistance when the customer wants those services. Partner involvement does not automatically give the partner access to diagnostic content.
Can a KontextOS partner access participant responses or organizational evidence?
Not merely because it is a partner or installs the software. Partner access must be explicitly authorized by the customer, limited to an assigned purpose, and governed by the applicable privacy, confidentiality, security, and contractual requirements.
Installation should ordinarily require only the technical information needed to prepare, configure, validate, support, or remove the deployment. It should not require access to participant identities, responses, evidence, findings, reports, or AI interactions. Any exceptional access should be least-privilege, time-limited, logged, and removed when the authorized work ends.
Who owns organizational information and customer-specific results?
KontextOS's intended policy is that the customer owns the organizational information it contributes and the customer-specific context, findings, reports, maps, analyses, decision records, evidence collections, contextual datasets, and other organization-specific artifacts derived from that information, subject to rights that individual contributors or third parties may hold in materials they provide.
KontextOS retains ownership of its platform and preexisting intellectual property, including its software, course content, diagnostic methodology, prompts, schemas, templates, taxonomies, and general-purpose models and frameworks. When a customer-specific artifact uses a KontextOS template or framework, the customer owns its information and resulting organization-specific content, while KontextOS retains the reusable platform, template, and methodology.
Ordinary platform use should not be treated as authorization to use customer information for unrelated commercialization, benchmarking, model training, product improvement, or cross-customer analysis. Any such use would require explicit contractual authorization and appropriate privacy protections. Definitive customer agreements will control the legal ownership, access, licensing, retention, export, and deletion terms.
How does KontextOS approach security and privacy?
KontextOS has implemented or specified controls for consent management, privacy suppression, role-based access, customer-directed retention, controlled export and deletion, evidence fingerprinting, diagnostic audit events, backup, and rollback. The planned deployment model gives each customer a dedicated environment rather than placing multiple customers' real diagnostic data in a shared KontextOS-hosted environment.
KontextOS does not currently claim comprehensive security certification, independently validated appliance hardening, or a mature production incident-response program. Security representations for a real-data deployment must be based on the controls and evidence verified for that particular configuration.
How many participants are needed?
There is no universal minimum. An appropriate cohort depends on the population being examined and the strength of the conclusions the organization wants to support. A small number of leaders or subject-matter experts can provide useful key-informant evidence and candidate hypotheses, but that evidence should not be presented as workforce consensus or prevalence.
Broader organizational conclusions require appropriate participation, coverage, representation, evidence-source labeling, and disclosure of missing information. Supporting policies, workflows, decision structures, ownership records, and other authorized artifacts may strengthen the diagnostic. Human review, privacy screening, and explicit limitations remain important regardless of cohort size.
What does an organization receive?
The intended real-data diagnostic outputs include customer-reviewed, evidence-linked findings and reusable contextual assets. Findings should identify their supporting evidence, coverage, materiality, limitations, and possible remediation directions instead of presenting AI-generated conclusions as unquestioned facts.
The current Organizational Simulation demonstrates this approach with fictional evidence and simulated findings. Final deliverables for a paid real-data engagement will be defined when that offering becomes operational and the engagement is scoped.
What can happen after a diagnostic?
An organization may use approved findings to plan remediation, improve workflows and governance, clarify ownership, strengthen organizational knowledge, evaluate AI initiatives, or define implementation work. A customer may engage a KontextOS partner or another provider for consulting, integration, security, training, change management, or managed services. The customer remains responsible for choosing its service providers.
Persistent KontextOS is intended to provide a continuing workspace for approved evidence, findings, remediation history, contextual assets, and governance activities. That real-data product remains planned and partner-dependent.
Are partner services included in the software price?
No. The commercial model separates KontextOS software from professional services. Installation, integration, facilitation, remediation, training, managed services, and ongoing support must be separately scoped when needed. A partner is responsible for the services it contracts to deliver, including its staffing, deliverables, warranties, regulatory responsibilities, and service support.
How can an organization evaluate KontextOS?
An organization can request access to the free Organizational Simulation or begin a discussion about one of the limited PDA pilots expected to open after early testing. Simulation access is reviewed and organization-scoped. It is designed to demonstrate the method without accepting sensitive real organizational evidence. Pilot selection will require a suitable use case, customer-controlled environment, supported configuration, and agreed responsibilities.
Important notice
This FAQ explains the current product direction and intended responsibility boundaries. It is not a license, service-level agreement, security certification, guarantee of pilot selection, or promise of general availability. A definitive written agreement and verified deployment scope will control any paid real-data pilot or later engagement.
