For regulated industries and security-conscious teams, sending meeting audio to a third-party SaaS is a non-starter. Self-hosted, open-source meeting notes are the answer.
What 'self-hosted' should mean
- The app runs inside your network, or on infrastructure you control
- Transcription happens on the user's device or your own hardware
- The source is open, so your security team can audit it rather than take a vendor's word
- Identity integrates with what you already run — SSO/SAML, and SCIM if you provision at scale
- There is an audit trail of who read what
The Ledgeur model
Ledgeur meets the first three outright: it is MIT-licensed, the schema is in the repository, and transcription and speaker separation run on the user's own device rather than anywhere you would have to secure. It does not meet the last two. There is no SSO, no SAML, no SCIM and no admin audit log today, and there is no packaged Docker or Helm deployment — self-hosting is currently a manual job for somebody comfortable with Postgres. We would rather you knew that before a procurement call than during one. If those are hard requirements, we are not the right answer yet.
Why open source wins the review
Auditability plus on-device processing means there's nothing for an attacker to exfiltrate from a vendor and nothing opaque for your security team to object to.