# HEOSSI

> Governed intelligence infrastructure for trust-critical systems.

Intelligence you can govern. Trust you can prove.

## Company

- Legal name: HEOSSI (PTE.) LTD
- UEN: 202532790K (Singapore)
- Incorporated: 2025-07-28
- Registered address: 552 Ang Mo Kio Avenue 10, #21-1982, Cheng San Place, Singapore 560552
- Website: https://www.heossi.com
- Press: press@heossi.com
- Machine-readable record: https://www.heossi.com/facts.json

## Released products

Each product publishes and cryptographically signs its OWN facts.json. The
figures below are read from those files, not restated from marketing copy, so
they cannot drift from what the products actually ship. Open the factsUrl and
check any of them.

### Bee by HEOSSI — The Progressive Quantum-Native Intelligence Engine

Bee by HEOSSI — The Progressive Quantum-Native Intelligence Engine. A specialist-intelligence platform uniting BSIS, multimodal AI, post-quantum assurance, and governed real-quantum-hardware execution for enterprise and high-assurance work. It is built by HEOSSI (Pte.) Ltd., a Singapore-incorporated company (UEN 202532790K). Six production tiers form the Intelligence Ladder (Cell → Brood → Comb → Buzz → Hive → Swarm), covering public access, professional reasoning, builder workflows, team operations, enterprise specialist intelligence, and high-assurance reasoning. Enclave adds private, regulated, and sovereign deployment. BSIS combines Bee's governed 96-domain specialist architecture, research, retrieval, tools, evaluations, safety, routing, and release control. Post-quantum cryptography (FIPS 203/204/205) supports signed evidence and Enclave Sovereign security paths; Bee's governed real-QPU execution architecture is progressing through its production activation gates.

- Site: https://bee.heossi.com
- Facts (signed, machine-readable): https://bee.heossi.com/facts.json
- As published: 2026-07-29T00:00:00.000Z (schema bee.facts.v2)
- 6 production tiers
- Package (npm): @heossihq/bee — https://www.npmjs.com/package/@heossihq/bee
- Package (pypi): bee-sdk — https://pypi.org/project/bee-sdk/
- Package (mcp): io.github.heossihq/bee — https://registry.modelcontextprotocol.io/
- Signature: ML-DSA-65 + Ed25519 (verified by HEOSSI against registry-pinned producer keys at 2026-07-30T08:14:03.002Z)

### QNSI

Quantum-Native Security Infrastructure

- Site: https://qnsi.heossi.com
- Facts (signed, machine-readable): https://qnsi.heossi.com/facts.json
- As published: 2026-07-21 (schema 3.3.0)
- 87 post-quantum algorithms across 13 families
- 7 compliance frameworks / 48 controls (mapped, not certified)
- Package (npm): @heossihq/qnsi
- Package (PyPI): qnsi
- Package (crates.io): qnsi
- Package (Maven Central): com.heossi:qnsi
- Package (go): github.com/heossihq/qnsi-public/sdks/go/qnsi
- Package (npm): @heossihq/qnsi-mcp
- Signature: ML-DSA-65 + Ed25519 (verified by HEOSSI against registry-pinned producer keys at 2026-07-30T06:14:42.030Z)

## Full solution catalogue

Stage is stated honestly. Most of these are NOT released; a list that implied
otherwise would be a lie a reader could check.

- BEE (bee) — The Progressive Intelligence Engine [stage: General Availability]
- QNSI (qnsi) — Quantum-Native Security Infrastructure [stage: General Availability]
- SIGQ (sigq) — Quantum-Enhanced Stock Market Prediction System [stage: Staging]
- Tunnel (tunnel) — Quantum-Safe Connectivity Fabric [stage: Alpha]
- DDIP (ddip) — Deterministic Development Intelligence Platform [stage: Alpha]
- QSIG (qsig) — Quantum Secure Interoperable Grid [stage: Development]
- IACC (iacc) — Industrial Autonomous Command Cloud [stage: Development]
- WAHH (wahh) — Blockchain Multi-Rails for Modern Finance [stage: Development]
- Profy (profy) — Modern Operating System for Finance & Compliance [stage: Development]
- Q-Risk-Engine (qrisk) — Quantum-Inspired Credit Risk & Fraud Engine [stage: Development]
- AIOS (aios) — Autonomous Interoperable Operating System [stage: Research]
- NIOS (nios) — Neural-Interface Operating System [stage: Research]

