# Baalda for enterprise

> Baalda for enterprise: self-host the open-source backend, keep knowledge as plain markdown, separate vaults per department with per-file permissions, and connect internal AI over MCP.

Source: https://baalda.com/for/enterprise
Site: Baalda, https://baalda.com

Self-host the sync backend, keep every note as a plain file, and give each department its own vault with its own access. Your internal assistants connect over MCP and see only what they are allowed to.

## Run it where your data lives

The core is Apache-2.0, backend included. Deploy the sync server yourself and point the app at it. Notes stay as .md files on each person's disk.

## One vault per department

Separate vaults for each team or business unit, each with its own members, folders and tags. Structure that still holds when the org doubles.

## Undo at the scale of the whole vault

Checkpoints capture every note and the folder structure together. One is taken each day the vault changes, and a revert is broadcast to every member live.

## The plan that fits: Self-host

Self-host with no limits under Apache-2.0, or run on the managed Team plan. Talk to us about rollout and support.

## FAQ

### Can we self-host Baalda?

Yes. The core, including the sync backend, is open source under Apache-2.0. The deployment guide in the repository covers running the backend yourself and pointing the app at it.

### Where are our notes stored?

Every note is a plain .md file in a folder on each member's own disk, kept in step through the sync backend. There is no proprietary block format to export from.

### Can access be limited inside one vault?

Yes. Viewer and Editor access is set per folder and per file, and AI assistants connected over MCP are held to the same permissions.