Automation

The anonymization logic that runs in the desktop app also works at the command line and on a shared server.

CLI batch anonymization

Point piixie anonymize at a folder and it processes every supported file:

piixie anonymize ./raw-documents \
  --mode synthetic \
  --out ./safe-documents

Use CLI jobs for source folders, CI test fixtures, support exports, or recurring reports that need anonymization before sharing. Modes and profiles work the same as in the app.

Server mode

Run a shared Piixie server so each team member doesn’t carry the local compute cost:

piixie server \
  --host 0.0.0.0 \
  --port 8787

Desktop apps on the network connect to the server and submit documents there instead of running the model locally. The dedicated local server guide covers hardware sizing, GPU acceleration, and connecting the UI.

Recommended policy

• Keep raw documents where they belong, not in prompt tools.
• Store anonymized outputs separately and mark them as derived files.
• For synthetic mode, review generated replacements before using them as examples.
• For shared servers, add authentication, logging, and retention rules at the network layer.

Architecture

The desktop app, CLI, and server share one anonymization core:

Desktop app ─┐
CLI batch ───┼─→ Piixie core ─→ model (local or server GPU)
Server ──────┘        │
                      └─→ anonymized output ─→ optional downstream LLM