Secure document intake

Secure document intake without a portal.

Sprag gives outside senders a one-way upload page for sensitive files. They can submit documents and leave without getting an account, folder, listing, workspace, or download path.

What it means

Secure intake is narrower than secure file transfer.

Generic transfer tools move files between people. Sprag receives documents into an operator-controlled intake boundary. The sender does not become a collaborator, and the upload page does not become a shared drive.

Accountless

The sender does not join your platform.

Clients, sources, employees, applicants, and partners can upload without creating a user account or installing a sync client.

One-way

No folder leaks back out.

Uploaders can submit files and keep a receipt, but they cannot browse, retrieve, edit, or delete submitted material.

Sovereign

The intake path belongs to the operator.

Run Sprag on infrastructure and S3-compatible storage you choose instead of routing sensitive intake through a default cloud drive.

Hardening path

Start simple, then harden the same intake shape.

Self-hosted

Run it as a small file drop.

Use Sprag as a plain HTTPS intake box when the server may read submitted files and simple deployment matters most.

Self-hosted file drop

Security model

Require E2E or onion-only ingress.

Use server-blind E2E when stored uploads should be ciphertext to the server, or onion-only deployment when uploaders should not reach a clearnet host.

Security model