Marshal
Put AI agents to work across your whole team, safely.
Every agent gets its own sandboxed space with the tools it needs, the credentials it should use, and only the network access you allow. Open a space and work with Claude Code or another agent in your browser. Hand off a task as a run and get a result back. Set up a deputy that picks up work on a schedule or from a GitHub, Slack or webhook event. All of it runs on your own Kubernetes cluster, and the audit log shows who did what.
What you can do
A private environment with a terminal in your browser, your code, and the agent ready to go. Stop it when you are done and pick up where you left off.
Work alongside an agent in a spaceGive the agent a task and walk away. It works in its own space, asks you when it needs a decision, and ends with a result you can read.
Hand off a task as a runSave a mission once. A deputy runs it by hand, on a schedule, or when a GitHub, Slack or webhook event arrives.
Keep deputies on standing workNetwork policy decides what each space can reach. Credentials stay out of the agent’s hands. The audit log records who did what.
Govern every agentUse cases
See what teams build with Marshal, step by step.
A deputy reviews each new pull request the moment it opens.
Review every pull requestWake up to upgrade pull requests that are ready for review.
Nightly dependency upgradesAn alert starts a run that gathers the facts and tells the right person.
Triage alerts from your toolsEvery engineer gets the same ready space, with the access and network rules you set.
A governed dev environment for every engineerMany runs at once, each in its own space, all in one list.
Run a fleet of agents in parallelAgents call your APIs with real keys while they hold only a placeholder.
Let agents use secrets they never seeHand a task from Claude Code or another MCP client to a run, and follow it to the result.
Delegate from your AI clientHow the parts fit
You pick packages (agents, tools, integrations) and put them in a stack. A member makes a manifest from the stack, and every space and run starts from a manifest. A network policy sits around each one.
Building blocks explains each part and how they connect.
Find your way
First steps for owners, admins and members.
Getting startedWhat spaces, runs, deputies and manifests are, and how they connect.
ConceptsEvery feature, its settings, and when to use it.
FeaturesWhat teams build with Marshal, end to end.
Use casesShort, numbered steps for one task at a time.
How-to guidesStart from what you see on screen and get the fix.
Help and fixesEvery CLI command, role and package.
ReferenceRun Marshal
Marshal is self-hosted. You install it on your own Kubernetes cluster (EKS, GKE, or a single k3s node) inside your own network. Your source code and credentials stay in your infrastructure.