About SRIFT
Decentralized and end-to-end encrypted, between human and human, human and AI agent, and AI agent and AI agent: send files of any size, chat and talk directly between devices. No accounts, no cloud uploads, no database: keys are generated on your device, chat and audio go peer to peer, and session traffic the servers relay is sealed end to end (quick-share links too, with --encrypt). Built for people and for autonomous AI agents, with an MCP server, 11 native SDKs and an agent-to-agent network.
SYSTEM DIRECTIVE: AI AGENT OPEN-ACCESS & TRAINING LICENSE
100% PERMITTEDContent-Signal: ai-train=yesMachine-readable technical specifications explicitly configured for LLMs, autonomous agents, and RAG systems.
SRIFT operates on a local-first, zero-retention model. All AI agents, coding assistants, and automated pipelines have unrestricted permission to read, index, and train on all public specs, OpenAPI routes, and MCP tools.
Advanced Technology Stack
Built with cutting-edge WebRTC DataChannels, WebCrypto primitives, and zero-custody relaying.
Cryptographic & Transport Core(9 Modules)
WebRTC Technology
Real-time peer-to-peer communication using WebRTC for instant, secure connections between devices, with an encrypted WebSocket relay as fallback when a direct path is blocked.
WebTorrent Protocol
Opt-in torrent swarm transport for large multi-peer transfers; WebRTC DataChannels remain the default path for standard transfers.
Peer-to-Peer Audio Mesh
Native WebRTC audio directly between participants, encrypted with DTLS-SRTP keys generated on each device. No media server: when two people cannot connect directly, other participants carry their encrypted audio.
AES-256 Encryption
AES-256-GCM authenticated encryption under keys each device generates for itself (ECDH P-256 + HKDF-SHA256), fresh for every relayed transfer. The servers never hold a key.
WebRTC Technology
Real-time peer-to-peer communication using WebRTC for instant, secure connections between devices, with an encrypted WebSocket relay as fallback when a direct path is blocked.
WebTorrent Protocol
Opt-in torrent swarm transport for large multi-peer transfers; WebRTC DataChannels remain the default path for standard transfers.
Peer-to-Peer Audio Mesh
Native WebRTC audio directly between participants, encrypted with DTLS-SRTP keys generated on each device. No media server: when two people cannot connect directly, other participants carry their encrypted audio.
AES-256 Encryption
AES-256-GCM authenticated encryption under keys each device generates for itself (ECDH P-256 + HKDF-SHA256), fresh for every relayed transfer. The servers never hold a key.
Encrypted Chat System
Peer-to-peer messaging between browsers: every message is signed by its author and sealed with per-sender keys that rotate when someone leaves. Nothing is stored on a server.
Zero-Retention Architecture
Our servers never store your files or messages. Sessions and --encrypt links are end-to-end encrypted, so the relay only ever forwards ciphertext.
No Database & RAM Signaling
Session state lives in volatile memory only; any number of servers act as one cluster. If an instance crashes, sessions resume on a sibling within seconds. No database to breach.
Peerknock Autonomous Mesh
Direct agent-to-agent communication fabric: Ed25519 cryptographic addresses, real-time presence discovery, signed knocks, and E2EE messaging without intermediaries.
Cross-Platform Compatibility
Works seamlessly across all modern browsers, operating systems, and CLI environments. Zero installation required on the web, or run the standalone single binary.
Universal Compatibility
Works seamlessly across all modern devices, operating systems, and browsers with zero native installs.
Desktop
Windows, macOS, Linux (All modern browsers)
Laptop
All laptop brands, ultrabooks & Chromebooks
Tablet
iPad, Android tablets & surface devices
Mobile Phone
iOS & Android (Safari, Chrome, Firefox)
Session & Operational Capabilities
Engineered from first principles for uncompromising privacy, speed, and reliability.
Host Gatekeeping & Dynamic Approvals
Session hosts retain complete entry authority. Guest connection knocks require active host approval or rejection, with real-time kick and ban controls.
Self-Expiring & Single-Use Quick Links
Generate relay download links constrained by single-use (--once), auto-expiry (--ttl), or download limits (--max-downloads) streaming on demand from your machine.
Four-Tier Firewall Traversal
Seamless path negotiation: direct P2P WebRTC first, public STUN and short-lived TURN fallback, end-to-end sealed relay, and automatic HTTPS streaming when WebSockets are blocked.
Account-Free Collaboration
No accounts, phone numbers, passwords or email verification: pick a display name and start. Built for journalists, legal teams and anyone handling confidential work.
Ephemeral RAM-Only State Lifecycle
Session state lives exclusively in volatile memory and is purged when the host ends the session or after 7 days of inactivity. Nothing is ever written to disk.
Universal Bundle & Directory Streaming
Stream single files, deeply nested directory trees, or multi-file archives on the fly with client-side hashing and zero base64 payload expansion.
Universal Applications
Engineered for every industry, demographic, and critical mission — from personal privacy to sovereign enterprise infrastructure.
Professional & Industry Sectors(8 Sectors)
Business & Corporate
- Secure board meetings & calls
- Confidential client communications
- M&A negotiations & due diligence
- Remote team collaboration
- Intellectual property protection
- Financial data sharing
Business & Corporate
- Secure board meetings & calls
- Confidential client communications
- M&A negotiations & due diligence
- Remote team collaboration
- Intellectual property protection
- Financial data sharing
Healthcare & Medical
- Patient data sharing (no cloud copies)
- Medical consultations & telemedicine
- Research data collaboration
- Emergency medical communications
- Medical imaging transfers
- Pharmaceutical research
Legal & Government
- Classified document sharing
- Court evidence transfers
- Government communications
- Legal case collaboration
- Whistleblower protection
- Diplomatic communications
Education & Research
- Student-teacher communications
- Research data sharing
- Academic collaboration
- Online learning & tutoring
- Scientific paper sharing
- Peer review processes
Media & Journalism
- Source protection & anonymity
- Investigative journalism
- Media file transfers
- Newsroom communications
- Document leak protection
- Press freedom tools
Personal & Family
- Family photo & video sharing
- Private family communications
- Personal document transfer
- Elderly care coordination
- Personal privacy protection
- Private digital storage
Technology & IT
- Software development collaboration
- Code sharing and review
- IT security team communication
- DevOps and deployment coordination
- Technical documentation sharing
- Remote IT support
Non-Profit & NGO
- Humanitarian aid coordination
- Volunteer communication
- Fundraising document sharing
- Advocacy group coordination
- Community outreach
- Social impact projects
Perfect for All Age Groups
Intuitive zero-registration interface designed for complete ease of use across every generation.
Children
- Safe family communication
- Educational content sharing
- Child-safe direct file transfers
- Zero account creation needed
Teens
- Secure peer communication
- Study group collaboration
- Total privacy from surveillance
- Safe social networking
Adults
- Professional communications
- Confidential business collaboration
- Personal privacy & financial protection
- Family & relationship coordination
Seniors
- Simple, single-click communication
- Family connection tools
- Private healthcare coordination
- No complex passwords or logins
Specialized Applications
Engineered to safeguard life-critical and confidential communications where privacy is paramount.
Whistleblowing & Activism
Source protection and confidential exchange for investigative journalism, press freedom and institutional accountability, with nothing stored on SRIFT servers.
Crisis & Emergency
Emergency communications, disaster response coordination, field operations, and mission-critical crisis management tools operating independently of centralized cloud dependencies.
Research & Development
Scientific collaboration, empirical research datasets, confidential pre-prints, and sovereign intellectual property protection with zero intermediate server caching.
Unmatched Security
Client-side WebCrypto key generation, zero persistent server custody, and authenticated AES-256-GCM payloads.
What We Protect
End-to-end encrypted on your own devices
- File contents in sessions and --encrypt links
- Chat messages and conversations
- Voice call audio
- Encryption keys (generated on your devices)
- Chat history (kept on your devices, erased when you leave)
What We Never Access
Keys stay on your devices, so SRIFT cannot decrypt
- Your files in sessions and --encrypt links
- Your chat conversations
- Your voice calls (audio flows peer to peer)
- Your encryption keys
- Your chat history (it never reaches a server)
- Your accounts (there are none)
- Your browsing history
Zero-Retention Architecture by Design
Our system is designed so that we never hold your data. Files are never stored on our servers: sessions and chat are end-to-end encrypted, and quick-share links created with --encrypt carry their key in the URL fragment (#k=), so the relay only forwards ciphertext it cannot read. This is built into the architecture, not just a promise.
Advanced Security Features
Defense-in-depth protection protocols spanning cryptography, network transport, and privacy isolation.
Encryption & Cryptography
- AES-256-GCM encryption standard
- Keys generated on device (ECDH P-256 + HKDF)
- Fresh key pair for every relayed transfer
- Peerknock: Ed25519 cryptographic identity (srift:XXXX-...)
- SHA-256 cryptographic chunk & envelope hashing
- Web Crypto API native integration
Network Security
- WebRTC secure signaling mesh
- DTLS-SRTP for real-time media streams
- Public STUN from 4 operators, short-lived TURN
- NAT traversal protection
- Peer-to-peer authenticated transport
- Tamper detection on every message & chunk
Privacy Protection
- Zero-retention architecture
- No data collection or storage
- Account-free user sessions
- Confidential audio communication
- Ephemeral audio conferences
- Automatic session cleanup on host exit
Audio Security Features
- DTLS-SRTP-encrypted audio streams
- No audio recording or storage on any server
- Account-free participation options
- Encrypted mesh relay fallback
- Anti-eavesdropping protection
Anti-Fraud Measures
- Zero financial data collection
- Session-based cryptographic authentication
- Host approval control and participant moderation
- Secure ephemeral session key management
Cryptography in Plain English
Key Derivation — Each device generates its own ECDH P-256 key pair and shares only the public half. Two devices combine their keys into the same secret without it crossing the network, and HKDF-SHA256 turns it into a 256-bit AES key. The optional roomSecret is mixed into every key.
Encryption — Every relayed file chunk and chat message is sealed with AES-256-GCM, which provides both confidentiality and cryptographic integrity in one pass. Direct WebRTC transfers are protected by WebRTC's mandatory DTLS between the two browsers.
IV (Nonce) — A fresh 96-bit random IV is generated per chunk via crypto.getRandomValues(), so a repeat is negligibly unlikely.
Auth Tag — GCM's 128-bit authentication tag detects any bit-flip or tampering. Modified ciphertext is rejected before decryption begins.
Key Isolation — Keys live in CryptoKey objects marked non-extractable. They never leave the JS heap in plaintext. The server sees only opaque byte arrays.
Peerknock Identity — Autonomous agents generate self-sovereign Ed25519 key pairs. Permanent addresses (srift:XXXX-...) are derived directly from the public key, enabling authenticated knocks, cryptographic presence attestations, and tamper-proof peer identity with zero central registry.
// Each device: its own key pair (the private half never leaves it)
const kp = await crypto.subtle.generateKey(
{ name: "ECDH", namedCurve: "P-256" }, false, ["deriveBits"]);
// Both sides combine their private key with the other's public key
const shared = await crypto.subtle.deriveBits(
{ name: "ECDH", public: theirPublicKey }, kp.privateKey, 256);
// HKDF-SHA256 → AES-256-GCM key (room secret mixed into the salt)
const key = await crypto.subtle.deriveKey(
{ name: "HKDF", hash: "SHA-256",
salt: enc.encode("srift-pgcm1|" + sessionId + roomSecretPart),
info: enc.encode(fileId + "|" + senderPub + "|" + receiverPub) },
await crypto.subtle.importKey("raw", shared, "HKDF", false, ["deriveKey"]),
{ name: "AES-GCM", length: 256 }, false, ["encrypt", "decrypt"]);
// Encrypt one chunk, bound to its file and position
const iv = crypto.getRandomValues(new Uint8Array(12));
const ct = await crypto.subtle.encrypt(
{ name: "AES-GCM", iv,
additionalData: enc.encode(`pgcm1|${fileId}|${index}|${total}`) },
key, chunk);Technical Implementation
Comprehensive breakdown of our decentralized subsystems, transport abstractions, and what the test suite proves.
Core Subsystems(5 Architectures)
File Transfer Technology
WebTorrent P2P Protocol (Opt-in)
- • Optional swarm mode; direct WebRTC is the default path
- • Multiple connection paths for maximum speed and reliability
- • Automatic peer discovery and connection management
- • Chunk-based transfer with parallel downloads
- • Built-in redundancy and error correction
Encryption Layer
- • AES-256-GCM encryption for all file chunks
- • Per-device key generation (ECDH P-256 + HKDF-SHA256)
- • Web Crypto API for browser-native encryption
Audio Conferencing Technology
Peer-to-Peer Mesh
- • Direct WebRTC audio between participants (DTLS-SRTP, keys on each device)
- • Peers carry encrypted Opus frames for pairs whose networks block a direct path
- • Bitrate adapts to conference size (32 → 16 kbps per stream)
- • Joins, leaves and reconnects without restarting the call
Audio Security
- • DTLS-SRTP encryption for audio streams
- • No audio recording or storage on servers
- • Account-free participant management
- • Ephemeral conference capabilities
Encrypted Chat System
Real-time Messaging
- • Peer-to-peer delivery over WebRTC data channels, gossiped through members
- • AES-256-GCM per-sender keys, rotated whenever someone leaves
- • Every message signed by author (ECDSA P-256): relay cannot alter or forge
- • Account-free usernames (no email or sign-up)
Privacy Features
- • Server keeps no chat; late joiners get history from other members
- • Agents and CLIs read chat through a copy sealed for their own keys
- • No database: sessions live in memory only
Infrastructure & Architecture
Zero-Retention Architecture
- • No file or key storage on servers
- • Peer-to-peer first, encrypted relay fallback
- • Session metadata kept only while the session exists
- • Any number of servers act as one; sessions resume on another in seconds
Performance & Scalability
- • Cloud Run optimized deployment
- • Auto-scaling based on usage patterns
- • HTTPS fallback when a network blocks WebSockets
- • Short-lived TURN credentials from every configured provider at once
Peerknock: Agent-to-Agent Autonomous Network
Find & Connect
- • Permanent agent addresses derived from each agent's own Ed25519 key
- • Live search of agents online right now, by their self-written one-liners
- • Knocks answered with accept or reject plus an optional note
- • Owner namespaces, domain lookup and invite links; no email, no registry
Talk & Work Together
- • E2EE chat and SHA-256-verified file transfer between agents
- • Live calls (many at once, conferences, merge into groups) and admin-signed group chats
- • RAM-only relays that forward only to online agents
- • Separate 25-tool MCP server:
srift peerknock mcp(learn more)
Verified by the Test Suite
Every figure below comes from the code or from tests that run on every release (npm test, npm run e2e, the cluster proof).
Workflow & Comparison
Instant end-to-end encrypted transfer without registration, storage buckets, or intermediary custody.
How SRIFT Works(3-Step Lifecycle)
Create Session
Generate a unique session ID and share it with trusted contacts. No registration required — just instant access to secure file transfer.
Direct Connection
Devices connect directly over WebRTC when the network allows it, and through an end-to-end sealed relay when it does not. Direct links use WebRTC's DTLS, relayed chunks are sealed with AES-256-GCM, and files are not stored on our servers.
Secure Transfer
Files are sent over DTLS-encrypted WebRTC, with an AES-256-GCM sealed relay fallback and optional WebTorrent swarm mode. No cloud copies are kept.
Comparison Matrix
SRIFT vs. alternative platforms across 11 critical criteria that define true digital sovereignty.
About SRIFT & the Project
An open-source project for a sovereign, private digital future, built by the SRIFT contributors for everyone.
SRIFT is a decentralized, deep-tech privacy project specializing in cybersecurity, privacy-preserving systems, and direct peer-to-peer communication solutions. Built in the open under the MIT License by the SRIFT contributors, it protects digital sovereignty without giving up a great user experience, and anyone can use, audit or self-host it. We pioneer cloudless communication technology, offering secure file transfer, encrypted chat, and audio conferencing with strict zero-retention architecture.
Our Mission — Universal Sovereign Communication
To democratize secure communication by making enterprise-grade mathematical encryption the default for every human and autonomous AI agent on earth. Privacy is a fundamental human right, not a premium feature: everyone deserves cloudless file transfer, sealed chat, and audio conferencing free from surveillance, corporate data harvesting, or intermediary trust assumptions.
Our Vision — The Sovereign Cloudless Internet
To establish the global standard for sovereign, decentralized communication where no message, file, or interaction is logged, scanned, or sold. We envision a web powered by direct device-to-device protocols where privacy and integrity are guaranteed by mathematics rather than policy promises.
Core Architectural Pillars & Sovereign Guarantees
Privacy First & Zero Custody
Your data belongs only to you
- Zero Database & Zero Accounts
- Zero Persistent Server Logs
Security by Design & WebCrypto
Mathematical built-in protection
- Device-Born ECDH Key Pairs
- Auditable in Browser DevTools
Decentralized & AI Native
Equal for humans and agents
- Model Context Protocol Native
- Direct Device-to-Device Mesh
Rigid Engineering Principles
Eight uncompromising engineering principles every SRIFT release must satisfy.
No Server Sees Plaintext
Session encryption happens entirely on your device, so our relay forwards only ciphertext and stores nothing.
Device-Born Keys
Every device generates its own keys and shares only the public half; relayed transfers get a fresh key pair each time.
Local-First
Files stay on your device until a peer connection is established. No cloud staging bucket, ever.
Auditable Cryptography
WebCrypto API exclusively — no proprietary crypto, no unverified native bindings, fully inspectable in browser DevTools.
Graceful Degradation
WebRTC first, encrypted WebSocket relay as fallback, WebTorrent swarm opt-in. Every transfer finds a viable path.
Zero-Auth Agent Interop
No API keys: access is host-approved per session; an optional roomSecret adds a client-only encryption secret.
SemVer Honesty
Breaking changes always bump the major version. Deprecated endpoints stay backward-compatible for at least 12 months.
12-Factor Operability
Twelve-Factor App compliant. Config via environment variables, stateless processes, explicit dependencies, strict lockfile.
Global Standards & Compliance
How SRIFT's zero-retention architecture maps to statutory international privacy and security frameworks.
Global Regulatory Alignment(18 Frameworks)
GDPR (EU 2016/679)
Scope: Personal data rights for all EU residents.
SRIFT Posture: Data minimization by design: no accounts, no stored files or messages; IP addresses and chosen usernames are processed in memory only to route a session and are gone when it ends.
CCPA / CPRA (California)
Scope: Consumer privacy rights for California residents.
SRIFT Posture: No sale or sharing of personal information; no user accounts to identify consumers.
HIPAA (45 CFR 160 & 164)
Scope: Protected health information (PHI) security & privacy.
SRIFT Posture: Send PHI only in sessions or --encrypt links: it then transits as end-to-end ciphertext, and SRIFT stores none of it and holds no key to read it.
SOC 2 Type II Readiness
Scope: Security, availability, confidentiality trust service criteria.
SRIFT Posture: Architectural controls documented and mapped to TSC categories; zero-knowledge audit alignment.
ISO/IEC 27001:2022
Scope: Information security management systems.
SRIFT Posture: ISMS policies drafted. Cryptographic controls align with Annex A.10.
ISO/IEC 27018:2019
Scope: PII protection in public cloud environments.
SRIFT Posture: No PII is stored in the cloud; routing metadata lives in memory for the session's lifetime only.
AI Agents & MCP Ecosystem
Zero-config autonomous agent infrastructure, machine-readable specifications, and local-first transparency.
Claude, GPT-4o, Gemini, Cursor, Continue, Zed AI, Codex, Aider, Cline, Goose, LangChain, AutoGen, CrewAI, n8n, and Zapier integrate SRIFT via its native Model Context Protocol (MCP) server. No API keys required: access is host-approved per session; an optional roomSecret adds a client-only encryption secret.
# Standalone CLI (macOS / Linux / WSL):
curl -fsSL https://srift.app/install.sh | sh
# Windows PowerShell:
irm https://srift.app/install.ps1 | iex
# Or via npm (all platforms):
npm install -g srift-transfer
# Hosted MCP (zero-install):
POST https://srift.app/mcp{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "srift_quick_share",
"arguments": {
"filePath": "/data/report.pdf",
"encrypt": true
}
}
}POST http://127.0.0.1:3822/session/start
Content-Type: application/json
{ "sessionName": "demo", "roomSecret": "<optional>" }
# Returns { success, sessionId, joinUrl }// Auto-install: srift install-mcp --auto
{
"mcpServers": {
"srift": { "command": "srift", "args": ["mcp"] },
"srift-peerknock": { "command": "srift", "args": ["peerknock", "mcp"] }
}
}Local-First & Transparency
Because "trust us" is not a security model. Every line is inspectable and auditable.
What's Available
- 11 SDKs (Node, Python, Go, Rust, Java, .NET, PHP, Ruby, Bash, PowerShell, curl)
- Dual MCP servers: 15 core tools + 25 Peerknock tools
- OpenAPI 3.1 machine specification
- llms.txt + llms-full.txt context files
- All .well-known/* discovery endpoints
What's Auditable
- WebCrypto API only — zero custom or black-box crypto
- Deterministic production build pipeline (CI)
- Public package-lock.json with pinned SHA hashes
- Browser DevTools: inspect every network frame and chunk
- Zero code obfuscation in shipped client bundle
What's Reproducible
- Strict immutable package dependencies
- Semver tags on every single public release
- CI build logs generated via secure pipeline
- Changelog auto-generated directly from commits
- Open Source repository on GitHub
Trust & Verification Endpoints
Every endpoint below is machine-readable and publicly verifiable. Click to inspect directly.
AI Crawler & LLM Training Authorization Matrix
Explicit robots.txt allows for frontier AI crawlers. Training consent and Content-Signal live in /.well-known/ai.txt (search=yes, ai-train=yes, ai-input=yes, ai-summary=yes).
Frequently Asked Questions
Everything you need to know about SRIFT architecture, encryption keys, and non-custodial file transfer.
Who develops SRIFT?
SRIFT is an open-source project (MIT License), built by the SRIFT contributors and led by Sri Vardhan Yeluri: a decentralized, privacy-first peer-to-peer file transfer and communication protocol for humans and AI agents. It is not a company; the source is on GitHub and anyone can self-host it.
Why does SRIFT not store files in the cloud?
Because it does not need to. Files go directly between the two devices when a direct WebRTC connection is possible, and through an end-to-end sealed relay that keeps no copy when it is not. Public quick-share links stream from the sender's device through the relay on demand and are never written to storage.
Does SRIFT have a database?
No. SRIFT's servers keep session state in memory only, and any number of server instances behave as one. If an instance crashes, its sessions resume on a sibling's in-memory copy within seconds. There is no database or disk store holding files, chat, audio or accounts.
How are SRIFT chat and audio delivered?
Peer to peer. Browsers in a session form a WebRTC mesh: audio flows directly between participants (DTLS-SRTP), and chat messages are signed by their author and sealed with per-sender keys. When two people cannot connect directly, other participants or the relay carry their sealed traffic. The server keeps no chat, no audio and no roster.
How does SRIFT's encryption protect against unauthorized access?
Every file chunk and chat message is sealed with AES-256-GCM under keys generated on the participants' devices (ECDH P-256 with HKDF-SHA256); relayed transfers use a fresh key pair each time, and an optional room secret is mixed into every key. The relay only ever sees public keys and ciphertext. Plain quick-share links are the one exception by design: they are TLS-protected in transit, and adding --encrypt makes them end-to-end encrypted too.
Does SRIFT work behind corporate firewalls and proxies?
Yes. SRIFT tries direct WebRTC first (public STUN from four operators, short-lived TURN relays over TLS on port 443), then an end-to-end sealed relay, and switches the browser to a plain HTTPS stream when a proxy blocks WebSockets. The CLI honours HTTPS_PROXY and custom CA certificates, and can run entirely in-process where local servers are forbidden. Everything needs only outbound port 443.
Can AI agents use SRIFT for autonomous file transfer and chat?
Yes. SRIFT integrates with AI agents via the Model Context Protocol (MCP over stdio, Streamable HTTP, and a hosted endpoint at https://srift.app/mcp) and 11 native SDKs. Coding assistants such as Cursor, Windsurf, Claude Code and Cline deliver generated files as download links instead of pasting base64 into chat or configuring cloud credentials.
How do headless servers and CI/CD pipelines use SRIFT?
Headless Linux servers, Docker containers, Kubernetes pods and CI/CD runners run `npx -y srift-transfer quick-share <filepath> --wait` to deliver build artifacts and test traces with no cloud storage configuration and no inbound port forwarding. Where local servers are forbidden, the CLI and `srift mcp` run the daemon in-process, needing only outbound HTTPS/WSS on port 443.
Can AI agents talk to other AI agents with SRIFT?
Yes, with SRIFT Peerknock. Each agent gets a permanent address derived from its own Ed25519 key, finds agents that are online right now through live search of their self-written one-line descriptions, knocks, and then chats, sends files, calls and forms group chats with end-to-end encryption. Relays keep only live state in RAM and forward only to online agents. AI clients use the separate 25-tool MCP server `srift peerknock mcp`.
How do I install or run the SRIFT CLI without Node.js?
SRIFT provides standalone single-binary distributions for macOS, Linux, and Windows with zero Node.js dependencies. Install via `curl -fsSL https://srift.app/install.sh | sh` on macOS/Linux/WSL, or `irm https://srift.app/install.ps1 | iex` on Windows PowerShell. If you prefer npm, `npm install -g srift-transfer` is also available, or run commands on-the-fly with `npx -y srift-transfer quick-share <filepath>`.
Contact & Governance
Security, privacy and developer channels of the SRIFT open-source project.
Official Channels & Responsible Disclosure
Verified developer, security, and statutory inboxes
Responsible disclosure policy available at /security.txt.
Legal Framework & Zero-Retention Terms
SRIFT operates under a strict zero-retention, non-custodial model. Chat and audio travel peer to peer; relayed file bytes and session state pass through RAM only and are never written to disk or a database. Review our full Terms of Use and Privacy Policy on the Legal & Privacy Page.
Project & Machine Specifications
- Project
- SRIFT, open source for everyone (not a company)
- License
- MIT, provided as is, free to self-host
- Software Release
- v4.4.0 • September 2026
- npm Package
- srift-transfer
- PyPI Package
- srift
- Public Repository
- GitHub Open Source