## Curated product use-case portfolio

50 representative scenarios: 25 QNSI and 25 Bee. Each product maintains a 100-case canonical library. These are evaluation patterns, not customer case studies, certifications, endorsements, or evidence that a customer deployment has completed.

### Assemble cryptographic evidence for a bank cyber-incident materiality decision

- Product: QNSI
- Sector: Banking & payments
- Canonical route: https://qnsi.heossi.com/use-cases/bank-cyber-incident-materiality-evidence
- Operational decision: Materiality and regulator clocks run while responders reconcile key logs, service ownership, data classifications, and contradictory timestamps from separate teams. Decision: What cryptographic assets, data paths, and business services were affected, and when was that known?

### Preserve authenticity of stablecoin reserve and reconciliation reports

- Product: QNSI
- Sector: Digital assets & fintech
- Canonical route: https://qnsi.heossi.com/use-cases/stablecoin-reserve-report-signatures
- Operational decision: Reserve, bank, ledger, and attestation files move through spreadsheets, object stores, and external firms where filenames and access logs do not establish content authenticity. Decision: Can a reviewer prove which system produced each reserve snapshot and whether the file changed after approval?

### Replace a PQC underwriting checkbox with measurable evidence

- Product: QNSI
- Sector: Insurance & asset management
- Canonical route: https://qnsi.heossi.com/use-cases/cyber-insurance-pqc-underwriting-evidence
- Operational decision: Questionnaires ask whether a company is quantum-ready but rarely capture asset coverage, unsupported dependencies, tested migrations, or accountable exceptions. Decision: Has the applicant identified material cryptographic exposure and funded a credible transition, or only adopted a policy statement?

### Determine cryptographic scope during a healthcare breach

- Product: QNSI
- Sector: Healthcare providers
- Canonical route: https://qnsi.heossi.com/use-cases/health-breach-crypto-scope
- Operational decision: Encryption status is often inferred from platform configuration even when exports, caches, backups, or accessible keys change the real exposure. Decision: Was compromised ePHI actually protected, were relevant keys exposed, and which records fall inside the incident boundary?

### Build the cryptography section of a medical-device premarket file

- Product: QNSI
- Sector: Medical devices
- Canonical route: https://qnsi.heossi.com/use-cases/medical-device-premarket-crypto-file
- Operational decision: Algorithm lists and architecture diagrams fail review when they omit key generation, update, recovery, certificate, third-party, and lifecycle evidence. Decision: Is every cryptographic claim connected to a design requirement, implementation, verification result, and residual risk?

### Prove provenance of transformed regulated laboratory records

- Product: QNSI
- Sector: Pharma & life sciences
- Canonical route: https://qnsi.heossi.com/use-cases/regulated-lab-record-provenance
- Operational decision: Middleware transformations can alter format or metadata without a durable cryptographic link to the raw record and approved software version. Decision: Can an inspector follow a result from instrument output through parsing, normalization, review, and final report?

### Transition cryptographic trust across an interagency API

- Product: QNSI
- Sector: Government
- Canonical route: https://qnsi.heossi.com/use-cases/interagency-api-trust-transition
- Operational decision: An API can be technically upgraded yet remain unusable because partner agencies depend on different certificate authorities, gateways, release cycles, and authorization packages. Decision: Which agency owns issuer trust, version negotiation, revocation, and failure response when algorithms change?

### Challenge a defense supplier's cryptographic assurance claims

