Run the whole Beesiness stack inside your network.
For education, legal, healthcare, and public-sector teams that need to keep meeting audio inside their network. Helm chart ready, GDPR-aligned controls, signed image updates, audit-grade access logs. Already deployed in production at education customers.
Who buys Beesiness Enterprise
Education & K-12
Student-data jurisdiction (FERPA, EU regional rules) rules out third-party bots. Beesiness's Helm chart sits inside your school network. Live on-prem at K-12 education customers.
Legal & professional services
Attorney-client privilege requires audit-grade chain of custody. Beesiness's audit log + DPA + on-prem encryption-at-rest meet the bar without retraining your team.
Healthcare & insurance
HIPAA + GDPR overlap demands EU residency or on-prem. Beesiness's Helm chart pairs cleanly with your existing patient-data controls.
Public sector & finance
Air-gapped deployments, signed image updates, BYOC GPU pool for Whisper inference. Compliance-first by design.
What's in the Helm chart
Web app + admin
Next.js 15, runs on any Kubernetes node
Postgres 16
Your choice: Neon, AWS RDS, or in-cluster
Vexa Cloud OR self-hosted bots
Air-gapped clusters use self-hosted Vexa
Whisper-large-v3 ASR
GPU pool sized to your meeting volume
Claude API OR Llama-3.3-70B
Cloud Claude or in-cluster Llama
Inngest self-hosted
Background jobs in your VPC
Object storage
MinIO / Cloudflare R2 / AWS S3 — your choice
Compliance + audit posture
GDPR
Two-party consent flow + EU DPA + right-to-delete pipeline
SOC 2 Type II
Audit window Q4 2026
FERPA-friendly
Student-data isolation patterns
HIPAA-overlap
Encryption at rest + in transit, audit log
Self-host Helm chart
Air-gapped deployment supported
How a deployment goes
- 1Discovery call (30 min). Tell us about your network, your compliance constraints, and your meeting volume. We size the cluster and quote.
- 2Pilot install (1-2 weeks). Beesiness engineering helps you install the Helm chart in a staging namespace. We run a 50-meeting acceptance test before signing.
- 3Production cutover (1 week). Move to production namespace, wire your SSO, configure DPA + audit retention, train the admin team.
- 4Ongoing. Quarterly health-check call with your CSM. Signed image updates land in your registry monthly; you decide when to roll them out.
Ready when you're ready.
Email enterprise@beesiness.com with your network size + compliance jurisdiction. We respond within 1 business day with a discovery-call slot.