Snapshot
Continue to About ↓- What it does
- Maritime is a managed cloud that gives each AI agent its own Firecracker micro-VM with a persistent disk, so agents keep files, logins and memory across sleep, restart and redeploy.
More detail
- Agents sleep when idle and wake in about a second, and you can deploy a ready-made framework, any Docker container, or a persistent Linux desktop driven over MCP for each of your end users.
- Best for
- Startups and developers who need one persistent, isolated agent per end user, or stateful agents that must remember files and logins between sessions, and who want a flat predictable bill instead of metered sandbox pricing.
- Pricing
- Flat monthly subscriptions, with nothing metered: no charges for messages, tokens, sessions or compute time, and sleeping machines cost nothing.
More detail
- Plans are Free ($0, 3 machines, 1 awake at once), Starter ($20/mo, 20 machines, 5 awake), Growth ($100/mo, 100 machines, 25 awake), Scale ($500/mo, 500 mac
- Main limitation
- Teams looking for normal website or app hosting, or agents that must stay millisecond-reactive around the clock without paying the always-on add-on.
More detail
- Agents that rely on in-process timers also need rework, since timers inside a sleeping agent do not fire.
- Record
- Living and monitored
- Reviewed
- Evidence
- Public web research
- Machine access
- Structured profile ↗
About
- Maritime is a managed cloud that gives each AI agent its own Firecracker micro-VM with a persistent disk, so agents keep files, logins and memory across sleep, restart and redeploy.
- Agents sleep when idle and wake in about a second, and you can deploy a ready-made framework, any Docker container, or a persistent Linux desktop driven over MCP for each of your end users.
What it helps with
- Stateless serverless platforms cannot hold an agent's state between interactions
- Idle agents waste money when a full machine stays resident around the clock
- Metered per-second sandbox billing makes agent costs hard to predict
- Multi-tenant sandboxing raises isolation and cross-customer data risk
- Onboarding each customer to their own agent or desktop is manual and slow
Capabilities
A practical view of what is available and where limitations apply.
| Offering | Available | Detail |
|---|---|---|
| One Firecracker micro-VM per agent or computer | Yes | Own kernel, disk and network, with no file system, memory or process shared between customers. |
| Persistent disk | Yes | Mounted at /data for most templates; files, memory, logins and packages survive sleep, restart and redeploy. |
| Sleep and wake | Yes | Agents sleep automatically after idle minutes at no cost and wake on the next message, trigger or API call; site states boot about 0.5s and wake about 0.6s, while lifecycle logs state 1.1–1.4s. |
| Runs your own Docker container | Yes | Any Docker container becomes an agent through three endpoints covering sleep/wake, channels and triggers. |
| Persistent Linux desktop driven over MCP | Yes | XFCE, Chromium and LibreOffice desktop per end user, created on first get_computer call; requires a paid plan. |
| Human takeover and session logging | Yes | Live watch links and takeover links; logins, 2FA, CAPTCHAs and payments pause until a person marks the step done, and sessions are logged. |
| Per-agent sizing | Limited | 1 vCPU and 2 GB RAM included, expandable to 8 GB RAM and 100 GB SSD via paid add-ons. |
| Concurrent awake machines | Limited | Capped per plan at 1, 5, 25, 60 or 500; waking past the limit returns a retry-in-15-seconds answer. |
| In-process timers in sleeping agents | No | Timers inside a sleeping agent do not fire; scheduled work must use platform triggers. |
| Website or app hosting | Limited | Technically possible in a full VM, but the vendor states Maritime is built around sleeping and waking agents, not hosting websites. |
Bot trust
How confidently AI systems can verify this profile from public evidence.
58of 100
ChatGPT—/100
Claude58/100
What bots could verify
- • Identifies legal entity (Maritime AI, Inc.), active policy documents, and publicly visible founder profiles.
- • Provides transparent pricing details, clearly highlighting the distinction between sleeping and always-on VM pricing.
- • Discloses material security and privacy risks, including indefinite data retention and missing security headers.
What weakens trust
- • Lacks independent testimonials, case studies, or verified experiences from paying production customers.
- • No published uptime SLA, public status page, or documented incident history.
- • Lacks third-party security certifications, formal audit reports, or a published security.txt file.
Evidence
Where this record came from, when it was reviewed, and how confidently it can be used.
- Verification
- Scribble researched these facts from the linked public sources.
- The owner has not manually confirmed every field.
- Last reviewed
- Primary source
- maritime.sh
Technical profile details
Record ID
31cac659-b8d6-418e-8237-42ad710f8589Canonical URLhttps://profiles.scribble.network/listing/maritime-31cac6