A private LLM API your security team can sign off on

What “private” actually means here

Bee gives security teams concrete controls to review: retrieval indexes are isolated per tenant, deployment boundaries are explicit, and the Data Processing Addendum - with EU Standard Contractual Clauses for international transfers - auto-incorporates into every paid plan.

Encryption is standard practice, stated plainly: TLS 1.3 in transit, AES-256-GCM at rest under per-tenant keys, with customer-managed keys available on Hive and above.

API plans from prototype to production

• →Bee Pollen - 500K pooled tokens per month, one API key, hard-limited with no surprise overage. No card required.
• →Bee Nectar - zero-base prepaid usage. Cell and Brood use standard capacity; stronger public models use cost-isolated Flex at their published per-model rates.
• →Bee Honey - $1,500/month platform commitment plus prepaid usage from the first call. Cell through Comb use standard capacity, stronger models use Flex, and the plan carries a 99.9% uptime SLA.
• →Bee Propolis - $3,000/month platform commitment plus prepaid usage. Cell through Hive use standard capacity, Swarm uses explicit Flex, and the plan carries a 99.9% uptime SLA.
• →Bee Royal Jelly - contracted token rate cards, private deployment, and net-30 procurement terms.

The deployment ladder

When shared cloud is not enough, Enclave engagements scope a single-customer boundary from $15,000/mo. Regulated and Sovereign controls-including key ownership, audit, locality, and infrastructure-are fixed per contract and deployment manifest. Broader self-hosted and air-gapped operation is not generally available today.

You start on the public API and move down the ladder as requirements harden - the wire format and your client code stay the same.

Post-quantum posture

Bee Enclave Sovereign customer transport runs NIST-finalized post-quantum cryptography - FIPS 203 (ML-KEM) key exchange with FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA) signatures - by default, with no classical-fallback handshake. Public tiers use standard TLS 1.3 today, with the PQC default following the Sovereign rollout.

For data with a long confidentiality horizon, that closes the harvest-now-decrypt-later gap at the transport layer.

Verify before you buy

Bee publishes its trust evidence: live engine status at /status, release validation records at /trust, and the full legal surface - Terms, Privacy Policy, DPA, sub-processor list - linked from every page footer. Procurement teams can request counter-signed copies.