Your AI work library, on your own server.
Run Exagram on one Linux VM you control. Your AI tools connect to it the same way they connect to Exagram Cloud. We never see a Self-hosted install’s data.
Everything runs on your VM. We’re not in the path.
Your AI tools reach your server over MCP and sign in with OAuth. People open files in the web app, Exagram for Mac or through a Link.
- Claude
- ChatGPT
- Cursor
- Claude Code
- Any MCP client
- web
- api
- worker
- usercontent
- Postgres
- Object store
- The web app
- Exagram for Mac
- Anyone with a Link
No telemetry
Your keys
Previews can’t act as you
Community Edition or Business?
Start free on your own server. Move to Business when you need approvals, redaction, an audit trail or single sign-on.
| Feature | Community Edition | Business |
|---|---|---|
| Price | Free | Custom, priced for your team |
| Where it runs | Your server | Your server, or Exagram Cloud in the region you choose |
| Library, Revisions and Links | ✓ | ✓ |
| Folder access per AI Connection | ✓ | ✓ |
| Approvals and Publish policy | — | ✓ |
| Redaction for Connections | — | ✓ |
| Audit trail | — | 1 year, with export |
| SSO (SAML) and SCIM | — | ✓ |
| Support | Community, on GitHub | Priority support |
Yes. It’s free to run on your own server under the AGPL-3.0 license. Approvals, redaction, the audit trail, SSO and SCIM come with Exagram Business.
No. We never see a Self-hosted install’s data, and it sends no telemetry. The security guide lists every outbound connection and the setting that turns it off.
Your install serves the web app at your own address. Exagram for Mac switches to it from the menu bar: Server, then a custom address.
Pull the new release’s bundle, then start it again; migrations run on their own. The install docs have the steps, and how to back up first.