Images & add-ons
Images
An image is what a machine starts from: the operating system, the tools and the software already installed. Every new machine boots from its image; everything it writes afterwards lives on its own disk.
You choose an image in the two ways below, or ask us for a Marketplace image.
Your own image, for sandboxes and agents
A sandbox or agent can run any Linux container image: build it from a GitHub repo with a Dockerfile, upload a ZIP, or pull a pre-built image from a public registry.
# build from a repo with a Dockerfile at the root
maritime create my-box --repo https://github.com/acme/my-box
# move an existing machine onto a pre-built public image
maritime deploy my-box --source docker --image ghcr.io/acme/my-box:v2 --waitBuilds run on a separate build machine, with a layer cache seeded from your previous image. Private code goes through repo builds; pre-built images must be on a public registry. The container contract and its gotchas are in Deploy any container; build details are in How builds work.
Computer images
A computer starts from a Maritime image chosen by its os:
linux(default): an XFCE desktop with Chromium and LibreOffice. See Linux desktops.windows: a Windows desktop. See Windows desktops.android: Android 15 (AOSP, no Google Play). See Android phones.
A computer starts from one of these three images. To add software, install it once on the computer: it stays on that computer's disk until you delete it. For a desktop image with software already set up, see the Marketplace below.
Marketplace
The Marketplace lists desktop images with the software already set up, such as MEDENT, Open Dental, QuickBooks Desktop Enterprise, SAP GUI for Windows, CargoWise One, Dentrix and UltraTax CS. Each card books a call with us, and we set the image up for your account. The last card requests an app that is not listed yet.
Maritime images are free; you pay only for the machine. Partner images can carry a publisher fee, per hour or per month, shown on the image. See Billing & plans.
Limits
- ZIP upload: 500 MB compressed, 2 GB unpacked.
- A build that prints nothing for 5 minutes is killed.
- A typical repo build and ship takes 1 to 3 minutes.
Every number is in Limits & errors.