Built to keep sensitive work local.
DevPantry reduces exposure by running its utilities in the browser. This page explains the protections we rely on—and the limits you should understand before using any web application.
Security architecture · Last updated October 3, 2026
On-device execution
Tool inputs are processed by browser APIs instead of a DevPantry processing backend.
In-memory token work
JWT inspection and signing use browser memory and WebCrypto where supported.
No account surface
There is no account, password, or saved workspace to protect.
How the tools are isolated
Image, PDF, JSON, and JWT tools process their inputs locally. The collaborative editor uses browser-side AES-GCM encryption for document updates, a WebSocket relay, and encrypted update storage in a Cloudflare Durable Object. It also keeps local document state in IndexedDB.
The server relay handles encrypted document updates rather than the plaintext document. File-processing tools do not upload source images or PDFs. Usage analytics and other network features are described in the privacy policy.
Security boundaries
Client-side processing protects data from being sent to DevPantry for tool execution. It cannot protect a compromised device, a malicious browser extension, copied output, or data shared with another website after export. Review sensitive output before saving or sharing it.