Contact
Deployment questions, privacy review, a tricky integration, or a straight comparison against what you use now — all fair game.
Our assistant searches our own knowledge base and answers what it can. If it cannot fully answer you, a person takes over — and you will be told which happened. We do not publish a response time we have not committed to.
Before you write
Yes, with a local model. The workspace, the retrieval stack and the PII detector all run without outbound internet; licence verification is offline against a bundled public key. Cloud model providers are the only part that needs the internet, and they are optional.
Community is free and uncapped, so the most honest trial is to run it. For the Enterprise modules, get in touch and we will sort out a key.
Tell us where you are coming from. Knowledge bases, automations and websites all import and export as files, and there is a converter for existing n8n workflows.
Use this form with "security" in the subject and it is routed to the right people. Please do not include exploit details in the first message.
Yes. Send it over. The data processing agreement, the sub-processor list and the security model are all published, so most of it is already answered in writing — which usually makes the round trip short.
That is usually who replies. If your question is about deployment topology, the retrieval stack or the privacy model, say so and it goes straight to an engineer rather than through a qualification call.
Community is free and uncapped, so a pilot costs you infrastructure and time rather than money. If the thing you want to pilot is an Enterprise module, we will issue a key for the duration.
What to expect
Bovenkerkerweg 6 unit 1.12 1185 XE Amstelveen Netherlands KvK 97632430
Source, issues and releases live on GitHub. Legal documents — privacy policy, terms, data processing agreement and sub-processors — are linked in the footer of every page.
github.com/Bee-Flow/Bee-Flow-AI