Public Roadmap

What's Next for MariMetric

We start with Container Tracking and evolve into a Maritime Intelligence Platform. This page is updated monthly and is fully transparent.

ShippedIn ProgressPlanned
ShippedV1.5 — Q2 2026 (current)

Container Tracking MVP

  • Real-time tracking for 3 carriers (Maersk, COSCO, ONE)
  • 18-language support at the edge
  • DCSA v2.2 standard 9-step timeline
  • Share link + 1200×630 image with clipboard copy
  • Full site-wide SEO + GEO structured data
In ProgressV1.6 — Q3 2026

Fleet Dashboard + Active Monitoring

  • Active monitors (track 1-50 containers continuously)
  • Per-tier refresh intervals (6h Free → 5min Business)
  • Background job queue for monitor refresh
  • 5 queries/IP/day rate limit on free tier
  • ISO 6346 check digit validation for all queries
PlannedV2.0 — Q4 2026

Public REST API Beta

  • GET /v1/containers/{number} (Maersk, COSCO, ONE)
  • Webhooks for status change notifications
  • API key management + tier-based rate limiting
  • OpenAPI 3.1 spec + interactive docs
  • TS / Python / Go SDK packages (npm, pip, go)
PlannedV2.5 — Q1 2027

MCP Server + AI-Native Access

  • @marimetric/mcp-server (npx install)
  • Tools: track_container, get_fleet_status, validate_container_number
  • Cursor / Claude Desktop / ChatGPT integration guides
  • Demo space: 'ChatGPT 查箱号' end-to-end
PlannedV3.0 — Q2 2027

Maritime Intelligence Platform

  • Vessel / Port / Route entity tracking
  • Predictive ETA using historical transit data
  • Anomaly detection (delays, diversions, customs holds)
  • Carbon emissions analytics (EEXI / CII)
  • On-prem / VPC deployment for enterprise

Our product strategy

Tracking captures traffic → Dashboard creates value → API builds ecosystem → MCP targets AI. Four distinct moats, each with a clear monetization path.

Tracking

Free traffic entry

Dashboard

Ongoing monitoring value

API

Developer ecosystem

MCP

AI-era infrastructure