Overview

Mesh Storage is the home for your data inside Alloy. Upload MCAP recordings from the web or sync them from devices, then browse, replay, and query them in Alloy.

What is Mesh Storage?

Mesh Storage is a managed data lake for your organisation. Files land in object storage, get indexed into queryable tables, and become available everywhere in Alloy: Replay, the SQL Workbench, and any Iceberg-compatible client like DuckDB, Spark, or Trino.

Files are organised by upload source, under the uploads root:

• uploads/web-uploads/: files you or a teammate upload from the browser.
• uploads/sdk-uploads/: files uploaded with the Python SDK.
• uploads/devices/<device-id>/: files uploaded automatically by your registered devices.

All of them end up in the same data lake, queryable side by side.

With the Agent Platform. If your organisation also has the Agent Platform, Alloy creates missions from any new MCAP file in Mesh Storage automatically, whether it comes from Alloy Edge, the app or the SDK. Only MCAP files become missions. In organisation settings → Missions → Create missions from Mesh, you choose how files group into missions, how long Alloy waits for an upload to settle, and which files to leave out. The agent reviews each new run once a recurring report runs on each new mission (new workspaces start with the First-look report), and it finds the runs and moments your team asks about, so finding a run stops being one team's job. See Review every run you upload and Find why a robot failed.

A tour of Mesh Storage

Mesh Storage has separate pages for Data, Devices, and Workbench.

• Data: browse files in List, Timeline, or Folders view; upload files; create API keys for external tools. Select a file to Inspect, Replay, Download, Export, or Delete it.
• Devices: add and approve devices, check status and last contact, and manage device keys.
• Workbench: query ingested data with SQL.

Open Devices → Add device for the Track Folder binary setup. The panel also links to the Docker setup.

How a file moves through Mesh Storage

Whether you upload from the web or a device pushes it up, every file shows one of these statuses:

1. Queued: the file has landed in object storage and is waiting to be processed.
2. Ingesting: Alloy is parsing the MCAP and building queryable tables.
3. Ingested: the file is queryable in the SQL Workbench and external Iceberg clients.
4. Ingest failed: something went wrong. Hover the badge for the reason.

Files that Alloy does not ingest show Skipped.

Replay and Inspect work as soon as an MCAP file lands. You don't have to wait for ingest to finish to scrub through a recording.

Next steps

• Getting data in: web uploads, Track Folder, or the Python SDK
• Python SDK: upload files, query ingested data, and read Mesh files from Python
• Managing your fleet: key rotation and dashboard signals
• Exploring your data: the file browser, SQL Workbench, external clients
• Troubleshooting & FAQ: common questions and fixes