Private media relay
Media moves.
Metadata doesn't.
Send a file through Hermes. Its identifying metadata is stripped, and the asset is encrypted at rest before it reaches its workspace.
No re-encoding. No public access to private files.
Hermes relay map
Request path
Payload: preservedContainer metadata: removed
12supported formats
0re-encoded
1database per user
Encrypted at rest
What happens at ingest
A cleaner route
for the same file.
Hermes handles the identifying details, not your creative work. Your original media is never re-encoded.
Media manifestBefore / After
GPS coordinatesEmbedded location dataRemoved
Camera serialDSC-••••-4812Removed
Author nameEmbedded profileRemoved
Image / audio dataOriginal payloadPreserved
Illustrative metadata fields. Results depend on the file format and its contents.
Removes container metadata only. Faces, places and text visible in the picture, and data inside the video stream, are not changed.
Workspace boundaries
Public when shared.
Private when kept.
Choose a public workspace for shareable assets, or a private vault tied to your account. Private media stays owner-only.
One upload
Public workspaceShareable by linkContainer metadata removed
Private workspaceOnly you can open itStored in your user vault
Choose who can access each upload.
For developers
One endpoint.
Clean on arrival.
Upload through the stable v2 route. Choose a workspace, then use the v1 media URLs to retrieve public assets.
Sign in to get startedcurl -X POST "$HERMES_URL/v2/" \
-H "Authorization: Bearer $HERMA_API_TOKEN" \
-F "file=@image.png" \
-F "workspace=public"Multipart form data