Web upload

The fastest way to get a recording into Alloy: drag the .mcap file into Mesh Storage and walk away. No client to install, no device to provision.

Use this for ad-hoc files, recordings shared with you by a teammate, or a single mission you want to inspect without setting up an edge client.

Step 1: Open the upload modal

From the Mesh Storage action bar, click Upload.

Step 2: Add files

Drag MCAP files into the drop zone, or click to open the file picker. You can add multiple files at once.

Only .mcap files are accepted. Other file types are rejected with a warning telling you which ones were skipped — drop those out and continue.

Step 3: Upload

Click Upload to start. Each file shows a progress bar and a status badge:

The overall progress bar at the bottom shows total progress across all files.

You can click Cancel to abort all in-flight uploads. Cancelled multipart uploads are explicitly aborted on the backend so no orphaned parts are left behind.

Step 4: Wait for processing

Uploaded files land in the uploads/ folder of Mesh Storage with a status badge:

1. Queued — the file has landed in object storage and is waiting to be processed
2. Processing — Alloy is parsing the MCAP and building queryable tables
3. Ready — the file is queryable in SQL Workbench and external Iceberg clients
4. Failed — something went wrong; check the row for the error

Replay and Inspect work as soon as the file lands — you don't have to wait for processing to finish.

What about large files?

Web uploads use multipart upload. Each file is split into parts and uploaded in parallel. There's no per-file size limit imposed by the uploader, but very large files (multi-GB) are usually faster to push from a device using Edge upload over a stable connection.

What about folder structure?

Web-uploaded files all land flat under uploads/. If you want files organized by device, mission, or run, use device-based ingestion — files there are organized by device automatically.

AdNav mission uploads

For AdNav organizations using the mission uploader, upload either raw .anpp files or a single .zip containing folders exported by INS Manager. Do not mix ANPP and ZIP files in one upload or upload CSV files individually.

When a log lacks device identification, select the correct device in INS Manager and convert it before uploading. ZIP the complete export folder, including the CSV files and any DeviceInformation.txt and Configuration.txt files. Keep separate device exports in separate folders within the ZIP.

Alloy converts the exported CSVs to MCAP and retains the supplied metadata. ZIP uploads cannot recover measurements or packets absent from the export; raw ANPP remains the path for additional SDK-decoded packet data. This option applies to AdNav mission ingestion, not the MCAP-only Mesh Storage uploader above.