Native protocol
Wire format for the direct-address QUIC session: framing, manifests, resume probes, and compatibility negotiation. Read →
Documentation
Read the bits that matter
FileFerry's docs are intentionally narrow: they describe what is implemented today and what is on the roadmap, not aspirational marketing.
Reference pages
Security and trust
Device identity, trust-on-first-use, fingerprint pinning, destination path safety, and PSK mode. Read →
Daemon mode
Long-running headless receive mode, persisted daemon config, and the current trust boundary. Read →
Project status
What ships today, what is in progress, and the phase order through 1.0. Read →
Releases
Tagged releases, signing plan, distribution targets, and how to verify a build. Read →
Hosted send portal
Threat model, transport constraints, encryption, retention, abuse guardrails, and deployment plan for the future send.fileferry.app surface. Read →
Source of truth
The canonical references live in the repository — these pages summarize them. For the latest detail, read:
README.md— product positioning and target UX.BUILD.md— active build plan, milestone checklist, verification commands.AGENTS.md— durable operator and engineering rules for the repo.docs/protocol-native.md— the native protocol reference.docs/architecture.md,docs/discovery.md,docs/security.md,docs/daemon.md,docs/performance.md,docs/release.md,docs/send-web.md, anddocs/cli-json.md— durable implementation notes as each slice settles.
Everything lives in the same Git repository at github.com/dunamismax/fileferry.