- Product: QNSI
- Sector: Defense & national security
- Canonical route: https://qnsi.heossi.com/use-cases/defense-supplier-crypto-attestation
- Operational decision: Statements such as quantum-safe or FIPS validated can blur the product, module, firmware, operation, certificate owner, and deployed configuration. Decision: Which supplier claims are independently evidenced, configuration-specific, inherited, or still unqualified?

### Prepare incident evidence for a Singapore foundational digital infrastructure operator

- Product: QNSI
- Sector: Cloud & data centres
- Canonical route: https://qnsi.heossi.com/use-cases/singapore-fdi-incident-evidence
- Operational decision: A control-plane or key-service incident can affect many tenants, while evidence is fragmented across infrastructure, managed-service, and customer teams. Decision: Can the operator rapidly identify affected cryptographic services, supplied functions, customers, and containment actions?

### Find hidden cryptography in a SaaS dependency graph

- Product: QNSI
- Sector: Software & SaaS
- Canonical route: https://qnsi.heossi.com/use-cases/saas-dependency-crypto-inventory
- Operational decision: SBOM package names do not reliably reveal certificates, protocol defaults, bundled providers, transitive crypto libraries, or runtime configuration. Decision: Which libraries, runtimes, services, and managed dependencies will block a cryptographic transition?

### Verify network-function software before carrier rollout

- Product: QNSI
- Sector: Telecommunications
- Canonical route: https://qnsi.heossi.com/use-cases/telecom-network-software-signing
- Operational decision: Images pass through vendor portals, integrators, registries, and staging systems where a checksum copied beside the file is weak provenance. Decision: Does the candidate image originate from the approved vendor build and match the tested configuration?

### Constrain supplier remote-access trust in electric operations

- Product: QNSI
- Sector: Energy & electric grid
- Canonical route: https://qnsi.heossi.com/use-cases/grid-supplier-remote-access-trust
- Operational decision: Emergency vendor accounts and shared support certificates persist across substations and generation sites after the original work ends. Decision: Which supplier identity can reach which asset, for what task, using which credential and approval?

### Produce a pipeline cyber-incident evidence pack during operations

- Product: QNSI
- Sector: Oil, gas & pipelines
- Canonical route: https://qnsi.heossi.com/use-cases/pipeline-cyber-incident-regulatory-pack
- Operational decision: Responders must join corporate identity, vendor access, SCADA, field device, and key-management evidence without disrupting safety-critical operations. Decision: Which operational assets and cryptographic controls were affected, and what containment is safe while product continues to move?

### Expire vendor cryptographic access after water-system maintenance

- Product: QNSI
- Sector: Water & wastewater
- Canonical route: https://qnsi.heossi.com/use-cases/water-vendor-connection-governance
- Operational decision: Integrators need rapid support access, but reusable certificates and shared VPN accounts remain active across multiple facilities. Decision: Does each vendor credential terminate when the approved service task ends?

### Find certificate concentration across an OEM supplier network

- Product: QNSI
- Sector: Manufacturing
- Canonical route: https://qnsi.heossi.com/use-cases/manufacturing-supplier-certificate-risk
- Operational decision: Component reviews are organized by part number, hiding shared trust infrastructure that can affect many models and plants at once. Decision: Which products and factories depend on a supplier root, signing service, or unsupported crypto library?

### Trace cryptographic evidence through automotive tier suppliers

- Product: QNSI
- Sector: Automotive & mobility
- Canonical route: https://qnsi.heossi.com/use-cases/automotive-tier-supplier-crypto-evidence
- Operational decision: OEM evidence breaks across tier-one modules, tier-two firmware, open-source libraries, and manufacturing provisioning. Decision: Which supplier component introduces each algorithm, key, certificate, or software signer into the vehicle?

### Preserve signature provenance for electronic cargo documents

- Product: QNSI
- Sector: Maritime & ports
- Canonical route: https://qnsi.heossi.com/use-cases/cargo-document-signature-provenance
- Operational decision: Bills, manifests, releases, and customs messages pass through carriers, banks, ports, agents, and platforms with different identity and archive systems. Decision: Can parties prove who issued, endorsed, transformed, and presented each cargo record?

