Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mesa.dev/llms.txt

Use this file to discover all available pages before exploring further.

Mesa is a programmable storage layer and virtual filesystem, built specifically for AI agents and developers building agentic products. Mesa supports versioning with simple checkpoints as well as complex branch-based workflows. We provide full Git compatibility but Mesa is far more powerful than a traditional Git hosting platform. You can read more about our versioning model here.

​
How it works

In Mesa, you organize resources using a special type of directory called a repository. A repository has a completely unique version history in Mesa and its own permissions and access controls. A repository is a chain of Changes or snapshots of the repository at that point in time. You can always go back and view the state of files at older Changes and even restore the current state of a file from an older Change version. In Mesa reads and writes are durable automatically. All writes are automatically persisted to the Change currently checked out in your local MesaFS instance. See Quickstart for more.

​
Use cases

Mesa is designed for high-throughput, machine-driven workflows where you need reliable versioning, low-latency reads and writes, and infinite scaling across many different repositories. It works wherever your agents run, whether in a sandbox or in-process. You can use it with a variety of tools and frameworks. Some common use cases that Mesa is optimized for:
  • Memories and Skills management
  • Prompt-to-app builders
  • SWE agents
  • Agent infrastructure like sandboxes
  • Agent orchestrators
  • AI workflow builders

​
Benefits over traditional Git hosting

  • Our APIs and product surface area are designed from Day 1 to be used by Agents
  • Designed for high-volume automated workflows and large repo counts
  • Fine-grained API tokens for precise access control
  • Virtual filesystem for easy agent access

​
Pricing

See our pricing page for more details.

​
Up Next

Quickstart

Create your first repository and experiment with versioning.

Versioning

Learn about Mesa’s versioning model and how it maps to your use case.

MesaFS

Explore Mesa’s virtual filesystem for easy reads and writes.

Best Practices

Learn best practices for using Mesa in your agent workflows.

​
FAQ

No. You can use Mesa entirely through the SDK and REST API without ever running a Git command. Mesa handles versioning, branching, and history behind the scenes. If you choose to instead use Mesa as a standard Git server, it is fully compatible with standard Git clients over HTTPS.
Yes. Mesa supports clone, fetch, push, and branch operations over HTTPS using any Git client. Authenticate with your API key as the password:
git clone https://t:<API_KEY>@api.mesa.dev/<org>/<repo>.git
See the Git Server docs for details.
GitHub is built for human developers collaborating through pull requests. Mesa is built for machines. Our APIs, virtual filesystem, and versioning model are designed for high-throughput automated workflows where thousands of ephemeral agents read and write concurrently. Mesa also supports more ergonomic checkpoint-style versioning that doesn’t require the ceremony of Git, making it easier to use in agentic applications.
Mesa offers official SDKs for TypeScript, Python, and Rust. The REST API can be called from any language. Mesa works with agent frameworks like Vercel AI SDK, Langchain, and Mastra, and integrates with sandbox providers like Daytona and E2B.
Changes are Mesa’s core versioning primitive — similar to Git commits. Each change captures a snapshot of edits with a message and author. Bookmarks are lightweight pointers to changes — similar to Git branches. Together they support everything from simple linear checkpoints to full branching and merging workflows. See Versioning for more.
The FUSE-based virtual filesystem supports macOS (via macFUSE) and Linux (via FUSE3), including both Debian/Ubuntu and Alpine distributions. For environments where FUSE isn’t available, the TypeScript SDK includes an app-level virtual filesystem that works anywhere Node.js runs. See Virtual Filesystem for details.
Automatic GitHub sync is coming soon. You can already push and pull between Mesa and GitHub using standard Git commands since Mesa is fully Git-compatible. See GitHub Sync for the latest status.
Mesa supports custom on-prem deployments for enterprise customers. By default, Mesa runs as a hosted service at app.mesa.dev. If you’re interested in on-prem deployment, reach out to us over email at founders@mesa.dev.