Roadmap
Updated as things ship
Most roadmaps are a wish list with a logo on it. This one is graded honestly: beta means you can switch it on today and it is in real use, in development means it exists and is not finished, and exploring means not a line of it is written. Nothing here carries a date, because a date on a roadmap is a promise and we would rather keep the ones we make.
Open the appFollow along on GitHub
Status
Beta means you can use it now, behind an opt-in, while we are still changing it — not a waiting list. In development means it is real code you may already be able to reach, but we are not calling it finished yet.
Build internal applications against your own data model: a designer for the schema, a query layer, row-level access rules, connectors to the systems you already run, and an assistant that drafts the first version for you.
Enterprise plan. Usable today and still moving — expect it to keep changing shape.
Describe a page and get working HTML, CSS and JavaScript — or React — with its own database behind it. Preview it live, let it call your integrations and automations as you, version every change, then publish, share or download the whole thing as a zip.
Enterprise plan. Usable today and still moving.
A compliance workspace inside organisation settings that grades your own installation against 44 checks across GDPR, the EU AI Act and ISO 27001 — and holds the paperwork behind them. A data-subject request inbox with a public intake form, a breach register that starts the 72-hour authority clock the moment an incident is recorded, a record of processing activities, a DPIA per assistant, and for ISO a Statement of Applicability, ISMS policy documents, a risk register, internal audit and training attestations. Every register exports as a PDF.
Enterprise plan, and an administrator with the compliance permission. The checks read your live configuration rather than a questionnaire, so the score describes this installation — it is not a certificate, and no auditor has signed off on how we map a check to an article.
A workspace that holds its own knowledge, its own custom instructions and its own memory. Invite colleagues as editor or viewer, and every change lands in an activity trail.
On every plan, and still settling — memory is extracted per project, so nothing leaks between them.
Extend the workspace with signed, versioned add-ons from the Bee Flow module hub. Each one declares exactly which permissions it wants — database, AI, email, outbound network — and an administrator has to approve that list before it runs.
Installed by an administrator. Packages are signature-verified on every boot and quarantined if they fail. The catalogue is still small.
A matter file that behaves like a notebook: gather sources, draft against them, and keep a verified table of authorities. Research reaches into case law, EU sources and statute, and every citation is checked rather than assumed.
Enterprise plan, opt-in. Dutch law only, and desktop only — both the sources and the interface are built around Dutch practice.
Run a helpdesk inside the workspace: shared inboxes, canned replies, automations, an audit trail and per-member access. Assistants draft answers from your knowledge base without sending anything on their own.
Enterprise plan, opt-in, and each member needs the support permission.
Describe the kind of organisation you are looking for and get a researched, enriched list back, with a small CRM behind it: contacts, an activity timeline, and follow-up tasks that chase the person they are assigned to.
Enterprise plan, opt-in. Check your own legal basis before prospecting — the tool does not decide that for you.
The packaging format, the permission manifest, the install runtime and the developer kit all exist. What is missing is the part that matters to you: a module has to be signed by Bee Flow before the product will load it, so you cannot yet build one and install it yourself.
The hard part is deciding how to trust a package we did not sign, without weakening the guarantee that makes the permission list worth reading.
A public board where you propose something and vote on what other people have proposed, so the ordering of this page stops being ours alone. Sign in with your Bee Flow account or with GitHub; accepted requests become issues in the public repository.
Requests are reviewed before they appear publicly.
Legal Studio checks citations against real sources, and today those sources are Dutch: Dutch case law, Dutch statute and the EU material that sits above them. We are working out what it takes to add other jurisdictions — which official registers publish in a form that can be cited reliably, what a licence to use them costs and permits, and how a matter file should behave when it spans more than one legal system.
Research, not a plan. The hard part is not the retrieval — it is that a citation checker is worthless unless the source it checks against is authoritative in that jurisdiction, and that varies enormously by country.
The idea: you build something useful for your own workspace, publish it, and another organisation installs it — paying you, not us. Everything about that is unbuilt. There is no publisher account, no review process and no way for you to be paid.
Genuinely an idea at this point. It also needs answers on liability, review, and what happens to a customer whose supplier walks away.
This page describes what we are working on, not what we promise to deliver or when.
Work starts because a customer hit a wall, not because a category looked empty. That is why the list is uneven: Legal exists in depth for Dutch practice and not at all for anywhere else, because that is who asked for it. When we do not know whether something is worth building, it stays under "exploring" and we say so, rather than describing it in the present tense and hoping nobody checks.
A beta feature is switched on by your administrator and is in real use — it is not a preview you join and then wait for. In development is one step behind that: the code exists and you may well be able to reach it, but we are still changing decisions inside it and would rather you knew that before you build on it. In both cases your data is treated exactly as it is everywhere else in the product; the encryption, the permissions and the audit trail have no beta version.
About this page
Because we would miss them, and a missed date on a public page is worse than no date at all. Our terms disclaim uninterrupted operation for the same honest reason. If you need a commitment for a procurement process, ask us directly and we will put one in writing for your specific case rather than to the whole internet.
People do. The risk is less about stability than churn — the feature may change shape under you, and a workflow built around one screen may need adjusting. If that is a problem, wait. If you would rather influence the shape while it is still soft, switch it on and tell us what is wrong with it.
Tell us. Until the public board is live, the contact form reaches a human and the GitHub repository takes issues. A request from someone who explains what they are actually trying to do beats a feature title every time.
This page changes as things ship, and releases are published on GitHub. There is no notification list yet — that is fair criticism, and it is on the list itself.
Mostly, and the differences are deliberate. Billing and the hosted-only pieces do not apply when you run it yourself, and usage caps are not enforced off our cloud at all. Everything on this page that is not about subscriptions is the same code either way.
That is useful. Tell us what you are trying to do and we will tell you honestly whether it is close or years away.
Start a conversationOpen an issue