Templates
A template (formerly called a blueprint) is a ready-to-deploy agent. Launch one of Maritime's ready-made templates in one click, or package your own working agent (image, configuration, and memory) into a template you can share with a private link.
Ready-made templates
The Templates tab in the dashboard lists Maritime's ready-to-run starting points. Each is a real agent framework, pre-configured and one image pull from live: pick one, give it a name, and deploy. Each links straight to its guide:
- OpenClaw: autonomous agent with 100+ skills.
- OpenClaw Identity: its own real phone number, email, and tunnel.
- OpenClaw Browser: drives a real Chromium for web automation.
- Hermes: self-improving agent with persistent memory.
- Hermes Identity: Hermes with its own phone, email, and tunnel.
- ZeroClaw: ultra-lightweight Rust agent, <5 MB RAM.
Your own templates go one step further: they capture a specific agent you already built (its image, configuration, and memory) so you (or anyone you send the link to) can clone the whole thing, not just the base framework.
What's in a template
A template captures all three layers of an agent:
- The image, including any code you changed inside the container, not just the base image.
- Environment variables: keys are kept, but secret values are blanked. Whoever deploys fills in their own.
- The
/datavolume: the agent's memory, persona, and workspace files. You pick exactly which files to include during creation.
Credentials never travel: gateway passwords, device pairings, SSH keys, and any JSON fields that look like api_key / token / password are stripped automatically.
Create a template
- Open your agent and choose Save as template. If the agent is running, Maritime puts it to sleep first so the capture is consistent.
- Give it a name and description, choose a visibility of Private (only you) or Unlisted (anyone with the link can clone it), and optionally add tags and a cover image.
- Review the file list from the agent's
/datavolume and deselect anything you don't want to ship. - Create. Capture usually takes 1-10 minutes (it snapshots the image and volume); you can navigate away and come back.
When it's ready you get a magic link, maritime.sh/share/templates/<slug>, that you can send to anyone. Your templates live under Templates → My Templates, where you can change visibility, share, or delete them.
Deploy from a share link
On a shared template's page, Clone Agent asks for a name, then walks through the environment variables the original agent used. For the LLM key you can choose Use Maritime LLM (included), billed against your API budget, or paste your own key. Optional connected services can be left blank and reconnected later. The clone boots with the template's image and memory, but none of the creator's secrets.
Submit a template
Built something worth sharing more widely? On the Templates page, Submit a template lets you propose it as a ready-made template. There are three ways to hand us the source. Pick whichever matches where your agent lives. Every submission also takes a template name, an optional description of what the agent does, and a contact email (pre-filled from your account) so we can reply. The recordings below walk through each path with Pi, an open-source coding-agent toolkit.
1. From a GitHub repo
The default option. Paste the repository URL. That's all the source we need; reviewers clone the repo directly. Give it a name, describe what the agent does, and hit Submit for review. The dialog confirms with Submission received and the email we'll reply to.
2. From a ZIP file
For code that isn't on GitHub. Drag & drop the archive (or click Choose file). It uploads immediately to private storage and the card flips to uploaded with a check mark, so reviewers get your actual code, not just a link. The submit button stays disabled until the upload finishes; then name it, describe it, and submit as usual.
3. Something else
For agents that live anywhere else: a Docker image, a docs page, a hosted service. The link is optional; use the description to say what the agent does and the notes field for anything we should know (where the image is published, how to try it, licensing). You need at least a link or a note so the review has something to go on.
Whichever path you pick, the submission lands with the Maritime team for a hand review. There's no automatic publish. We'll follow up at the address you provided, and if it's a fit, your agent ships as a ready-made template on this page.
From the CLI
# Package a sleeping/stopped agent:
maritime blueprint create my-agent --name "Support Bot v2" --visibility unlisted
# List yours:
maritime blueprint list
# Clone one into a new agent:
maritime blueprint deploy support-bot-v2 --name my-support-bot
# Alias: maritime bpFull flag reference in the CLI docs. (The CLI command is still maritime blueprint, the original name for templates.)