Baalda for enterprise

Company knowledge on infrastructure you control, readable by your own AI.

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.

An example vault

What a enterprise vault can look like.

A vault is a folder of plain markdown files. Shape it however you work. This is one way to start, and the week below is what a few days in it could look like.

Company
  • Engineering
  • Runbooks
  • Incident response.md
  • Architecture decisions
  • Sales
  • Objection handling.md
  • People (restricted)
  • Policies
  • Security policy.md
Example layout. Every row is a real folder or .md file on disk.
  1. Mon

    IT runs the sync backend on the company's own servers.

  2. Tue

    Engineering and Sales each get their own vault, permissioned on its own.

  3. Wed

    The internal assistant answers from the runbooks over MCP.

  4. Thu

    People files stay restricted, down to the individual note.

  5. Fri

    A bad bulk edit is reverted from a checkpoint, for every member at once.

How it works

Three things companies do in Baalda

01

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.

02

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.

03

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.

Talk to us

FAQ

Frequently asked questions

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.

Start your team’s brain

Free and open source. No account needed.