### Modernize identity trust across an airline partner ecosystem

- Product: QNSI
- Sector: Aviation
- Canonical route: https://qnsi.heossi.com/use-cases/airline-identity-federation-agility
- Operational decision: Operational access spans employers and airports, while shared accounts and long-lived federation keys weaken revocation and attribution. Decision: How can crew, ground handlers, alliance partners, and contractors authenticate without permanent overbroad federation?

### Time-bound supplier remote diagnostics for rolling stock

- Product: QNSI
- Sector: Rail & public transit
- Canonical route: https://qnsi.heossi.com/use-cases/rail-supplier-remote-diagnostics
- Operational decision: Shared vendor certificates and persistent tunnels can outlive faults, contracts, staff, and fleet ownership. Decision: Can a supplier diagnose one fleet subsystem without retaining access to other trains or depots?

### Align IoT cryptographic support with the promised support period

- Product: QNSI
- Sector: IoT & smart cities
- Canonical route: https://qnsi.heossi.com/use-cases/iot-support-period-crypto-evidence
- Operational decision: A support promise can exceed certificate validity, cloud dependencies, component maintenance, and the device's ability to adopt safer algorithms. Decision: Can the manufacturer maintain keys, certificates, libraries, and update trust for the whole declared support period?

### Authenticate data from shared scientific instruments

- Product: QNSI
- Sector: Education & research
- Canonical route: https://qnsi.heossi.com/use-cases/research-instrument-signing-identity
- Operational decision: Shared facilities export files through vendor workstations and removable media that do not preserve trustworthy machine or session identity. Decision: Can a result be attributed to the correct instrument, configuration, operator, and acquisition session?

### Sign forensic evidence at every custody handoff

- Product: QNSI
- Sector: Legal & professional services
- Canonical route: https://qnsi.heossi.com/use-cases/forensic-chain-of-custody-signing
- Operational decision: Case tools record audit events but exports and inter-firm transfers can detach evidence hashes from identity, method, and custody context. Decision: Can every acquisition, copy, analysis, export, and transfer be linked to an authorized actor and unchanged content?

### Contain seller-app credentials in an ecommerce marketplace

- Product: QNSI
- Sector: Retail & ecommerce
- Canonical route: https://qnsi.heossi.com/use-cases/marketplace-seller-app-credential-isolation
- Operational decision: Broad API tokens and shared integration secrets turn a single plugin compromise into cross-merchant exposure. Decision: Can one compromised seller application be prevented from reading other merchants, orders, payouts, or customer data?

### Rotate streaming distribution keys without blacking out licensed audiences

- Product: QNSI
- Sector: Media & digital content
- Canonical route: https://qnsi.heossi.com/use-cases/streaming-distribution-key-rotation
- Operational decision: Multiple DRM systems, device generations, regions, and distribution partners create long overlap windows and orphaned keys. Decision: Can origin, CDN, packager, player, and partner trust change within rights and availability constraints?

### Govern credentials used by autonomous AI agents

- Product: QNSI
- Sector: AI & data platforms
- Canonical route: https://qnsi.heossi.com/use-cases/ai-agent-credential-lifecycle
- Operational decision: Long-lived API keys and shared service accounts let an agent's prompt or plugin compromise become broad infrastructure access. Decision: Which agent instance may call which tool, with what credential, data boundary, and expiration?

### Turn KYC exception files into a reviewable structured decision queue

- Product: Bee
- Sector: Banking & capital markets
- Canonical route: https://bee.heossi.com/use-cases/banking-capital-markets-structured-review
- Operational decision: Give compliance reviewers a bounded queue with cited source passages, explicit exceptions, and a retained approval trail.

### Answer questions across policy wordings and endorsements with traceable citations

- Product: Bee
- Sector: Insurance
- Canonical route: https://bee.heossi.com/use-cases/insurance-cited-knowledge
- Operational decision: Resolve coverage questions against the controlling policy text without hiding conflicting versions or unsupported conclusions.

