System requirements

DOCSUPRA installs nothing on the endpoint. It needs a modern browser, and for downloads, a path to one API host. Everything else on this page is what an IT team asks before allowing it.

Browsers

Platform	Supported	Notes
Windows 10/11	Chrome 110+, Edge 110+, Firefox 115+	Enterprise-managed browsers are fine; no extension is used.
macOS 12+	Safari 16+, Chrome 110+, Firefox 115+	HEIC photos decode natively in Safari; other browsers use the built-in converter.
iOS / iPadOS 16+	Safari, Chrome	Installable as an app from Share → Add to Home Screen; camera capture supported.
Android 10+	Chrome 110+, Samsung Internet 20+	Installable; camera capture supported.
ChromeOS	Chrome 110+	Installable.

Required browser features: JavaScript, HTML canvas, Web Crypto (for SHA-256 receipts), localStorage, service workers (for offline use; optional). Private/incognito windows work but keep no licence between sessions.

Network: hosts to allow

docsupra.com           application (HTTPS 443)
api.docsupra.com       licence checks; JSON only; no file upload endpoint exists
js.stripe.com, api.stripe.com, checkout.stripe.com, hooks.stripe.com, merchant-ui-api.stripe.com
                           payment pages only (not needed for daily use once licensed)
static.cloudflareinsights.com, cloudflareinsights.com
                           optional cookie-free page counter; blocking it changes nothing

These are the only hosts the page may contact; the browser enforces the list through the Content Security Policy. TLS-inspecting proxies are compatible provided they pass WebSocket-free HTTPS to these hosts. Bandwidth: the application is about 470 KB compressed on first load and cached afterwards; documents never leave the machine, so there is no upload traffic.

Virtual desktops and shared workstations

Seats are counted per person, so shared workstations, VDI pools and non-persistent profiles do not consume extra seats: a member signs in and their seat follows them.
Non-persistent profiles lose the browser cache, so the application reloads (about half a second on a corporate line) and, for individual plans, the licence must be restored from the receipt link. Team and Studio licences are restored by signing in.
No local files are written except what the user chooses to download.

Offline operation

Once loaded, the application works without a network connection: auditing, correction and preview all run locally. Downloads on a paid plan need one request to the licence host; if it is unreachable the download waits and the work is not lost. This is also the simplest way to verify the no-upload claim: switch the network off and keep working.

Performance

A 12-megapixel document photo is corrected in one to four seconds on a 2019-era laptop; a batch of 300 ID photos audits in about two minutes. Memory use peaks at roughly 4× the decoded image size. No GPU is required.

Storage on the endpoint

localStorage holds the licence token, preferences and the Enterprise Studio intake answers (a few kilobytes). The Enterprise Studio audit log (file names, hashes and verdicts, never images) is kept in the browser’s IndexedDB until cleared by the user. Clearing site data removes all of it; the software then behaves as on a first visit.