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

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.

Maritime — run screenshot 1 (home.png)
home.png
Maritime — run screenshot 2 (page_.png)
page_.png
Maritime — run screenshot 3 (page_pricing.png)
page_pricing.png
Maritime — run screenshot 4 (page_docs.png)
page_docs.png

What it does well

What it fails at

Red flags

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

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

Evidence

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-29

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Hlido trust score

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/maritime.svg)](https://hlido.eu/check/?agent=maritime)

HTML

<a href="https://hlido.eu/check/?agent=maritime"><img src="https://hlido.eu/badge/maritime.svg" alt="Hlido trust score"></a>