### Turn prior-authorisation packets into a reviewable structured decision queue

- Product: Bee
- Sector: Healthcare
- Canonical route: https://bee.heossi.com/use-cases/healthcare-structured-review
- Operational decision: Extract the decision facts while keeping clinical judgement, source provenance, and human approval visible.

### Reconcile the complete history of research notebooks and analyses before acting

- Product: Bee
- Sector: Life sciences
- Canonical route: https://bee.heossi.com/use-cases/life-sciences-full-history-reconciliation
- Operational decision: Surface contradictory observations and protocol changes before a scientist or quality owner accepts a conclusion.

### Answer questions across discovery productions with traceable citations

- Product: Bee
- Sector: Legal
- Canonical route: https://bee.heossi.com/use-cases/legal-cited-knowledge
- Operational decision: Navigate large matter records while retaining document-level citations, access boundaries, and counsel review.

### Reconcile the complete history of inspection findings and remediation before acting

- Product: Bee
- Sector: Accounting & audit
- Canonical route: https://bee.heossi.com/use-cases/accounting-audit-full-history-reconciliation
- Operational decision: Connect findings, owner responses, evidence, and reopenings so closure decisions are not based on the latest note alone.

### Operate a bounded agent over tender evaluation records without surrendering approval

- Product: Bee
- Sector: Government
- Canonical route: https://bee.heossi.com/use-cases/government-bounded-agent
- Operational decision: Automate permitted preparation steps while preserving procurement controls, segregation of duties, and accountable sign-off.

### Answer questions across mission briefing corpora with traceable citations

- Product: Bee
- Sector: Defense
- Canonical route: https://bee.heossi.com/use-cases/defense-cited-knowledge
- Operational decision: Support time-sensitive analysis without collapsing classification boundaries or presenting generated text as authoritative evidence.

### Operate a bounded agent over security finding remediation without surrendering approval

- Product: Bee
- Sector: Software engineering
- Canonical route: https://bee.heossi.com/use-cases/software-engineering-bounded-agent
- Operational decision: Prepare and validate fixes within repository policy while leaving merge, deployment, and exception decisions to named owners.

### Operate a bounded agent over threat-report corpora without surrendering approval

- Product: Bee
- Sector: Cybersecurity
- Canonical route: https://bee.heossi.com/use-cases/cybersecurity-bounded-agent
- Operational decision: Enrich and route intelligence under tool and data constraints without allowing autonomous containment or disclosure.

### Review visual and recorded evidence alongside maintenance work orders

- Product: Bee
- Sector: Manufacturing
- Canonical route: https://bee.heossi.com/use-cases/manufacturing-multimodal-evidence
- Operational decision: Compare images, readings, and technician notes before recommending a maintenance action or equipment release.

### Reconcile the complete history of storm response logs before acting

- Product: Bee
- Sector: Energy & utilities
- Canonical route: https://bee.heossi.com/use-cases/energy-utilities-full-history-reconciliation
- Operational decision: Bring fragmented field updates into one evidence trail without overriding dispatch authority or safety procedures.

### Reconcile the complete history of vendor release evidence before acting

- Product: Bee
- Sector: Telecommunications
- Canonical route: https://bee.heossi.com/use-cases/telecommunications-full-history-reconciliation
- Operational decision: Expose dependency changes, unresolved defects, and approval gaps before a network rollout decision.

### Turn customer support conversations into a reviewable structured decision queue

- Product: Bee
- Sector: Retail & ecommerce
- Canonical route: https://bee.heossi.com/use-cases/retail-ecommerce-structured-review
- Operational decision: Classify disputes and obligations consistently while protecting customer data and retaining human escalation.

### Review visual and recorded evidence alongside supplier continuity assessments

- Product: Bee
- Sector: Logistics & supply chain
- Canonical route: https://bee.heossi.com/use-cases/logistics-supply-chain-multimodal-evidence
- Operational decision: Combine facility evidence, shipment records, and supplier statements before sourcing or continuity decisions.

