End-to-end encrypted

Private team messaging.

Lock is end-to-end encrypted chat for teams who have nothing to hide and everything to protect. Every message sealed on your device, readable only by your team.

09:41
#GENERAL E2EE
A
Alex 09:41 AM

Anyone reviewed the launch brief?

MC
Mia 09:42 AM

Yes — pushed the patch already.

S
Sam 09:43 AM

Deploying to staging now.

Message #general

Product walkthrough / Four quick steps

Less explaining.
More getting things done.

Follow a small team from their first invite to sharing the next project update. Open each step to see how Lock fits into the workday.

Actual web app screenshots · Demo workspace and example content, not a live workspace

01Set up your team

A home for the project.

Name your workspace during signup. General is ready automatically, and the next screen lets you invite a teammate or go straight to your first message.

No setup detour before the conversation.

Actual Lock workspace setup showing Studio North, General, and the teammate invitation form.
Actual web app / Workspace created and invitation queued
02Keep the conversation moving

An update, not another meeting.

Post a rich-text message in a channel or send a private DM. Live delivery, online presence, and unread badges help teammates pick up the conversation.

Decisions stay with the people doing the work.

Actual General conversation with Jamie’s first welcome message and the rich-text composer.
Actual web app / First encrypted message sent
03Share the files behind the work

The brief, right beside the discussion.

Attach a document or image to your message. Files are encrypted on your device before upload, so the attachment stays private alongside the conversation.

Less hunting through inboxes for the right file.

Actual General conversation showing Project-brief.txt with an Encrypted attachment label.
Actual web app / Project-brief.txt encrypted before upload
04Take the conversation with you

Desk, phone, or browser.

Use Lock on macOS, iPhone, or the web. Keep your team’s channels, direct messages, and encrypted files close wherever you work.

One workspace. More ways to stay connected.

Explore the apps
Studio / Your workspaceIllustrative preview
macOS

A focused native desktop workspace.

iPhone

Your conversations when you step away.

Web

Open Lock directly in your browser.

01 — Features

Your conversations stay private.
Your team stays connected.

01

End-to-end encryption

Messages are encrypted on your device and decrypted only on the recipient; your data stays yours.

02

Real-time delivery

Instant delivery over WebSockets. Encrypted does not mean slow.

03

Team workspaces

Channels, DMs, and roles organized in one secure place.

04

Direct team calls

Pro-only voice calls between two team members. Encrypted WebRTC transport, in beta—not group calls.

05

Zero knowledge

Encryption keys live on your device. Our servers never hold your private keys.

06

Encrypted files

Documents and files sealed in transit and at rest.

07

Two-factor auth

Passkeys, TOTP, and security-key support by default.

Calls are an early beta: chat-key possession checks run automatically with no code comparison. First-use trust depends on server-delivered keys; changed remembered keys block calls. Cross-network relay calling still needs live validation. Pro-only access is not yet enforced. Explore direct team calls.

macOS / iPhone / Web

One app, everywhere
you need to be.

A native macOS app for your Lock conversations. Keep channels, direct messages, and encrypted files close — without keeping a browser tab open.

Also on iPhone and the web. Take Lock with you, or open it in your browser — private team messaging wherever you work.

  • Private, by default.

    Messages and attachments encrypted on your device.

  • Stay in the loop.

    Live messages, online presence, and unread badges in your sidebar and Dock.

  • Make it your space.

    Rich-text messages, emoji, and optional message sounds. All in a focused desktop workspace.

Explore the encryption
Lock on macOS and iPhone / Interface previews

02 — Security

How your messages
stay private.

Encryption, up close
Explore encryption
01

Keys are born in your browser

Your device generates an encryption key pair. The service stores the public key and an encrypted private-key backup for recovery. How that backup is protected matters.

02

Messages are encrypted before they leave

Message bodies and new attachments are encrypted on your device. Recipients decrypt them using their keys; account details and conversation metadata are not hidden.

03

Understand the trust boundaries

Content encryption is not a blanket guarantee. Password-based recovery, server-delivered keys and unlocked devices have limits. No independent security audit is published here.

Read the security details and reproducible attachment evidence ↗

03 — What we hold

Nothing left to chance.

New message bodies and attachments reach storage as ciphertext. Recovery and authentication have important trust boundaries; encryption does not hide all account and conversation metadata.

Plaintext on our servers

Not stored

New message bodies and attachments are stored as ciphertext. Older public web uploads were not encrypted and are not retroactively protected by this update.

Access to your keys

Encrypted backup

Your device uses the private key; the server holds an encrypted backup. The account password also unlocks that backup, so the authentication server remains part of the trust boundary.

Evidence, not endorsements

Check the format

Review the attachment protocol, public test vector and CryptoKit verifier. These demonstrate format compatibility, not an independent audit or customer endorsement.

04 — Process

Three steps. One locked workspace.

01Create

Your people.
Your space.

Name your team and invite your people. Encryption is on from the first message.

02Communicate

Start something private.

Chat and share files in real time. Every exchange is sealed end-to-end.

03Stay locked

Keep your
circle close.

Manage invitations and membership. Know the recovery limits before your team relies on encrypted history.

Nothing
to hide.

Encrypted by default. Simple per-user pricing. Built for teams who take privacy seriously.

Get started
A closer look / Encryption

Just your team.
Just your conversation.

Messages are encrypted on your device before they’re sent. Recipients use their keys to decrypt them. Recovery, device security and server-provided keys have important trust limits.

  1. 01

    Sealed on your device

    Your browser encrypts the message before it leaves.

  2. 02

    Private along the way

    Our servers receive ciphertext, not readable messages.

  3. 03

    Opened by your team

    Your teammates’ devices decrypt the message using their keys.

Read the security details, limitations and test evidence ↗