Self-hosted PDF toolkit
Merge, split, compress, convert, OCR, redact and sign — every tool runs on your own hardware and your files are wiped the instant your download starts.
Google verifies your identity. Squish then encrypts your vault before storing it.
Your SMTP parameters are encrypted locally in your browser with AES-256-GCM. Enter your PIN to unlock.
Portable backups use a separate 12+ character passphrase, PBKDF2-SHA256 (300,000 iterations), and AES-256-GCM. Server (.env) credentials are never exported.
Server-side profiles live in this server's .env file, which only opens up with an API_KEY — but you almost certainly don't need to invent one: if you haven't set API_KEY yourself, Squish already generated one the first time it started and saved it into backend/.env (it also printed it to the server's startup log). Open that file, copy the API_KEY="…" value, and paste it below — no restart needed, this page just has no way to read that file for you.
backend/.env or the startup log — or click Generate if you'd rather pick your own.
Still failing? The value above doesn't match what the server is actually using. That means one of:
backend/.env and copy API_KEY="…" fresh.To pin your own value instead of the auto-generated one: put it in the server's environment (export API_KEY=<value> before starting locally, or the API_KEY: line in docker-compose.yml) or as a plain API_KEY= line in backend/.env, then restart the server and enter that same value here.