Mesa
Product · Git Server

A headless Git server, built for agent workloads.

Standard Git over HTTPS — clone, fetch, push, branch. Native large file support, no LFS. Sub-50ms latency, no rate limits, and API keys scoped down to a single branch.

Read docs
# Clone any Mesa repo over HTTPS - just like GitHub
$ git clone https://t:${MESA_API_KEY}@api.mesa.dev/acme/agent-workspace.git


# Push, branch, force-push - all standard Git
$ git checkout -b feature/new-flow
$ git add .
$ git commit -m "feat: agent run 7f2a"
$ git push -u origin feature/new-flow
1.0OVERVIEW

Standard Git, but built for the way agents push code.

Mesa speaks the Git HTTP smart protocol over HTTPS. The git CLI, libgit2, JGit, and CI runners all clone, fetch, and push without modification — no proprietary client, no migration tax.

Underneath, Mesa runs on a purpose-built version control engine based on Jujutsu. The Git transport layer translates transparently, so your client sees a normal repository while you get all the speed and concurrency of the underlying engine.

2.0GIT COMPATIBILITY

Everything your tooling expects.

Supported Git operations
OperationStatus
Clone
Fetch & pull
Push
Force push
Signed commits
Branches
Tags
3.0NATIVE LARGE FILES
No LFS, no pointers, no side channel

Commit large files like every other file.

Mesa’s storage layer treats large files as first-class objects in the repository. You commit datasets, model weights, and media directly — no LFS client, no pointer files, no special configuration that breaks agent tooling.

Max pack per push
5 GiB
Per-file limit
None
vs. traditional Git hosts
  • Native large file storage
  • Random access on multi-GB files
  • Built-in deduplication
  • Separate LFS server
  • Pointer files in your tree
4.0AGENT THROUGHPUT

Designed for thousands of concurrent agents, not a handful of humans.

Multi-tenant by design

Tens of thousands of repos per org. No per-tenant infrastructure to provision — create a repo with one API call.

No rate limits

Run thousands of concurrent clones, fetches, and pushes.

Strong consistency

Pushes are durable when they return. Reads see the latest committed state — no eventual consistency surprises mid-run.

5.0SCOPED ACCESS

API keys, scoped down to a single branch.

Every Git operation authenticates with a Mesa API key over HTTP Basic. Mint short-lived, narrowly-scoped keys per agent — not per developer.

ScopeOperations
read
Clone, fetch, pull
Hand a sandboxed agent a token that can only browse the code.
write
Read + push to allowed refs
Let an agent commit its work, scoped to a single repo or branch glob.
admin
All operations
Reserve for human operators and trusted automation.
// Mint a key scoped to a single repo, with read-only access
const key = await mesa.apiKeys.create({
  scope: "read",
  resources: [{ org: "acme", repo: "agent-workspace" }],
  ttl: "1h",
});


// Hand it to the agent that needs to clone, nothing else
sandbox.env.MESA_API_KEY = key.token;

Fig. 1. Mint a short-lived, repo-scoped key per agent.

6.0GITHUB SYNC
Coming soon

Bidirectional sync with GitHub.

Run agents against Mesa for speed and isolation, then ship the result back to GitHub.

Mesa↔GitHub
  • Mirror repos in either direction
  • Push agent work as PRs
  • Continuous webhook-driven sync

git clone today.

No new client, no migration. Just a faster, agent-native Git server.

Read docs