Security
Last reviewed · August 2026
Your work stays yours.
Pluribus is built so the most sensitive thing in a production — the work itself — never has to be trusted to us. Media, prompts, and graphs stay in your workflow. The record travels as structured fields and SHA-256 fingerprints.
01The record travels. The media doesn’t.
Pairing syncs a narrow, allow-listed set of structured fields — enough to hold the record together, and nothing that spends a client’s trust. Unreleased creative never touches Pluribus at all.
Stays in your workflow
- Images, video, and renders
- Models, LoRAs, and character sheets
- Graph JSON and filenames
- Prompts and node IDs
- Local source paths
- The private map from local files to record references
What the record carries
- Project and people fields you enter
- Source kinds and classifications
- Normalized operation classes
- Structured intended-use fields
- Confirmation requests with stable IDs
- SHA-256 graph fingerprints — the proof, never the graph
Nothing here trains a model. Not the fields, not the fingerprints — and the media never arrives in the first place.
02A record that proves itself.
Every action in a workspace lands in an append-only audit log. Each entry carries the SHA-256 hash of the entry before it, computed in the database — one continuous chain from the first event to the newest.
person.linked
9f2c…41aa
prev 0000…0000
confirmation.recorded
b7e1…08cd
prev 9f2c…41aa
record.frozen
5d4a…9e37
prev b7e1…08cd
Alter one row — even a timestamp — and the break is loud and locatable. That’s an audit trail in the chain-of-custody sense: tamper-evident, not just kept.
03Isolation lives in the database.
The controls a security questionnaire asks about, already in place — starting where the data actually lives.
Row-level security, every table
Postgres enforces workspace separation on every table. Another workspace’s rows aren’t hidden by the application — they’re unreachable, by database rule.
Sign-in without passwords
Access is a one-time email link. No passwords to phish, reuse, or breach.
Every entry point metered
Per-endpoint rate limits keep automated guessing a dead end.
Encrypted in transit and at rest
TLS 1.2+ on every connection, AES-256 at rest. The stack is small on purpose — Vercel, Supabase, Resend — a short list to secure and a short list to audit.
05The boundary is auditable.
The one Pluribus component inside your workflow — the ComfyUI plugin — is GPL-3.0 open source. What pairs, what syncs, what stays: every line is public.
06Put us under review.
Running vendor diligence? Bring the questionnaire — we’ll walk your team through the architecture, from the boundary to the chain. Vulnerability reports go straight to the people who wrote the code.