End-to-End Encrypted · No Size Limits · Cross-Platform

How ShareBolt Works: Any File. Any Size. Any Device. Anywhere.

ShareBolt is a zero-knowledge file transfer platform that encrypts your files on-device before they ever leave your hands — then routes them through the closest Cloudflare edge node directly to your recipient, whether that's a human user, a remote team, or an autonomous AI agent. There are no file size limits, no server-side decryption, and no compromise on compliance.

Step-by-Step: How a Transfer Works

Every ShareBolt transfer follows a six-stage cryptographic pipeline. Each stage is designed to ensure that no plaintext data — and no encryption key — ever touches a server you don't own.

STEP 01

Initiate — Choose Your File(s)

Select any file or folder from any device: a 4K video from your iPhone, a 200 GB model checkpoint from your Linux workstation, or a document from your web browser. ShareBolt imposes no format restrictions and no per-file size caps. Drag-and-drop, folder upload, or CLI — all supported.

STEP 02

Encrypt — AES-256-GCM Client-Side

Before a single byte leaves your device, ShareBolt runs AES-256-GCM encryption entirely on-device using the Web Crypto API (browser) or native crypto primitives (desktop/mobile). Your encryption key is derived from your vault passphrase using PBKDF2 — it is never transmitted to ShareBolt infrastructure, ever.

STEP 03

Package — Zero-Knowledge Tokenization

The encrypted ciphertext is tokenized with a stable blind index — a deterministic hash that allows the ShareBolt search layer to locate your file without knowing its content. File names, MIME types, and metadata are encrypted separately. The server sees only opaque ciphertext blobs and anonymous index tokens.

STEP 04

Route — Nearest Cloudflare Edge Node

The encrypted payload is routed to the Cloudflare edge node geographically closest to the originating request. If you are subject to GDPR, EU data residency headers ensure the file never transits a non-EU zone. HIPAA and CCPA routing rules can similarly be enforced at the header layer, automatically.

STEP 05

Deliver — Client-Side Decryption

The recipient — whether a human, a remote team member, or an autonomous AI agent — receives the encrypted blob. Their client (browser, app, or SDK) decrypts it locally using the shared vault key or a one-time transfer token. No plaintext ever exists on ShareBolt infrastructure at any point in the delivery chain.

STEP 06

Log — Immutable Cryptographic Ledger

Every transfer event — initiation, routing decision, delivery confirmation — is appended to an immutable cryptographic ledger as a hash-chained block. This tamper-evident audit trail satisfies SOC2 Type II, HIPAA, and GDPR audit requirements without storing any plaintext event data.

Works on Every Device and Platform

ShareBolt is engineered for true cross-platform coverage. Whether your team runs iOS in the field, Linux on inference servers, or Windows in the enterprise — every transfer is protected by the same AES-256-GCM pipeline.

iOS

Flutter app with background transfer support, Face ID vault unlock, and native iOS share sheet integration.

Android

Flutter app with background transfers, biometric authentication, and Android share sheet support.

Windows

Native desktop client with shell integration for drag-and-drop vault uploads.

macOS

Flutter desktop app with menu bar integration and Apple Silicon hardware acceleration.

Linux

CLI and daemon modes for headless servers, CI/CD pipelines, and AI inference nodes.

Web Browser

Zero-install experience in Chrome, Firefox, Safari, and Edge via the Web Crypto API.

Transfers of Any Size — No Limits

ShareBolt's BYOS (Bring Your Own Storage) architecture eliminates size restrictions by routing encrypted payloads directly to your own cloud storage backend — whether that's Cloudflare R2, AWS S3, or Azure Blob. ShareBolt never buffers your file on shared infrastructure. This means a 10 TB genomics dataset and a 200 KB config file go through the same encrypted pipeline with zero per-file overhead.

For teams without dedicated storage, the Standard Shield tier provides up to 2 GB per transfer using ShareBolt-managed encrypted storage — sufficient for most document, code, and media workflows. Upgrade to Pro Vault or Enterprise Citadel to unlock unlimited file sizes and bring your own storage bucket.

Transfer Method Max Size Encrypted? Agent-Compatible?
Standard Shield 2 GB ✅ Yes ✅ Yes
Pro Vault (BYOS) 25 GB per file (BYOS storage unlimited) ✅ Yes ✅ Yes
Enterprise Citadel Unlimited ✅ Yes ✅ Yes
Legacy consumer tools 20–200 GB ❌ Server-side only ❌ No

