Kamiwaza is a software-only AI orchestration platform that enters the buyer conversation at Layer 2C and works downward. It is one of only two vendors in the instrument (alongside Articul8) whose primary product includes the reasoning plane. Where Articul8's Intelligence-2C focuses on mission decomposition and domain-specific agent routing, Kamiwaza's Intelligence-2C focuses on governance: cross-agent authority, relationship-based access control, and policy enforcement at execution time. The enterprise gets production-validated cross-agent governance that no other on-prem vendor provides independently.
The capture mechanism is governance-layer capture: a third pattern distinct from both coupled capture (data moves into the vendor's namespace) and decoupled capture (data stays open, proprietary opinion layer is captive). Kamiwaza's data stays in place, the infrastructure stays under enterprise control, and the enterprise feels free at the visible layers. What Kamiwaza captures is the authority to decide what the data means (the living ontology at Layer 1B) and what agents may do with it (the ReBAC governance at Layer 2C). These are arguably the most valuable layers to own, and the hardest to leave, because the ontology, relationship graph, and governance policies accumulate over time as proprietary Kamiwaza artifacts.
The gaps at Layer 0 (all three sub-layers), L1C and L2A are by design. A software-only vendor should not be at Layer 0. Kamiwaza's explicit 'no data movement' thesis means L1C absence is architectural, not accidental. L2A absence reflects that Kamiwaza orchestrates AI workloads and agents, not the underlying infrastructure. These gaps define Kamiwaza's scope, not its weakness.
The buyer's trade: production-grade cross-agent governance and distributed AI orchestration without moving data or committing infrastructure, in exchange for Ceding the governance and semantic layers to Kamiwaza's proprietary platform. The data is free. The understanding of the data is captive. A closed system is a closed system.
Kamiwaza's position in the instrument is structurally inverse to Dell's: Dell is strong at the bottom of the stack (0A to 0C) and absent at the top (L2C). Kamiwaza is strong at the top (L2C, L1B) and absent at the bottom (L0, L1C, L2A). HPE's Unleash AI program bridges the two: Kamiwaza as the Delegated Layer 2C partner on HPE's infrastructure substrate. That pairing is the only assessed combination that covers all eight layers with identified authority at each.
Layer-by-layer status: Layer 0A (Enterprise Responsibility), Layer 0B (Enterprise Responsibility), Layer 0C (Enterprise Responsibility), Layer 1A (Derived Artifact Layer), Layer 1B (Kamiwaza Differentiator), Layer 1C (Ingestion Through the Distributed Data Engine; No ETL, CDC, Lineage or Orchestration), Layer 2A (Enterprise Responsibility), Layer 2B (Kamiwaza Runtime), Layer 2C (Deterministic Enforcement, Partial Plane), Layer 3 (+1) (Platform + Kaizen).
Assessment framework: 4+1 Layer AI Infrastructure Model. Scoring model: Decision Authority Placement Model (DAPM) — Retained, Delegated, or Ceded. Published by The CTO Advisor LLC (DBA The Advisor Bench). Author: Keith Townsend. Date assessed: October 27, 2026. Version: v1.27 - 4+1 v3: Layer 0 Sub-Layers.
Kamiwaza is a software-only AI orchestration platform that enters the buyer conversation at Layer 2C and works downward. It is one of only two vendors in the instrument (alongside Articul8) whose primary product includes the reasoning plane. Where Articul8's Intelligence-2C focuses on mission decomposition and domain-specific agent routing, Kamiwaza's Intelligence-2C focuses on governance: cross-agent authority, relationship-based access control, and policy enforcement at execution time. The enterprise gets production-validated cross-agent governance that no other on-prem vendor provides independently.
The capture mechanism is governance-layer capture: a third pattern distinct from both coupled capture (data moves into the vendor's namespace) and decoupled capture (data stays open, proprietary opinion layer is captive). Kamiwaza's data stays in place, the infrastructure stays under enterprise control, and the enterprise feels free at the visible layers. What Kamiwaza captures is the authority to decide what the data means (the living ontology at Layer 1B) and what agents may do with it (the ReBAC governance at Layer 2C). These are arguably the most valuable layers to own, and the hardest to leave, because the ontology, relationship graph, and governance policies accumulate over time as proprietary Kamiwaza artifacts.
The gaps at Layer 0 (all three sub-layers), L1C and L2A are by design. A software-only vendor should not be at Layer 0. Kamiwaza's explicit 'no data movement' thesis means L1C absence is architectural, not accidental. L2A absence reflects that Kamiwaza orchestrates AI workloads and agents, not the underlying infrastructure. These gaps define Kamiwaza's scope, not its weakness.
The buyer's trade: production-grade cross-agent governance and distributed AI orchestration without moving data or committing infrastructure, in exchange for Ceding the governance and semantic layers to Kamiwaza's proprietary platform. The data is free. The understanding of the data is captive. A closed system is a closed system.
Kamiwaza's position in the instrument is structurally inverse to Dell's: Dell is strong at the bottom of the stack (0A to 0C) and absent at the top (L2C). Kamiwaza is strong at the top (L2C, L1B) and absent at the bottom (L0, L1C, L2A). HPE's Unleash AI program bridges the two: Kamiwaza as the Delegated Layer 2C partner on HPE's infrastructure substrate. That pairing is the only assessed combination that covers all eight layers with identified authority at each.
CPUs, accelerators, servers, integrated systems, OS and hypervisor, physical plant
Validated deployment target with dedicated .deb package. Kamiwaza runs on DGX Spark but does not provide or manage the hardware.
Whitepapers with Intel Gaudi 3 (DHS deployment, 85% analysis time reduction) and Ampere processors. Hardware partner validations, not hardware authority.
Kamiwaza provides no compute hardware, networking, or acceleration fabric. The enterprise brings its own infrastructure (on-prem servers, cloud instances, edge nodes, DGX Spark), and Kamiwaza runs on top of it. The platform is validated on NVIDIA DGX Spark, Intel Gaudi 3, and Ampere processors, but these are deployment targets, not owned hardware. The enterprise retains full responsibility for Layer 0. This is by design: a software-only platform vendor should not own the compute layer.
None to borrow. The enterprise supplies the hardware and keeps the substrate judgment. The reading is Absent: nothing offered, nothing inherited.
The DGX Spark integration includes a dedicated ARM64 .deb package with CUDA dependencies, suggesting meaningful optimization work for that platform. The Intel Gaudi 3 whitepaper (DHS deployment) and Ampere whitepaper demonstrate silicon-agnostic deployment: Kamiwaza runs on NVIDIA, Intel, and ARM compute without hardware lock-in.
Interconnects, switching and routing, network virtualization
Assessment pending
Kamiwaza AI Orchestration Platform ships no network fabric; the enterprise or its cloud provider supplies and runs it.
Nothing at this sub-layer is the vendor's to decide: Absent.
Arrays, storage servers and software, front-end protocols: where the data sits
Assessment pending
Kamiwaza AI Orchestration Platform ships no storage substrate; the enterprise or its cloud provider supplies and runs it.
Nothing at this sub-layer is the vendor's to decide: Absent.
The data itself, organized and governed: the Governance Catalog that Layer 2C queries
Metadata catalog for ingested documents and data assets. Tracks connector provenance, security markings, ingestion status. Proprietary catalog: metadata schema and query interface captive to Kamiwaza.
Document-level security classification enforcement. system_high clearance validation, default_security_marking per connector, X-User-System-High header validation at retrieval time. Designed for regulated environments (federal, healthcare, financial services). Proprietary security model captive to Kamiwaza platform.
Assessment pending
Kamiwaza does not govern the enterprise's source data stores. They remain in place under whatever authority already manages them. What Kamiwaza does provide is a derived artifact layer: the DDE ingests from source systems (S3, Postgres, Kafka, SharePoint, Slack, file systems) into Kamiwaza's own vector stores (Milvus/Qdrant) and application database (CockroachDB). The Data Catalog indexes metadata. The security markings system (system_high, X-User-System-High header, default_security_marking) enforces classification at the artifact level. This is a genuine 1A function: Kamiwaza creates and governs its own data artifacts, but it operates alongside the enterprise's existing data governance, not in place of it. Comparable to how Palantir's Ontology creates a governed semantic layer over open data substrates without replacing the underlying storage. The vector store substrate is open-source (Milvus, Qdrant): the data artifacts are technically portable. But the ingestion pipeline logic, connector configurations, chunking strategies, and security markings are Kamiwaza IP.
High for the derived layer, none for the sources. Source systems stay under their own authority; the DDE's ingest, the catalog and the security markings are Kamiwaza's, and the vector substrate underneath is open source the enterprise could swap. Decision authority (October 5, 2026): Security markings are configuration-defined with exact matching and no implicit defaults, and the default marking is set per connector, so the pipelines execute what the enterprise configured. Code decides, visible, overridable, Retained.
Supported sources as of v0.9.3: File, Amazon S3, Kafka, Postgres, Hive, Slack. The connector model is extensible: additional connectors available through support agreements. DDE connector APIs are mounted under /api/dde/ with full CRUD, trigger, and document management. Rate limiting per connector and requester (HTTP 429 with Retry-After). Vectors live in Milvus ("from relational data in CockroachDB to vectors in Milvus," docs.kamiwaza.ai); a vector store serves retrieval, not the governed foundation, so it isn't scored at 1A. Qdrant isn't in Kamiwaza's docs. The Distributed Data Engine is documented as "a unified ingestion framework" (docs.kamiwaza.ai, 1.3.4), which moves data rather than storing or governing it, so it isn't scored at 1A.
Low-latency retrieval for RAG — vector/hybrid search, context windows
Automatically builds and maintains a knowledge graph across all data sources: entities, relationships, insights spanning organizational boundaries. No manual mapping or data centralization. Grounds AI in up-to-date enterprise context, reduces hallucinations. Proprietary ontology engine: the semantic understanding of enterprise data is captive to Kamiwaza. Documented in 1.3.4: the context manager routes uploaded documents and media into extraction and indexing, and agents populate and query a Graphiti-backed knowledge graph through the DDE MCP tool (add_knowledge, search_knowledge, get_memory).
The Distributed Data Engine's retrieval in the GA build, per Kamiwaza's 1.3.4 documentation: connector-driven pipelines push cleaned documents into the platform's vector stores, agents run grounded context search and retrieval through the DDE MCP tool (search_context, retrieve_context, agentic_search) and query the vector stores directly, and content keeps its connector's security markings in search and retrieval. The Retrieval Service API itself is job-based dataset access (inline, server-sent events, or gRPC over Filesystem, Amazon S3, Hive, Postgres, Kafka, and Slack adapters). Kamiwaza's retrieval orchestration: Ceded.
Assessment pending
Kamiwaza's primary product differentiator. The Context Manager automatically builds a living ontology across distributed data sources: a knowledge graph connecting entities, relationships, and insights that span organizational boundaries without manual mapping or data movement. The Inference Mesh routes LLM reasoning to data sources without moving the data, adding intelligence to retrieval without the security risk of sending internal data to public cloud APIs. The living ontology is the most architecturally significant 1B capability in the instrument alongside Palantir's Ontology. Both build a semantic layer over distributed data. The difference is architectural: Palantir pulls data into its namespace and operates the platform; Kamiwaza queries data in place and the enterprise operates the software on its own infrastructure. Both are Ceded: the semantic understanding is proprietary in both cases. The litellm fork on GitHub suggests open model routing for inference: Kamiwaza is model-agnostic at the inference layer, routing to whatever LLMs are available locally. This is a genuine differentiator vs. vendors locked to specific model providers. Open question: is the ontology exportable in an open format (RDF, OWL, JSON-LD)? If yes, the ontology data is portable even though the maintenance engine is captive. If no, both the engine and the accumulated knowledge graph are captive. This single fact would determine whether L1B capture is hard (nothing leaves) or soft (the snapshot leaves but the living maintenance doesn't). Either way, DAPM is Ceded: the ongoing ontology maintenance is proprietary regardless.
Total. The living ontology, the Inference Mesh and the retrieval service are Kamiwaza IP; the context assembled here runs nowhere else. The data stays put, which is the openness claim, and the ontology over it is the captive layer.
The Kaizen agent (v1.0) works across internal data sources through the Context Manager, drawing on information held across separate systems rather than a single repository. A skills library lets teams define what the agent can do and under which conditions. This is the L1B→L2B→L2C chain in action: retrieval (1B) feeds agent execution (2B) governed by policy (2C). Inference Mesh "adds large language model (LLM) reasoning to your data without moving it" (kamiwaza.ai/inference-mesh) by routing inference; it doesn't retrieve, embed or rank, so it isn't scored at 1B. 1B dependency audit (October 24, 2026): the Retrieval Service chip is corrected to the 1.3.4 documentation, which describes a job-based dataset-content API, not vector search; the 1.3.4 release notes list Milvus as an extension with no label and the Data Connector Builder as alpha. Re-read the same day on the DDE documentation, which "applies to the current GA build": connector pipelines into vector stores, grounded retrieval tools, direct vector store queries, and a Graphiti-backed knowledge graph, with security markings carried into retrieval. Strong holds. Graphiti is an open-source knowledge-graph framework, which bears on the cell's open question of whether the ontology exports.
Move/transform data — ETL/ELT, lineage, cost-aware movement, KV cache tiering
Kamiwaza's documented ingestion: it "aligns unstructured and tabular content under a unified ingestion framework," with connectors to files, S3, Kafka, Postgres, Hive, SharePoint and Slack, scheduled or one-time runs, and "Target storage (Kamiwaza vector database or an external store)." Connector logic and scheduling are Kamiwaza's: Ceded.
Assessment pending
Kamiwaza moves data in one way: the Distributed Data Engine ingests from files, S3, Kafka, Postgres, Hive, SharePoint and Slack into Kamiwaza's vector database or an external store, on schedules the enterprise configures. That is documented ingestion, a 1C function, and the grade rests on it. There is no general transformation, no change data capture, no lineage graph and no pipeline orchestration. The enterprise's Airflow and Spark keep doing that work. The product thesis is query in place ("Stop moving data. Start running AI where your data lives."), and it stays true: DDE lands data for retrieval rather than running the enterprise's data movement.
The engine executes the ingestion jobs the enterprise configures: decides code, visible, overridable, Retained. Portability reads Ceded, since the connector logic and scheduling are Kamiwaza's.
Lab-measured (Layer2C Lab 015, "Inherit the boundary. Own the gate."): two workrooms loaded through DDE's ingestion routes and restored with the pipeline force flag (about four minutes per workroom). Ingestion status was unreliable: a job reported "indexed" for a document with zero vectors, and a load reported complete into a collection the agent never reads. A load has to be verified by enumerating the store, not by reading the job's status.
GPU scheduling, quotas, RBAC, fair-share scheduling, utilization optimization
Assessment pending
Kamiwaza does not provision, schedule, or lifecycle-manage infrastructure. GPU scheduling, quota enforcement, VM lifecycle, cluster provisioning: none of this is Kamiwaza's domain. The enterprise's existing infrastructure orchestration (Kubernetes, VMware VCF, GreenLake, Run:ai) operates beneath Kamiwaza. The platform runs on Docker Swarm with Traefik, managed by Kamiwaza's own orchestration, but this manages Kamiwaza's internal services, not the enterprise's broader infrastructure estate. The enterprise retains full responsibility for infrastructure orchestration. Compare to VAST (Polaris manages the VAST fleet), VMware (VCF manages the entire estate), or HPE (GreenLake manages hybrid infrastructure). Kamiwaza has no equivalent: it is a tenant on the enterprise's infrastructure, not a manager of it.
None at the layer's function. Kamiwaza's own Swarm and Traefik manage Kamiwaza, not the enterprise's fleet. The reading is Absent: nothing offered, nothing inherited.
Kamiwaza v0.5.0 addressed 'GPU waste, job starvation, dependency conflicts', but this refers to managing Kamiwaza's own inference workloads on available compute, not infrastructure-level GPU scheduling across the enterprise.
Model serving, agent execution, inference APIs, distributed inference
Bounded collaboration spaces for teams and AI agents. Users and agents operate within existing permissions. Each Workroom contains its own data and tools available only to authorized users. Access boundaries enforced at the platform architecture level, not through manual policy changes. Proprietary runtime: execution model captive to Kamiwaza.
Configurable AI coworker that works across internal data sources through the Context Manager. Skills library defines what the agent can do and under which conditions. Multi-modal analysis and output. Expanded in v1.0. Proprietary agent framework captive to Kamiwaza.
Governed tooling platform enabling AI to access data and take action through controlled tools. Security enforced at the tool level: at execution time, AI can only perform actions the requesting user is authorized to take. ReBAC ensures permissions enforced when actions execute. Every action logged for audit. Proprietary governance model captive to Kamiwaza.
Ray Serve runs model serving and distributed work inside the Kamiwaza platform. Open source the enterprise could operate independently, though the Kamiwaza services layer that composes it is proprietary.
Assessment pending
Kamiwaza provides a genuine agent runtime: Workrooms (bounded execution environments with architecture-level access enforcement), Kaizen agent (configurable AI coworker with skills library), Tool Shed (governed tooling with ReBAC enforcement), and the Inference Mesh (local model serving). Chainguard-hardened containers provide attested infrastructure with SLSA Level 3 pipelines and verified SBOMs. What Kamiwaza does not provide is the broader model serving infrastructure: no NIM-equivalent optimized inference containers, no Triton, no KServe, no distributed training framework. The Inference Mesh serves models locally via Ray Serve, but the model serving story is thinner than a full 2B vendor like VAST AgentEngine or AWS Bedrock. The self-deploy model is notable: .deb packages for Ubuntu, .rpm for RHEL, MSI for Windows, macOS tarball. Enterprise Edition adds Terraform deployment. The enterprise operates the full platform on its own infrastructure with no Kamiwaza SaaS dependency at runtime. But self-deployable does not make it Retained: the runtime opinions are proprietary and captive. Authentication is built on Keycloak (open-source OIDC/JWT). RBAC policy is YAML-based. These substrates are open: the ReBAC governance layer above them is proprietary Kamiwaza IP.
High for the runtime, low for the substrate. Workrooms, Kaizen and the Tool Shed are Kamiwaza surfaces whose opinions do not lift; the container substrate is open source. The Community Edition is not a feature-equivalent exit.
Architecture stack: FastAPI gateway, Docker Swarm orchestration, CockroachDB (distributed SQL), Milvus/Qdrant (vector), etcd (service discovery), Ray Serve (model serving), Traefik (reverse proxy). The infrastructure substrate is heavily open-source: Python, React, CockroachDB, Milvus, Ray, etcd, Keycloak. The proprietary value sits in the Kamiwaza services layer that composes these into a governed platform. Out of the Infrastructure Substrate chip under the GA evidence table (October 24, 2026): CockroachDB, Docker Swarm, Traefik ("Istio or Greymatter for ingress and routing, depending on environment Identity provider integration for authentication Postgres as the persistent database"). Out of the Infrastructure Substrate chip by the bundle split (October 24, 2026): Milvus and Qdrant (vector stores, a Layer 1B function), Keycloak (authentication) and etcd (service discovery), components of the Kamiwaza platform rather than 2B runtime functions; CockroachDB, Docker Swarm and Traefik stay out under the GA evidence table.
Policy-driven placement and resource coordination — the Autonomy Layer
The ontology that determines what data means, how it relates across systems, and what policies apply, updated in real time across distributed sources. This is the governance foundation that the ReBAC layer and Tool Shed query to make authorization decisions. Proprietary semantic governance captive to Kamiwaza.
Constrains agent permissions based on relationship context, not just role. Emerged from production behavior: traditional RBAC breaks when autonomous agents cross department boundaries. Enforced at execution time with full audit logging. Proprietary governance model captive to Kamiwaza.
Determines which agents run, in what sequence, with what inputs, under what constraints. Enforces human-in-the-loop checkpoints. Manages agent lifecycle at the execution layer. Mission decomposition and decision authority placement. Proprietary agent governance captive to Kamiwaza.
Kamiwaza's governance and orchestration layer has no NVIDIA dependency. The platform is model-agnostic and silicon-agnostic at the reasoning plane.
Kamiwaza is one of two vendors in the instrument (alongside Articul8) whose primary product includes Layer 2C. They separate on the determinism rule: Both read moderate at Intelligence-2C; the determinism rule separates them within the grade, Kamiwaza on a deterministic mechanism at its upper edge, Articul8 on a probabilistic planner. Kamiwaza's Intelligence-2C is governance-first, and the center of gravity is a deterministic, code-based mechanism: the living ontology determines context, the ReBAC enforcement constrains agent actions at execution time, the Tool Shed governs what tools agents can invoke, and every action is logged for audit. Kamiwaza asks: 'may this agent act, on this data, under this policy?' That is control executing code outside the model: the kind the determinism rule rewards, structurally in the class of Palantir's interaction-time security. Town of Vail production evidence validates it across multiple agent types (accessibility auditing, document processing, fire detection coordination), with cross-departmental authority boundaries and human-in-the-loop checkpoints. Articul8's Intelligence-2C is reasoning-first: mission decomposition and domain-specific agent selection. That core is LLM-driven planning (probabilistic), which is why Articul8 sits lower in moderate under the determinism rule while Kamiwaza's deterministic ReBAC mechanism holds the upper edge of the same grade. The two are complementary in focus, but no longer at the same grade. Infrastructure-2C (where inference physically runs at request time): Partial for Kamiwaza. The Inference Mesh routes inference requests across available models and compute, which is adjacent to live placement. But the documentation frames this as locality-aware data access rather than multi-variable infrastructure placement reasoning (cost + compliance + latency + data residency simultaneously). Neither Kamiwaza nor Articul8 provides full Infrastructure-2C. Articul8 explicitly acknowledges this as the responsibility of hyperscalers and platform vendors. The RBAC-to-ReBAC evolution is architecturally significant. Traditional role-based access breaks when autonomous agents operate across department boundaries. Relationship-Based Access Control, which emerged from Kamiwaza's production behavior at Town of Vail, constrains agent permissions based on context, not just role. This validates the 4+1 model's claim that Layer 2C requires governance architecturally distinct from Layer 2A infrastructure RBAC. Compared by shape rather than roster: most vendors either ship no reasoning plane at all, or productize Intelligence-2C inside their own platform and cede that authority to themselves. Kamiwaza's distinction is not that it governs but how: cross-agent authority and ReBAC are governance-first rather than governance bolted onto an orchestration product, and the authority is Ceded to Kamiwaza in either case. Where it shows up inside another vendor's stack, that vendor's customers cede to Kamiwaza rather than to their platform vendor. Infrastructure-2C is unbuilt here and everywhere else on the instrument. Calibration (September 2, 2026): moderate. The determinism contrast with Articul8 ranks Kamiwaza above a probabilistic planner; it does not rank it with Palantir. Strong at 2C requires a reasoning mechanism or a complete Intelligence-2C plane (first-class agent identity, request-time gateway, registry, cross-agent orchestration, observability). Kamiwaza ships deterministic ReBAC enforcement, an ontology-backed governance layer and lifecycle governance, with no agent identity principal, no request-time gateway across runtimes and no registry in the cohort's sense. That is constraint and enforcement, the Salesforce description of moderate, executed deterministically.
Low, and Ceded to Kamiwaza. The governance mechanism the enterprise inherits (the living ontology, ReBAC enforcement, the Tool Shed, lifecycle governance) is Kamiwaza IP, and it is deterministic and code-based, not prompt-shaped: the authorization decisions are computed, not asked of a model. The relationship graph and governance policies accumulate over time as proprietary Kamiwaza artifacts that do not lift to another reasoning plane without rebuilding. The universal caveat still applies: the deterministic outcome-validator (did the decision achieve intent, under a graduated escalation policy) is absent here as everywhere, noted as universal rather than charged to Kamiwaza; live Infrastructure-2C placement is likewise only partial (the Inference Mesh's locality-aware routing).
Town of Vail deployment velocity: concept to first-phase production in three months. 20-30 additional use cases projected in first year. Additional use cases compose from existing primitives (decision flows, authority boundaries, governance constraints) rather than requiring new infrastructure. Economic model: fixed-cost infrastructure on the town's own solar/wind-powered data center: billions of tokens without variable cloud API costs. The Community Edition on GitHub provides a partial open-exit path, but it is not feature-equivalent to the Enterprise Edition (Workrooms, full ReBAC, Chainguard hardening). The Community Edition does not constitute a real escape hatch under the methodology's litmus test. To notes under the GA evidence table (October 24, 2026): Cross-Environment Evaluation (no owner doc or product page names a cross-environment evaluation capability).
AI-powered business capabilities — business logic, workflow automation
Configurable AI coworker with skills library. Multi-modal analysis and output. Works across internal data sources through Context Manager. The primary Layer 3 application Kamiwaza provides. Proprietary agent: captive to Kamiwaza platform.
Platform for discovering and deploying pre-packaged AI applications and services. Curated marketplace model. Deployment surface for enterprise and partner applications. Proprietary marketplace: captive to Kamiwaza platform.
Compliance automation, document processing, legal, HR, supply chain, sales acceleration, knowledge construction, smart cities. Templates and reference implementations, not packaged applications. Enterprise builds on these using Kamiwaza platform primitives. Not scored within this chip under the GA evidence table: the compliance, legal, HR and supply chain templates (the docs list further guides as "Coming Soon").
Assessment pending
Kamiwaza provides one first-party Layer 3 application: the Kaizen agent, a configurable AI coworker with a skills library, multi-modal analysis, and integration across internal data sources via the Context Manager. Kaizen is the primary user-facing surface for enterprise AI interaction. Beyond Kaizen, the App Garden provides a deployment surface for additional applications, and the Tool Shed enables governed tool composition. The use-case library is extensive: compliance automation, document processing, legal, HR, supply chain, sales acceleration, knowledge construction, but these are deployment patterns and templates, not packaged applications. Kamiwaza is primarily a platform vendor, not an application vendor. The analogy is closer to VMware (platform that enables enterprise-built applications) than to ServiceNow (application vendor with a platform). Layer 3 applications will be built by the enterprise's own teams or partners using Kamiwaza's platform primitives. The HPE Unleash AI partnership positions Kamiwaza-built applications (ARIA accessibility agent, deed restriction processor, fire detection coordinator) as reference implementations: proof points for what the platform enables, not the platform's Layer 3 offering. Partner integrations: Dell + Intel Gaudi 3 joint solution, HPE Unleash AI program, DHS deployment. These are delivery partnerships, not ISV ecosystem depth comparable to Dell's (5,000+ customers, OpenAI/Palantir/ServiceNow) or HPE's (26+ Unleash AI members).
High for Kaizen and the App Garden, which are Kamiwaza applications; the templates and patterns are portable in kind. The delegation habits built up in Kaizen stay with the platform. Decision authority (October 5, 2026): Kaizen's model makes the call. An act-approval flow appears only in an SDK pull request, not product docs, so no gate counts yet. Model decides, not overridable, Ceded; a documented approval step would move it to Delegated. Visible on Kamiwaza's public post that every Kaizen step leaves an auditable trail (Keith, October 5, 2026: a vendor's public post meets the public-evidence rule); the product docs cover audit records for state-changing API operations.
$11M total funding over 2 rounds (seed, Jan 2025). Early-stage company. The partner ecosystem is nascent compared to established vendors: delivery partnerships with HPE, Dell, Intel rather than a broad ISV marketplace. Out of the Use Case Templates and Deployment Patterns chip under the GA evidence table (October 24, 2026): the compliance, legal, HR and supply chain templates (the docs list further guides as "Coming Soon").
Kamiwaza 1.0 launch (May 2026), Kamiwaza v0.9.3 docs, product pages, HPE Town of Vail whitepaper, Tracxn profile, SecurityBrief coverage, GitHub repos /reconcile (September 1, 2026): hard-coded peer-grade ledger replaced with a shape-based reading; the roster drifted from the rows it described and went stale on every peer move. /reconcile (October 5, 2026): authority visible set from the cell's own text where it settles it: layer1a true. Direction, grades, and components unchanged. /reconcile (October 5, 2026): authority re-read against product docs under the judgment test, override rule, and Layer 3 ruling: layer1a to code / Retained; layer3 to model / Ceded. Grades and components unchanged. /reconcile (October 5, 2026): Layer 3 visible null to true on Kamiwaza's public post (Kaizen steps leave an auditable trail); direction holds model / Ceded. Grade unchanged. v1.11 (Layer 0 sub-layers, October 16, 2026): Layer 0 split into 0A Compute, 0B Network Fabric and 0C Storage Substrate by runtime decision (Keith, October 16, 2026); storage left 1A for 0C, and 1A, now Data Foundation & Governance, is graded on the catalog that classifies the data. three gap cells carrying the row's Layer 0 authority; summary edits (summary worksheet, Keith, October 16, 2026). v1.12 (October 19, 2026, /reconcile): plain-language pass: methodology rule numbers in the prose and audit notes replaced with the reasoning they stood for; no grade, chip or authority reading changed. v1.13 (October 19, 2026, /reconcile voice pass): em-dashes in the prose replaced with periods, colons, commas or parentheses; wording, grades, chips and authority readings unchanged. v1.14 (October 22, 2026, /reconcile): the 1B authority triple gets the boolean visible it was missing (true: the assembled context comes back to the enterprise; the ontology's logic isn't overridable). Direction unchanged, Ceded. v1.15 (October 23, 2026, /reconcile): Layer 1 research pass. 1C: DDE meets 1C's purpose; a gap stands only where the function fails the layer. 1A: "Vector Store Substrate (Milvus / Qdrant)" removed (a vector store substrate is retrieval infrastructure, and Kamiwaza's docs name only Milvus ("vectors in Milvus"), not Qdrant). 1B: "Inference Mesh" removed (Inference Mesh "adds large language model (LLM) reasoning to your data without moving it" and routes inference; retrieval sits upstream of it). 1A: "Distributed Data Engine (DDE) Ingestion" removed (Kamiwaza documents DDE as "a unified ingestion framework," which moves data rather than storing or governing it). Found by the Layer 1 slot cut. Grade and cell authority unchanged. v1.16 (October 24, 2026, /reconcile): 1B Retrieval Service chip corrected to the 1.3.4 documentation, a job-based dataset-access API. Found in the 1B dependency audit under the headend standard. Grade unchanged. v1.17 (October 24, 2026, /reconcile): 1B re-read on the 1.3.4 Distributed Data Engine documentation for the GA build: connector pipelines into vector stores, grounded retrieval tools, and a Graphiti-backed knowledge graph; strong holds. Found in the 1B dependency audit follow-ups. Grade unchanged. v1.18 (October 24, 2026, /reconcile): GA evidence recorded on 2 of 2 Layer 1B chips under the GA evidence table. Grade unchanged. v1.19 (October 24, 2026, /reconcile): Layer 1B GA evidence migrated to the GA evidence table version 2. Grade unchanged. v1.20 (October 24, 2026, /reconcile): GA evidence recorded on 2 of 2 Layer 1A chips under the GA evidence table version 2. Grade unchanged. v1.21 (October 24, 2026, /reconcile): GA evidence recorded on 1 of 1 Layer 1C chips under the GA evidence table version 2. Grade unchanged. v1.22 (October 24, 2026, /reconcile): GA evidence recorded on 3 of 4 Layer 2B chips under the GA evidence table version 2. Grade unchanged. v1.23 (October 24, 2026, /reconcile): GA evidence recorded on 2 of 3 Layer 3 chips under the GA evidence table version 2. Grade unchanged. v1.24 (October 24, 2026, /reconcile): GA evidence recorded on 3 of 4 Layer 2C chips under the GA evidence table version 2. Grade unchanged. v1.25 (October 24, 2026, /reconcile): GA evidence table version 2.1 applied: 2 chips recorded or narrowed, 1 to notes. Grade unchanged. v1.26 (October 24, 2026, /reconcile): Layer 2 bundle split: Infrastructure Substrate narrowed to Ray Serve; the other components move to notes. Grade unchanged. v1.27 (October 27, 2026): each component now carries a durable offering id; nothing else changed.