Networks

Maritime Networks is the network layer for agents and computers. Every agent and computer has three network settings: what it may reach on the internet, where its traffic exits, and which of your private systems it may use. The defaults reach everything from a shared address and nothing private. Change one setting and the platform enforces it on the host, outside the workload, so the workload cannot talk its way around it.

The three settings

Allow entries are domains (api.example.com), wildcards (*.example.com, subdomains at any depth, not the apex), IPv4 addresses, or IPv4 CIDRs. Deny entries are IPv4 addresses or CIDRs. The Maritime platform itself stays reachable in every mode. list with no entries and no preset equals none. A fourth switch, cutOff, stops all traffic at once and restores it when turned off.

Presets

A preset is a named allow and deny list shared by every agent and computer in the account. Two are built in. coding allows package registries (PyPI, npm, crates, Go, Maven, RubyGems, NuGet, pub.dev), source hosting (GitHub), container registries (Docker Hub, GHCR), Linux package mirrors, Nix, and Hugging Face. llm-apis allows the hosted model APIs (OpenAI, Anthropic, Google, OpenRouter, Mistral, Groq, Together, xAI, DeepSeek, Cohere, Fireworks). Your own presets live in Add-ons (Company settings, Policies), the CLI, and the API. Deleting a preset that workloads use is refused and the refusal counts them.

Residential IPs

The country exit sends the workload's traffic out through a residential IP: a home broadband or mobile address in the country you pick, from Maritime's residential provider. Sites that refuse cloud addresses see an ordinary home connection. TCP goes through the exit and names resolve there. UDP is dropped, except DNS.

Each workload has its own session, so two workloads never share a sticky IP. To get a new sticky IP at once, call new-ip; the next connection uses a new address. Changing the state, the city, or the session also starts a new session.

Residential traffic is billed per GB, in and out, at the rate the Exit row shows next to the option (options.country.priceLabel in the API). It counts toward the account's monthly cap (countryDataCapGb in account settings). Past the cap, connections are refused with outcome over_cap until the month ends. Bytes are counted when a connection closes, so a long connection counts when it ends.

With your own proxy (ownProxyUrl in account settings), the country exit goes through it instead. It is not billed, and state, city, and session do not apply.

CLI

The same six flags set the network on maritime agents create, maritime agents update, and maritime computers create. Flags not given keep their current value; none clears a list.

# Only package registries, source hosting, and one API of your own
maritime agents create --name worker --template-id codex \
  --internet list --network-policy coding --allow-out api.example.com

# Change a running agent: its own fixed address, and a database on your machine
maritime agents update <agent_id> --egress fixed --access db.office.private

# What is in force, and the address the internet sees
maritime agents network <agent_id>

# Try one connection from inside the agent
maritime agents network test <agent_id> api.example.com:443

# Presets shared by every agent and computer in the account
maritime network presets list
maritime network presets create --name partners --allow api.partner.com --allow '*.partner.com'
maritime network presets delete <preset_id>

maritime agents network test exits non-zero when the destination is not reached, so it works in scripts. A create that asks for a setting the account cannot have is refused with 422 and creates nothing.

API

One object, the same everywhere. Read and change it per workload, send it as network at creation, and manage presets at /api/v1/network/presets. The workload kind is agent, computer, or sandbox; a sandbox takes the shared and country exits only. Every field in an update is optional and replaces what it names; presetId: null clears the preset.

Inside the workload

A program inside the workload reads its own settings at http://100.127.254.1/network. It is the live view: it changes the moment you change a setting. The access entries name what to connect to.

$ curl -s http://100.127.254.1/network
{
  "kind": "agent",
  "workloadId": "...",
  "enforcement": "active",
  "cutOff": false,
  "internet": { "mode": "list", "allow": ["github.com", "api.example.com", "..."], "deny": [] },
  "exit": { "mode": "fixed", "ip": "203.0.113.7", "countryCode": null, "networkName": null },
  "access": [ \
    { "name": "db.office.private", "address": "100.127.0.3", "port": 5432,\
      "target": "localhost:5432", "networkName": "Office" }\
  ]
}

Agents also get a snapshot in their environment at boot:

Limits

• At most 100 allow entries and 50 deny entries per workload or preset. Deny wins over allow.
• Under list and none, a connection to a destination not on the list is reset at once. Name lookups still work, so a program sees a refused connection, not a hanging one. Activity records the destination with outcome blocked.
• fixed and country need a verified email and a paid plan: an active Starter, Growth or Scale plan, not the free trial, and not while a payment is failing. country is off for accounts that declared patient data. through needs one of your networks that allows internet. country also needs Maritime's residential provider or your own proxy (ownProxyUrl in account settings). The read tells you which, before you try.
• The account settings can turn fixed, country or through off; workloads that use a mode turned off leave from the shared address.
• A fixed address is requested when the first workload in a region asks for it and shows as requested for a short while. It is released when the last workload in that region leaves fixed.