Agent-to-Agent File Transfer

Modern AI pipelines don't just move data between humans — they move it between autonomous agents. A Claude worker generating a report needs to hand that file to a GPT-4 summarizer, which then delivers it to a n8n webhook node that archives it in a compliance bucket. This entire chain requires a file transfer protocol that understands agent identity, has no GUI dependency, and enforces security boundaries automatically.

ShareBolt's Agent SDK gives each AI agent a cryptographic DID (Decentralized Identifier) for authentication, a sandboxed directory allow-list so no agent can read files outside its approved scope, and a daily byte quota to prevent runaway data exfiltration. Transfers between agents are zero-knowledge encrypted end-to-end and logged to the immutable ledger — making them auditable even in fully automated pipelines. Every major LLM platform is supported out of the box.

How ShareBolt Works — Key Takeaways

  • AES-256-GCM on-device encryption: files are encrypted in-browser using the Web Crypto API before any byte leaves your device — ShareBolt servers never see plaintext.
  • HKDF-SHA256 perfect forward secrecy: each transfer step ratchets two fresh 256-bit keys; compromising one transfer does not expose past or future ones.
  • Ed25519 DID agent identity: AI agents authenticate with ephemeral challenge signatures — no shared API keys, no credential rotation risk, no server-side secret storage.
  • Resumable chunked uploads: each chunk is individually SHA-256 verified; a dropped connection resumes from the last verified chunk without re-uploading earlier data.
  • BYOS removes all file size limits: Enterprise + BYOS writes encrypted chunks directly to your R2 (S3/Azure/GCS on roadmap) — ShareBolt never buffers or proxies the file data.
  • SHA-256 tamper-evident audit ledger: every transfer block records sender, recipient, file hash, region, and timestamp; altering any field breaks the hash chain for all downstream blocks.

Frequently Asked Questions

Can I transfer files of any size?

BYOS removes storage caps. Individual file size limits still apply per plan (25 GB for Pro, unlimited for Enterprise with BYOS). Standard Shield supports up to 2 GB per transfer.

Does it work without installing an app?

Yes. The web interface runs entirely in modern browsers using the Web Crypto API for on-device encryption. No plugin or extension needed. Native apps are also available for Windows, macOS, Linux, iOS, and Android.

How are AI agents able to share files?

AI agents authenticate with Ed25519 DID cryptographic identities via the ShareBolt Agent SDK or REST API. Each agent operates in a sandboxed file path with a daily byte quota. Supported: Claude (MCP), GPT-4 (function calling), Gemini (tool use), and any LLM via REST.

Is the transfer encrypted end-to-end?

Yes. AES-256-GCM encryption runs entirely on-device before upload. Keys are derived locally via HKDF-SHA256 and never transmitted. No ShareBolt server or employee can access plaintext file content at any stage.

What storage backends does BYOS support?

Currently Cloudflare R2. S3, Azure Blob, GCS, and MinIO are on the roadmap. ShareBolt encrypts before writing to your bucket, so your cloud provider also never sees plaintext. You retain full data ownership.

How long are transfer links valid?

Pro and above plans can set expires_in_seconds=0 to create permanent links that never expire. Standard Shield links expire after 7 days. Enterprise supports policy-enforced expiry rules per team or compliance zone.

Can I send to someone without a ShareBolt account?

Yes. Recipients get a one-time secure download link. They decrypt the file in their browser using the shared key with no account required. For agent-to-agent transfers, both ends need an API credential or DID identity.

Is there an audit trail for every transfer?

On Ledger Guard and Enterprise plans, every transfer is written to an immutable SHA-256 block chain ledger. The ledger records sender, recipient, file hash, region, and timestamp. Any tampering breaks the hash chain and is immediately detectable.

What happens if a transfer fails mid-way?

ShareBolt uses chunked uploads with resumable transfer tokens. If a connection drops, the transfer resumes from the last verified chunk. Each chunk is individually integrity-verified with SHA-256 before the token advances.

Start Transferring for Free

No credit card required. Unlimited transfers on the free tier up to 2 GB. Upgrade any time for BYOS and agent workloads.