SafeShare

Spec sheet

Purpose

SafeShare is a self-hosted file-sharing service with automatic expiration and no required accounts.Read 12 Oct 2026 · github.com

Intended users

The deployment guide names whistleblowers, journalists, activists, corporate file-transfer users, and organizations with compliance requirements as example audiences for different configurations.Read 12 Oct 2026 · github.com

Deployment

The README documents Docker deployment and a downloadable Linux amd64 binary, plus an installable PWA.Read 12 Oct 2026 · github.com

Integrations

The project documents an API, webhooks, and Python, TypeScript/JavaScript, and Go SDKs for programmatic access.Read 12 Oct 2026 · github.com

Compliance

The deployment guide maps features to HIPAA, SOC 2, GDPR, and PCI-DSS requirements; it describes Fortress mode for regulated industries.Read 12 Oct 2026 · github.com

Support

The project directs bug reports and feature requests to GitHub Issues and security reports to its security channel.Read 12 Oct 2026 · github.com

License

The repository README identifies SafeShare as MIT licensed.Read 12 Oct 2026 · github.com

Accounts and access

Optional user accounts support invite-only registration, MFA, and SSO; the security guide also describes role-based access and anonymous uploads.Read 12 Oct 2026 · github.com

Administration

An optional admin dashboard supports file management, user administration, and system configuration.Read 12 Oct 2026 · github.com

API access

YesRead 23 Sep 2026 · github.com

At-rest encryption

The README says configuring an encryption key enables AES-256 encryption at rest for stored files.Read 12 Oct 2026 · github.com

Authentication

Optional user accounts support invite-only registration, role-based access, MFA, and SSO.Read 12 Oct 2026 · github.com

Browser encryption

Optional end-to-end encryption encrypts files in the browser with AES-256-GCM before upload, so the server does not receive the plaintext or decryption key.Read 12 Oct 2026 · github.com

Compliance limits

The README describes a Fortress mode for regulated industries but says PostgreSQL/S3 support and malware scanning are planned, not yet supported.Read 12 Oct 2026 · github.com

Deployment options

The README gives Docker and Docker Compose deployment instructions and a Linux amd64 binary download.Read 12 Oct 2026 · github.com

Download tracking

YesRead 23 Sep 2026 · github.com

Encryption at rest

When configured, SafeShare encrypts stored files with AES-256-GCM; losing the encryption key means the files cannot be recovered.Read 12 Oct 2026 · github.com

Encryption limit

End-to-end encryption keeps the whole file in browser memory twice and the documentation warns about files larger than 500 MB.Read 12 Oct 2026 · github.com

File controls

Uploads can have automatic expiration, download limits, and password protection.Read 12 Oct 2026 · github.com

Large files

SafeShare supports resumable uploads and downloads for large files.Read 12 Oct 2026 · github.com

Metadata limit

Metadata stripping does not support HEIC/HEIF, FLAC, WAV, OGG, WebM, or legacy Office formats, and does not remove Office comments or tracked changes.Read 12 Oct 2026 · github.com

Notable limit

The repository says PostgreSQL, S3, and malware scanning are planned but not yet supported in Fortress mode.Read 12 Oct 2026 · github.com

Privacy features

Anonymous mode redacts IP addresses from logs and the database, and metadata stripping can remove identifying metadata from supported file types.Read 12 Oct 2026 · github.com

Security caveat

The API reference says production deployments must run behind HTTPS.Read 12 Oct 2026 · github.com

Sharing controls

Uploads can have expiration times, download limits, and optional password protection.Read 12 Oct 2026 · github.com

Webhook security

Webhook deliveries can include SHA-256 HMAC signatures, including a timestamped signature described as replay-resistant.Read 12 Oct 2026 · github.com

Where Specifiction places it

• File transfer services#81 of 1057.6