For business
Integrate NoMoreData’s metadata analysis and processing capabilities into your own workflow — as an API today, and as deeper integrations as they are built.
Metadata lives in a different place in every format, and removing it safely is not simply deleting bytes. MP4 sample tables hold absolute file offsets — delete a box in front of them and the video stops playing. WebM records byte positions in its seek index. Getting this right once took real work.
Only the container is rewritten, so the encoded picture or video is copied through untouched. The work is set by the size of the metadata rather than the size of the file, and no CPU is spent transcoding. How large a file may be is decided by the API’s upload limit, not by the operation.
Every clean and edit re-reads the produced file and returns a report measured from the output. You can log what was actually removed rather than what was requested.
Strip location and device data from user uploads before they are published, so a photographer posting from home is not publishing their address.
Read the full metadata of ingested assets to populate a catalogue, and normalise or correct fields across a library.
Offer metadata inspection and cleanup inside your own editor without writing a parser for every container format.
Automate metadata removal as a step in a data-minimisation pipeline, with a verification report for each file processed.
Clean files on the way in or out, where re-encoding would be unacceptable and speed matters.
Remove seller-identifying metadata from listing photos automatically, before they reach a public page.
That is a conversation worth having. The engine has no native dependencies and no database, so it deploys as an ordinary Node service — but the licensing for self-hosting needs to be agreed rather than assumed. Get in touch.
Published plans carry monthly call allowances, and Enterprise volume is agreed case by case. Because nothing is transcoded, throughput is bound by I/O rather than CPU, which makes it cheaper to scale than it might look.
The HTTP API is what you can integrate against today: our OpenAPI 3.1 specification generates typed clients for Python, Go, Java, C# and other languages in seconds. The engine itself is a single TypeScript package with no runtime dependencies, identical in a browser and in Node — but it is not published to any public registry. Running it inside your own process is a conversation with us rather than an `npm install`. Ask.
On Enterprise agreements, as part of the contract. The self-serve plans do not carry one.