What we don't have.
Buying software on the strength of a feature grid that turns out to be a roadmap is a miserable experience, and everybody in this category has had it. So here is the complete list, on its own page, with a link you can send to whoever runs your security review.
The rule on the other side of this is written into the code. The file that defines what each plan includes, lib/plans.ts, carries an instruction at the top saying nothing goes in a feature list unless it ships today, and a test that fails if it does. This page is the same rule pointed the other way: it may not leave anything out.
None of this makes the on-device design less true. Your meeting audio is transcribed on your own machine and never reaches a server we run, and that is a stronger property than most of what is missing below. It is not a substitute for a certificate, and we will not pretend it is one.
Security and compliance
The certifications and paperwork a procurement process asks for.
We have not been audited against either. If your procurement process requires a report, we cannot pass it today. What we can offer instead is the source code and a design in which the meeting audio never reaches us at all.
The app itself signs in with SAML, and the single sign-on button appears whenever a workspace has it configured, so an organisation running its own backend can use it now. It is not switched on for Ledgeur's own hosted backend, so in practice you cannot use it with us yet.
Check it yourself: apps/desktop/src/lib/session.ts
We do not sign business associate agreements. The on-device design means protected health information in a recording never reaches a server we run, which is a strong position, but it is not the same thing as a BAA and we will not let it be mistaken for one. If your compliance programme needs the paperwork, you need a vendor who signs it.
None has been commissioned. Nobody independent has tried to break this.
We will thank you properly and credit you for anything you report, but we cannot pay for it yet.
Administration
What an IT team gets to manage, and what it does not.
Not built at all. Adding and removing people is done by hand. If your security review requires automated deprovisioning, we are not the right fit yet, and we would rather say so now than during onboarding.
Not built. Workspace administration today is one owner and a member list. Access tokens record when they were last used, and that is the extent of the audit trail.
How you get it
Where the software runs and how it reaches your machines.
There is no Docker image and no Helm chart. Self-hosting is genuinely possible, because the source is MIT and the whole schema is in the repository, but it is a manual job today. Enterprise means we help you do it rather than handing you a one-line install.
Check it yourself: supabase/migrations
The iOS and Android apps are the same code as the desktop app and sync with it under the same meeting ids, and both build to a store-ready, signed binary. Neither has a store listing yet, so today they are installed from source.
Check it yourself: docs/MOBILE.md
In the product itself
Things the app genuinely cannot do yet.
Two people editing the same meeting notes at the same moment will overwrite each other. Sync resolves by last writer, which is right for one person on two devices and wrong for two people on one document.
Check it yourself: packages/core/src/data/merge.ts
Action items go to Linear, Todoist, Asana, Notion, or any endpoint you point a signed webhook at. Jira, Monday and ClickUp are not built, and there is no two-way sync anywhere: a task closed in Linear does not close in Ledgeur.
Check it yourself: packages/core/src/tasks/push.ts
If one of these is a blocker
Say so. We would rather lose the evaluation now than during onboarding, and we will tell you honestly whether it is weeks away or not planned at all.
11 items