Use case

Private team comms without a phone number, a vendor lock-in, or a server to breach

RVNT gives small businesses and distributed teams end-to-end-encrypted messaging and large-file sharing with no phone-number onboarding and no central server holding your content — but it is a pre-release, unaudited tool with no admin console and no compliance certifications, so it is not a drop-in enterprise IT product.

The threat model

Corporate / industrial espionage: competitors, contract spies, or nation-state-backed actors trying to exfiltrate product designs, deal terms, or trade secrets — a category the U.S. estimates costs the economy between $225B and $600B a year. RVNT keeps content off any server they could compromise.
Server-side breach of your collaboration tool: tools like Slack and Microsoft Teams encrypt in transit and at rest but are not end-to-end encrypted, so a token theft or platform breach (e.g. the 2023 Slack incident, the 1TB Disney leak) can expose private channels. With RVNT there is no central server that stores or relays message content to breach in the first place.
The platform operator and its admins themselves: in Slack/Teams, workspace admins (and the vendor under legal compulsion) can read private messages and export private-channel content via eDiscovery. RVNT has no operator-readable copy — message content is decrypted only on endpoints.
Phone-number / identity correlation during onboarding: tools that require a phone number (e.g. Signal) tie each contractor or vendor to a SIM that can be subpoenaed or used to correlate identity. RVNT identities are local Ed25519 keypairs claimed by proof-of-work — no phone, email, or KYC.
Cloud file-sharing exposure: routing large deliverables (CAD files, video, datasets) through Dropbox/Google Drive/WeTransfer leaves a third-party copy and metadata trail. RVNT transfers stream peer-to-peer with no server copy and strip EXIF/metadata before sending.

Why mainstream apps fall short

Mainstream team chat (Slack, Teams) is server-side encrypted, not end-to-end — the vendor and your own admins can read private messages, and a stolen token or platform breach can expose private channels. That is the wrong trust model for sensitive deal terms, IP, or whistle-stop legal discussions.
Most secure messengers still demand a phone number per user, which is painful and identity-revealing for external contractors, fractional staff, and vendors you don't want to tie to a SIM — and the number can be subpoenaed to reveal who's involved.
Cloud file-sharing for large deliverables leaves a third-party copy and a metadata trail of who sent what to whom and when; size limits and provider scanning add friction and exposure.
Onboarding outside contributors into a managed enterprise suite often means buying seats, provisioning SSO, and accepting vendor lock-in for what may be a short engagement.

How RVNT maps to those needs

Message content that no platform operator, workspace admin, or breached server can read

End-to-end encryption (hybrid X3DH + Double Ratchet, AES-256-GCM) with no central server storing or relaying content

Onboard contractors and vendors without a phone number, email, or KYC

Local Ed25519 identity claimed by proof-of-work — no phone number, no account database

Share large deliverables (CAD, video, datasets) without a cloud copy or metadata trail

Direct peer-to-peer streaming file transfer — no size limit on a direct link, EXIF/metadata stripped, no plaintext on disk, no server copy

Hide who on the team is talking to whom from network observers

Sealed sender plus Tor routing so the network can't map your team's communication graph

Protect captured traffic against future quantum decryption of long-lived secrets

Hybrid post-quantum key exchange (X25519 + ML-KEM-768, NIST Level 3)

The legal & regulatory reality

RVNT is not an enterprise IT or compliance product. It has NO admin console, NO centralized provisioning or audit logging, NO managed backup, and NO compliance certifications or attestations of any kind — no SOC 2, no HIPAA, no signed Business Associate Agreement (BAA), no GDPR/ISO data-processing guarantees. If your organization is legally obligated to retain, supervise, or produce communications (e.g. FINRA/SEC books-and-records, HIPAA, eDiscovery/litigation hold), RVNT's architecture — content stored only on endpoints, nothing on a server — actively works against those obligations and is the wrong tool. RVNT also does not encrypt or protect data on a compromised endpoint; device and OS security remain your organization's responsibility. Treat RVNT as a private peer-to-peer messenger for teams that want it, not as a regulated system of record.

Where RVNT is the wrong tool

RVNT is pre-release software and has NOT undergone a formal third-party security audit. Do not rely on it as the sole channel for anything where a failure would seriously harm your business; use it alongside, not instead of, established tooling until it is independently audited.
There is no admin console, no central user directory, no managed backup, and no compliance certification (SOC 2 / HIPAA / BAA / SEC retention). RVNT cannot satisfy regulated-industry supervision or records-retention requirements, and lost devices can mean lost history — it is not enterprise IT.
RVNT does not protect a compromised endpoint. Malware, an infected laptop, a malicious insider, or a colleague who screenshots a chat all sit outside what encryption can defend. Hardened, updated devices and trust in your contacts are prerequisites.
The 'no size limit' on file transfer applies only to a DIRECT peer-to-peer connection. When two peers can't connect directly and fall back to a relay, transfers are capped at 256 MB until resumable relay ships — never assume unlimited size over a relay.

Frequently asked questions

Can our IT admins, or RVNT itself, read our team's messages?

No. Message content is end-to-end encrypted with the Double Ratchet (AES-256-GCM) and is decrypted only on the participating devices. There is no central server that stores or relays message content, and RVNT ships with no admin console — which is exactly why it cannot offer the centralized supervision, retention, or eDiscovery that some businesses are legally required to maintain. That is the deliberate trade-off.

How do we add an outside contractor without giving them a phone number or company account?

Each RVNT identity is a local Ed25519 keypair claimed by proof-of-work — no phone number, email, or KYC. A contractor installs the app, generates an identity on their own device, and you exchange and verify identities out-of-band (safety-number / QR verification is strongly recommended to defeat man-in-the-middle during the first key exchange). There are no seats to provision and no account database tying that person to a SIM.

Can we send large files like CAD drawings or video to a remote teammate?

Yes, over a direct peer-to-peer link there is no size limit; files are streamed in encrypted 512 KB chunks, integrity-checked with BLAKE3, and EXIF/metadata is stripped before sending, with no plaintext written to disk and no server copy. The honest caveat: if your two devices can't connect directly and the transfer falls back to a relay, it's capped at 256 MB until resumable relay ships.

RVNT is a post-quantum, peer-to-peer, end-to-end-encrypted messenger with no phone number and no servers — open source, and honest about being early.

Get RVNT All use cases