Skip to main content

Features

Bee Flow ships a layered feature set. Some are free at the Community tier; others are gated behind a licence key. See Tiers for the full matrix.

By feature

Community+ — Conversational UI on top of every integration. Agents are reusable, named personas with their own tool sets. 10 system starter agents seeded out of the box.

Community+ local · Pro+ vector — Drop documents in, ask questions across them. Local KB at Community; vector / hybrid / reranked KBs at Pro.

Pro+ — Trigger-based workflows. When an email tagged urgent arrives, summarise and post in Talk. Cron / webhook / NC event / manual triggers.

Community+ — Detect and redact emails, phone numbers, IBANs, BSNs, credit-card numbers and 14 other categories before prompts reach the model.

Enterprise+ — Stricter org-level policy: block prompts, log policy hits, audit-log export. Azure Content Safety for moderation.

Pro+ — Full-duplex voice calls with the assistant. Voxtral STT/TTS, energy-VAD, barge-in.

By use case

I want to…Start here
Summarise a long email or PDFChat & agents
Ask questions across a folder of docsKnowledge bases
Auto-triage my inbox every 10 minAutomations
Make sure customer data never leaves the tenantPrivacy shield
Log + audit every AI prompt for complianceDLP & guardrails
Talk to the assistant by voiceVoice
Build a custom agent for support ticketsStudio → Agent designer
Embed Bee Flow chat into another productAPI → Authentication

How tier gating works

Premium features are blocked at two layers:

  1. UI — gated nav entries are hidden at lower tiers (<RequireTier> wrapper).
  2. API — the requireLicenseFeature() middleware on the server returns 403 if the feature isn't allowed for the org's tier.

If you reach a 403, your tier doesn't include that feature. Upgrade or contact tomkooy@beeflow.nl. Source of truth: server/license/tiers.js.