HEANEXUS

Engineering status

Updated 2026-09-11. This page is the public version of our content truth matrix: lab-validated, EVT, alpha, and planned capabilities are strictly separated.

Legend

Data boundary principle

HEANEXUS is designed so that the local workspace and configuration remain on devices the user controls. When a user deliberately chooses a cloud model provider, the prompts and context required for that call are transmitted to that provider. We do not make unconditional claims such as "data never leaves the device" — the boundary follows the model form the user chooses, and is surfaced explicitly in the product.

Capability matrix

CapabilityStatusNotes
DSH runtime integrationLABLimited fixture validation passed; not a commercial release
USB delivery medium (hardware, T-001B)EVTNOT TESTED / DEFERRED; engineering sample, hardware validation not started
Local inference (vLLM + open models)LABEvidence from the owner's validation environment; not yet delivered as a HEANEXUS product capability
Local KB / offline product form (HEANEXUS Local)EVTEarly engineering validation; Alpha validation not yet complete
Host identity & credential foundationALPHAIn development (T-003 stage)
Provider credential secure persistent storageEVTProduction-grade secure storage not ready; development-stage approach only
Customer control plane (orders/entitlements/service)ALPHAIsolated dev environment, synthetic data only
Remote managed accessPLANNEDIn design; not integrated with real clients
Enterprise KB / RBAC / Ontology / auditPLANNEDDesigned into the architecture; not yet implemented in production
Windows / macOS clientsPLANNEDUnreleased
Payments & final SKUsPLANNEDPricing not announced

Current engineering progress (as of September 2026)

Directional milestones (not commitments)