Developers
Built to be inspected, not just trusted.
Notes on how Documateo actually works, for anyone evaluating it as infrastructure rather than just a tool.
Most tools ship zero bytes to a server
30 of 48 tools run entirely client-side via WebAssembly and native browser APIs (Canvas, Web Crypto, File System Access). If you're evaluating us for a workflow involving sensitive documents, that's a structural property of those tools, not a policy promise layered on top.
Server-side tools run on isolated, ephemeral compute
Video transcoding, Office conversion, and PDF repair run in short-lived containers with a read-only filesystem and no persistent state between jobs. Nothing you upload shares infrastructure with another user's job.
Files don't linger
Anything that does touch a server is deleted on a fixed schedule — every job gets a 2-hour expiry at creation, and an automated hourly sweep deletes anything past that expiry, so cleanup never depends on a person remembering to run it.
An API is coming
Programmatic access to every tool, API-key authenticated, is in development for Business plans.
See the API roadmap →Full technical detail on file handling and infrastructure is in our Data Security page.