### Review visual and recorded evidence alongside moderation appeals

- Product: Bee
- Sector: Media & publishing
- Canonical route: https://bee.heossi.com/use-cases/media-publishing-multimodal-evidence
- Operational decision: Evaluate the full appealed context while keeping policy references, uncertainty, and final editorial judgement visible.

### Answer questions across course and assessment corpora with traceable citations

- Product: Bee
- Sector: Education & research
- Canonical route: https://bee.heossi.com/use-cases/education-research-cited-knowledge
- Operational decision: Help staff and learners find controlling material without fabricating sources or silently crossing access boundaries.

### Turn employee policy questions into a reviewable structured decision queue

- Product: Bee
- Sector: Human resources
- Canonical route: https://bee.heossi.com/use-cases/human-resources-structured-review
- Operational decision: Route sensitive requests with cited policy context while reserving employment decisions for authorised people.

### Answer questions across engagement evidence rooms with traceable citations

- Product: Bee
- Sector: Professional services
- Canonical route: https://bee.heossi.com/use-cases/professional-services-cited-knowledge
- Operational decision: Accelerate client delivery while respecting matter isolation, source authority, and reviewer accountability.

### Reconcile the complete history of operating procedure libraries before acting

- Product: Bee
- Sector: Startups & SMB
- Canonical route: https://bee.heossi.com/use-cases/startups-smb-full-history-reconciliation
- Operational decision: Identify stale or conflicting instructions before a small team automates a consequential operational task.

### Operate a bounded agent over trade-surveillance alerts without surrendering approval

- Product: Bee
- Sector: Banking & capital markets
- Canonical route: https://bee.heossi.com/use-cases/banking-capital-markets-bounded-agent
- Operational decision: Enrich and prioritise alerts while keeping disposition, regulatory escalation, and model exceptions human-controlled.

### Answer questions across clinical policy libraries with traceable citations

- Product: Bee
- Sector: Healthcare
- Canonical route: https://bee.heossi.com/use-cases/healthcare-cited-knowledge
- Operational decision: Return the applicable policy passage and version while distinguishing retrieval support from clinical advice.

### Answer questions across repository-wide change analysis with traceable citations

- Product: Bee
- Sector: Software engineering
- Canonical route: https://bee.heossi.com/use-cases/software-engineering-cited-knowledge
- Operational decision: Trace behaviour across code, tests, and architecture records instead of generating an uncited patch from a partial file.

### Reconcile the complete history of detection rule backlogs before acting

- Product: Bee
- Sector: Cybersecurity
- Canonical route: https://bee.heossi.com/use-cases/cybersecurity-full-history-reconciliation
- Operational decision: Connect tuning history, incidents, exceptions, and telemetry gaps before changing a production detection.

### Answer questions across consultation submissions with traceable citations

- Product: Bee
- Sector: Government
- Canonical route: https://bee.heossi.com/use-cases/government-cited-knowledge
- Operational decision: Summarise public input without erasing minority positions, source attribution, or the policy owner's judgement.


## Policies

- privacy: https://www.heossi.com/privacy
- terms: https://www.heossi.com/terms
- security: https://www.heossi.com/.well-known/security.txt
- trustHub: https://www.heossi.com/trust-hub
- compliance: https://www.heossi.com/legal-compliance
- responsibleAi: https://www.heossi.com/legal-compliance/responsible-ai

## Provenance

Product claims in this document are FETCHED from each product's own facts.json at request time, not restated from memory, so they cannot drift from what the product publishes. Each PRODUCT signs its payload (ML-DSA-65 + Ed25519); both proofs are verified against registry-pinned producer keys before use. THIS company record is not itself signed.

Composed from: https://bee.heossi.com/facts.json, https://qnsi.heossi.com/facts.json
This document is not itself cryptographically signed (signed: false).
Generated: 2026-07-30T08:49:42.260Z