Maritime
Infrastructure · tested 2026-08-31 · re-test due 2026-11-29 · by the Hlido desk, not the vendor
In short: Agent-first hosting that gives every agent its own micro-VM at a flat $1/month — a genuinely differentiated infra bet, still early and self-benchmarked.
5 PASS · 0 FAIL of 5 public-surface claims
Quick answer
Maritime scores 75/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-31). STEADY (75) on a clear, differentiated value proposition (per-agent micro-VM isolation), transparent flat pricing, and a genuinely agent-first control surface (non-interactive CLI + typed SDKs + webhooks). Pricing: Usage-based · Subscription.
Maritime is infrastructure built for one specific shape of demand: running many isolated AI agents cheaply, one hardware-isolated micro-VM per agent rather than threads in a shared runtime. The pitch is unusually concrete for this category — a non-interactive CLI (so your own agents can provision agents), typed TypeScript and Python SDKs, lifecycle webhooks, encrypted per-VM secrets, sleep/wake in about a second, and a flat $1-per-agent-per-month price with nothing metered. That combination — hard isolation plus flat, legible pricing plus an agent-provisionable CLI — is a real position, and it is aimed squarely at the emerging pattern of shipping a dedicated agent per end-customer. Where to stay skeptical: the headline comparison table against E2B, Modal, Fly.io and others is vendor-authored and should be treated as a claim, not a benchmark; 'no cold starts / ~1s wake' and the isolation guarantees are exactly the things that need independent measurement before they are trusted for production; and the company is young with limited public track record. As a component in an agent stack this scores well because it is designed to be driven programmatically — but the reliability claims are unverified from the public surface alone.
Why STEADY
STEADY (75) on a clear, differentiated value proposition (per-agent micro-VM isolation), transparent flat pricing, and a genuinely agent-first control surface (non-interactive CLI + typed SDKs + webhooks). Held below higher bands because the review is public-surface only: the isolation and no-cold-start claims are unmeasured, the competitive comparison is self-authored, and the company has a short public track record.
Public-surface checklist
- PASS Homepage loads (required)
- PASS Primary value prop (required) — 'Run a thousand agents as easily as one' — per-agent micro-VM isolation
- PASS Cta present (required) — 'Start free' / 'Book a demo'
- PASS Pricing or access — Transparent flat tiers Free/$20/$100/$500/Custom + $1/agent
- PASS Evidence or demo — Live dashboard URL example + comparison table (vendor-authored)
What we saw
4 screenshots captured by the Hlido engine during the reviewed run (run-f8712cd20e309b66-maritime-sh). Our own captures — not vendor marketing material.
What it does well
- One hardware-isolated micro-VM per agent — a clear, defensible isolation model over shared-runtime rivals
- Flat, legible pricing ($1/agent/month, nothing metered) that is easy to reason about at scale
- Agent-first control surface: a fully non-interactive CLI so agents can provision agents, plus typed TS/Python SDKs and REST
- Lifecycle webhooks (deploy/sleep/wake/fail) and per-VM encrypted secrets
- Migration paths advertised from E2B, LangGraph and other platforms, plus SSH access and exportable state (low lock-in posture)
What it fails at
- The headline performance/isolation claims (no cold starts, ~1s wake, hard boundaries) are unmeasured on the public surface
- The side-by-side comparison table against competitors is vendor-authored — a marketing claim, not an independent benchmark
- Short public track record; no third-party reliability or security evidence visible
- No public status/SLA or incident history surfaced from the homepage
Red flags
- Competitive comparison table is self-published and should not be read as an independent benchmark
Best for
- Startups selling a dedicated AI agent per end-customer that need hard per-tenant isolation
- Teams that want their own agents to programmatically provision and tear down agent runtimes
- Cost-sensitive workloads where flat per-agent pricing beats metered compute
Not recommended for
- Workloads needing a proven, long-standing reliability/SLA track record today
- Buyers who need the isolation and cold-start claims independently verified before adoption
- Single-agent hobby use where a generic PaaS is simpler
Pricing & access
- ModelUsage-based · Subscription
- Price points we recorded
Agent-first hosting that gives every agent its own micro-VM at a flat $1/month — a genuinely differentiated infra bet, still early and self-benchmarked.
- Pricing findable on the public surfacePASS Transparent flat tiers Free/$20/$100/$500/Custom + $1/agent (tested 2026-08-31)
Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-31.
Related agents
Agent relevance
API CLI Webhook SDK
Agentic-Commerce Readiness 59/100 · INTEGRABLE
Independent readiness for agent delegation & transaction. How it’s scored · check live
Strong: Maritime is designed to be driven programmatically — a non-interactive CLI plus typed TS/Python SDKs and REST let an agent provision, wake, and tear down agent runtimes. Not behaviourally tested by Hlido from the public surface.
Agent-friendly score: 8/10
Score over time
The longitudinal record — every point is the score as published on that date. Raw series.
Evidence
- One isolated micro-VM per agent, provisioned from your backend — source (2026-08-31) verified
- Flat pricing at $1 per agent per month, nothing metered — source (2026-08-31) verified
- Non-interactive CLI + TypeScript/Python SDKs + REST — source (2026-08-31) verified
- No cold starts / ~1s wake from sleep — source (2026-08-31)



