
Overview
Specialist intelligence. Post-quantum security. Quantum computing.
- General Availability
- Stage
- 6
- Production Tiers
- 1,000,000 tokens
- Maximum Context
- OpenAI-compatible
- API
- Live
- Workspace
- Enclave deployment
- Sovereign
Evidence pack
Every claim on this page traces to a record below - facts contracts, conformance evidence and published artifacts.
Intelligence Ladder · six production tiers
Stack capabilities
What BEE delivers
- 6 production Intelligence Ladder tiers: Bee Cell, Bee Brood, Bee Comb, Bee Buzz, Bee Hive, Bee Swarm
- All tiers serve on governed, pinned base models or routing releases - Cell → Hive are production-deployed with scale-to-zero serving; Swarm is Bee's governed multi-lane routing fabric. Cell is the free entry tier, not an always-warm GPU. Public foundation-family lineage is disclosed on /models; exact revisions remain governed deployment records.
- Domain adapters are eval-gated and released through the governed pipeline - none merged into production routing yet, so tiers serve base-equivalent today. Each released adapter ships with a published validation record at /trust.
- Bee Enclave - a private / auditable / sovereign deployment mode for any Hive/Swarm-class workload, not a larger model tier.
- 7 published multimodal and tool-use capability groups across the ladder
- OpenAI-compatible API and governed workspace access
- Post-quantum protection using FIPS 203/204/205 is available with Enclave Sovereign deployments
Use cases
Where Bee is applied
25 representative workflows from Bee’s 100-case private, evidence-grounded AI library, each linking to the canonical entry.
Interfaces and modules
Integration surfaces
- Workspace (https://workspace.bee.heossi.com)
- OpenAI-compatible API (https://api.bee.heossi.com)
- Official TypeScript, Python, MCP, and VS Code packages
Deployment
Where it runs
Bee Enclave - a private / auditable / sovereign deployment mode for any Hive/Swarm-class workload, not a larger model tier.
Third-Party Services & Dependencies
HEOSSI solutions integrate with and depend on third-party services including blockchain networks, cloud infrastructure providers, cryptographic libraries, identity providers, and certificate authorities.
HEOSSI is not responsible for:
- Availability, performance, or security of third-party services
- Changes to third-party APIs, protocols, or standards
- Third-party service outages, breaches, or failures
- Costs associated with third-party services
- Compliance of third-party services with applicable laws
Performance metrics and capabilities may be affected by third-party service limitations. Customers are responsible for evaluating and accepting risks associated with third-party dependencies.
FAQ
Common questions about BEE
Is BEE OpenAI-compatible?
Yes. BEE exposes a drop-in OpenAI-compatible /chat/completions API, so existing OpenAI SDK code works by changing the base URL. It adds tenant-isolated retrieval, no customer-data training by default, MCP tool support, and QNSI-secured high-assurance paths.
Can I deploy BEE in a private or sovereign environment?
Single-customer deployment boundaries are designed and contracted per engagement. BEE Enclave supports private, regulated, and sovereign deployment paths for Hive/Swarm-class workloads. Broader customer-operated and disconnected deployment is not generally available today.
Does BEE train on my data?
No. BEE does not train on customer data by default, and retrieval is tenant-isolated so your data stays separated from other tenants. High-assurance and sovereign tiers add QNSI-secured post-quantum protection (ML-KEM, ML-DSA, SLH-DSA).
From the editorial
Latest writing on BEE
Next step
Interested in BEE?
Discuss deployment options, technical evaluations, and structured pilots with the HEOSSI engineering team.