Isolated micro-VM per agent
Each agent runs in its own VM boundary rather than a shared worker, which separates runtime state, secrets, and process space from other agents.
Maritime is a platform for deploying, managing, and scaling AI agents with isolated micro-VMs and a live API endpoint. Build customer-facing agents, custom workflows, and per-customer deployments.
Maritime is an infrastructure platform for deploying AI agents in isolated micro-VMs. It gives each agent persistent storage, encrypted secrets, and a public-facing way to receive messages through the dashboard, CLI, REST API, or connected channels.
The platform is built around sleeping agents that wake on demand, so teams can keep many agents running without managing their own servers. It supports framework-based agents and fully custom deployments, with a workflow focused on one agent per VM and per-customer isolation when needed.
Each agent runs in its own VM boundary rather than a shared worker, which separates runtime state, secrets, and process space from other agents.
Agents keep their state, including files on /data, when they go idle and wake again instead of restarting from scratch.
Agents can receive messages through the dashboard chat, CLI, REST API, web URL requests, or connected channels such as Telegram.
Maritime provides SDKs in TypeScript and Python, with REST underneath, so teams can provision and message agents from backend code.
You can deploy OpenClaw, Hermes, ZeroClaw, Claude Code, or your own Docker container and orchestration stack.
Agents can be tagged with external IDs and send lifecycle webhooks when they deploy, sleep, wake, or fail, which helps backend systems stay in sync.
A backend can create a dedicated agent for each new signup, keep customer data isolated, and send messages to the same agent over its lifecycle.
Teams can expose an agent through a public URL or chat channel and let it wake on demand when users send a message.
Developers can deploy their own containerized stack and use Maritime as the execution layer for agent logic, secrets, and persistence.
Products that need many live agents can keep them sleeping until needed, which matches the platform’s model for scaling out without shared workers.
Applications can use lifecycle events, triggers, or API calls to coordinate agent behavior from outside the agent process.
Agents sleep automatically after being idle, keep their state on persistent storage, and wake again in about a second when they receive a message, request, or trigger.
Yes. The docs say you can deploy a fully custom agent from a repository or Docker image, and that many teams run their own orchestration and dependencies.
Yes. The build docs describe provisioning one isolated agent per customer from a backend, using external IDs to keep your own database as the source of truth.
Agents can be reached through the dashboard chat, CLI, REST API, SDKs, web requests to a public URL, and connected channels such as Telegram.
No. The pricing page says plans are flat monthly agent slots, with add-ons billed as flat monthly prices rather than metered usage for messages, tokens, or compute time.
Traffic data is for reference only.
weaveos.com
Weave Router is an intelligent model router for coding agents. It evaluates coding tasks and routes requests across open and closed models, helping developers keep existing agent workflows while managing speed, quality, and model spend.
www.experientiallabs.ai
Experiential Labs is an open-source AI gateway that gives teams one endpoint and API key for hosted models, customer-owned keys, and local or custom models. It adds routing, budgets, access control, attribution, and optional intelligence features for agent traffic.
www.quotamint.com
An API for managing customer plans, feature access, credits, and usage tracking while keeping billing with your existing provider or custom system. Helps usage-based SaaS and API products make runtime access decisions and record consumption.